How do I enable/disable the Interactive Rebase Editor?

[craph]

Hi @eamodio ,

First, thank you for your beautiful work for GitLens :)

Is there an easy way to turn back on the Interactive Rebase Editor if I have disabled it by mistake ?

Where is the settings to turn it back on ?

Thank you very much.

Best regards,

[eamodio]

@craph Thanks!

To enable the Interactive Rebase Editor use the GitLens: Enable Interactive Rebase Editor command from the command palette (ctrl+shift+p or cmd+shift+p).

To disable the Interactive Rebase Editor use the GitLens: Disable Interactive Rebase Editor command from the command palette (ctrl+shift+p or cmd+shift+p).

Additionally, you can also open the GitLens interactive settings editor from the command palette (ctrl+shift+p or cmd+shift+p) and search for GitLens: Open Settings and jump/scroll down to the Interactive Rebase Editor section

[ivancuric]

Ah, was running from the right-click context menu in GitLens. Thought it'd disable it there as well.

[eamodio]

Not currently. If run from inside GitLens I "assume" you want the UI. Although, I should allow and opt-out for that as well.

[PiterGoCompany]

I'm using VS Code as my GIT default editor. After installing GitLens every rebase run from command line (eg. git rebase -i master) is causing that GitLens Interactive Editor is displayed. I can't disable Interactive Editor. Changing option in GitLens settings, and in VS setting doesn't help.

[eamodio]

Can you please add any more details you have to this issue: #1687 (comment). Thanks!

[kellijohnson-NOAA]

This setting is reset each time VS Code updates. Is there any way to make it stick even across updates?

[devinrhode2]

for heavy rebasers, I don't think this is a net positive.

It is quite buggy wrt the state of the git-rebase-todo text file.

Also, you can't ctrl+f search commits and sha's.

It's great if you've literally never used interactive rebase, though!!!

I'd love ctrl+f and to see the bugs fixed

[eamodio]

Please open issues about the "buggy-ness" you are seeing - as I'm not aware of any issues.

As for Ctrl+F -- I thought I had enabled the search, but apparently not, so I'll get that in ASAP.

And of course if you are more comfortable using the text file, its just a single click away (one time or for all time)

[eamodio]

CTRL+F will be enabled in the next insiders builds

[devinrhode2]

I might be becoming an old hat, I guess I started with the text file, and now I'm coming back to it due to the bugginess.

I wonder if you might consider something akin to vscode's native git merge assistant? Where vscode basically just adds coloring across git conflict markers, and then inserts little text buttons for accepting a certain chunk of code?

It's going to be hard to re-produce, but somehow gitlens seems to be holding onto state of the file

Are you able to add logging (like with Sentry.io)? That's probably the best long term solution