Timeline for undo-tree changed Treemacs layout when move history cursor in Spacemacs
Current License: CC BY-SA 4.0
13 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 16, 2024 at 1:02 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Mar 18, 2024 at 0:08 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Nov 18, 2023 at 23:06 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Oct 19, 2023 at 22:27 | answer | added | LI Bing | timeline score: 1 | |
| May 12, 2022 at 19:02 | comment | added | Edwin Clement | Putting a dot here, facing the same issue in spacemacs | |
| Apr 20, 2022 at 3:53 | comment | added | lawlist | In my own setup, I modified undo-tree-visualize-undo and undo-tree-visualize-redo to use with-current-buffer instead of switch-to-buffer-other-window, and that bypasses the problem with resizing window functions bound to the window-configuration-change-hook such as what is probably happening in your situation. Here is a gist from a couple of years ago -- It would be necessary to compare the code to the current version of undo-tree.el to ensure everything else is still the same. gist.github.com/lawlist/4765516cf58a1ccc1d11de63bacaff34 | |
| Apr 20, 2022 at 3:24 | comment | added | lawlist | If something is resizing windows, then the functions that have shrink and enlarge in their names are most likely responsible (with a few unlikely exceptions, e.g., where an alist to a display-buffer family of functions is expressly set with a particular width). Once you track down the function responsible, then you can work your way backwards to where the function is called, and then devise a plan to deal with the situation. You could even just put in some messages in the function mentioned in my previous comment to see when it gets called ... | |
| Apr 20, 2022 at 3:22 | comment | added | madaha | @lawlist Thank you for your advice. Maybe there are something config conflict by default. | |
| Apr 20, 2022 at 2:56 | comment | added | lawlist | I am not familiar with treemacs, but did a quick git clone and grep for shrink and enlarge and came up with the function treemacs--set-width. In your debugging quest, consider copying treemacs--set-width to a *scratch* buffer and modify it by making it do nothing. e.g., comment out everything and then evaluate the modified function; e.g., the new function that could be evaluated looks like (defun treemacs--set-width (width) "Doc-string." nil) You could even just type M-x eval-expression RET (defun treemacs--set-width (width) "Doc-string." nil) RET; and, then repeat your test. | |
| Apr 20, 2022 at 2:41 | comment | added | madaha | @lawlist Thank you. I just installed Spacemacs v.0.300.0 . I didn't set any addon configuration after install it. This issue happened on both Linux and macOS. | |
| Apr 20, 2022 at 2:21 | comment | added | lawlist | I am familiar with undo-tree and am unaware of any code that resizes windows. It only uses switch-to-buffer-other-window, switch-to-buffer and display-buffer. The culprit may possibly lie elsewhere. | |
| S Apr 20, 2022 at 1:18 | review | First questions | |||
| Apr 20, 2022 at 3:34 | |||||
| S Apr 20, 2022 at 1:18 | history | asked | madaha | CC BY-SA 4.0 |