You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are many issues and requests regarding the size of the treemacs window. But my problem is different: When I open treemacs on emacs startup, the other window right next to it shrinks by the size of the treemacs window, so that the overall buffer stays the same size, which is shared between treemacs and the other window. Then I need to enlarge the buffer manually, to restore the other window's size. I want to have this be done automatically: keep the size of the other window and instead resize the overall buffer (the window in terms of the window manager) to the left/right by the treemacs window. Of course only with Xemacs like flavours, not when the emacs is running inside a terminal.
Is there a way to achieve this? Otherwise, please consider this as a feature request :).
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity (this bot only works as a reminder, it will not close issues).
Hi,
There are many issues and requests regarding the size of the treemacs window. But my problem is different: When I open treemacs on emacs startup, the other window right next to it shrinks by the size of the treemacs window, so that the overall buffer stays the same size, which is shared between treemacs and the other window. Then I need to enlarge the buffer manually, to restore the other window's size. I want to have this be done automatically: keep the size of the other window and instead resize the overall buffer (the window in terms of the window manager) to the left/right by the treemacs window. Of course only with Xemacs like flavours, not when the emacs is running inside a terminal.
Is there a way to achieve this? Otherwise, please consider this as a feature request :).
The text was updated successfully, but these errors were encountered: