Already there
Settings - Git - Config - Editor

Note: The original question was about Git editor, then it was changed to the GE specific editor

Already there
Settings - Git - Config - Editor

Don't work. Open GT Editor rather of Notepad++

You're welcome to send a PR.

@Pavia00 There is a misunderstanding...

You set notepad++ as the default editor for Git. So when git want to interact with you (during rebase, ...) it will open Notepad++.

Here the "Edit file in working directory" is a GitExtension feature and it always open the GitExtensions editor.

If you want to open the file with something else, that's a new feature that should be developed...
But we can't reuse the git setting because it contains special parameters to be used by Git only.

So if it's what you want, please could you rewrite your feature request to be more explicit?

Ok. I dream that I have the function of opening a notepad by pressing the F4 key or the context menu. Please add new features in the next implementation.
I think GE can open the editor using git settings, to anymore.

You have Ctrl+O to choose the editor:

You have Ctrl+O to choose the editor:
The function open only associated file and don't use git settings as you can see:

I can't open dockefiler, Yml .gitignory and all othe service files, becose cannot associating it

For short and fast edit, a file i be wont have open in git editor.

P.S. I never understood. Why so many questions? If you need to correct or add 1 line in the source code.

P.S. I never understood. Why so many questions? If you need to correct or add 1 line in the source code.

If you think it is easy - send a PR. Else - just stop, it won't take us far.

If you think it is easy - send a PR. Else - just stop, it won't take us far.

I can't understand you. Please explain the statement " send a PR. "?

P.S. I never understood. Why so many questions? If you need to correct or add 1 line in the source code.

Once again, you seems to not understand the real behavior and that it is GitExtensions that asks all these questions but that is the Windows way to do.

I can't understand you. Please explain the statement " send a PR. "?

It's difficult for us contributors that knows that things are often not easy to fix because you always have edge cases to handle that something is easy to fix because "you just have to do...". And also having to discuss a lot and explain all that to someone landing on the project.

So, that's Why @RussKie is asking you, if you think it is just a one line fix to do it and create the pull request (PR) so that we just have to review and merge it.

Discussing on such feature requests without code changes is a waste of time for everyone...