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
{{ message }}
This repository was archived by the owner on Apr 11, 2023. It is now read-only.
Notepad++ is triggered 1st time and file opens and Im midway into editing file e.g which commits to squash/reword and before I get a chance to finish in cmd terminal it skips the operation to end. whatever the file I was editing is left as a uncommitted change and has to be discarded or deleted.
The recommended workaround was also identified:
Try setting your editor to "notepad++ -multiInst". Plain notepad++ will only tell the already running instance to open the file before exiting, which looks as if you finished editing the file in record time.
This is because Notepad++ can be used with a tabbed interface, and this can lead to a scenario where a file is opened in a new tab, and then the process closes immediately - getting into a state that's weird and confusing.
I had a quick look at what might be involved with passing arguments to the associated file editor, and I couldn't spot an easy solution. This also requires us to detect you've configured notepad++ as the default editor for text files, which we don't do right now - so that's more work.
I've got a lot on my plate right now, but happy to provide guidance where possible if someone is keen in getting involved.