Interactive rebase splitting to new pane for no reason #5007
Unanswered
mjmatthiesen
asked this question in
Q&A
Replies: 2 comments 3 replies
-
|
The extra pane comes from GitLens opening its own commit‑message editor. // settings.json
{
"gitlens.editor.commitMessageEditor": "none" // or "default" to use VS Code’s built‑in editor
}After you reload the window the rebase will edit the commit message in the current editor tab, not split a new pane. I ran into the same thing on 2023‑09 and fixed it with this setting. |
Beta Was this translation helpful? Give feedback.
2 replies
-
|
Looks to be fixed by 87c7be8 (which has been shipped now) |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment

Uh oh!
There was an error while loading. Please reload this page.
-
So I don't know if this is a bug, or if there's some config I am not finding, but the behaviour is stealing screen space for no discernible reason. Tabs exist and tabs are good.
started process, correctly uses the current view, no new pane:

once I start the rebase, I now get a new pane for zero discernible reason.

Sometimes everything ends up in the pane, sometimes it's just the interactive rebase. That seems to depend on what my view looked like before. Not a 100% on that, but if I don't get the second pane issue, then it wouldn't matter.
Anyway, long story short, how do I disable this behaviour?
Beta Was this translation helpful? Give feedback.
All reactions