Как мне получить COMMIT_EDITMSG для открытия из правильного местоположения?

Есть несколько проблем, которые могут вызывать путаницу и проблемы.

1. The Shell Special Variable

   If core.editor is set to the editor path and filename, then the $* variable is redundant and not needed. However, if the core.editor is set to a shell script, then the $* variable must be passed along to the editor.

   This is valid:

   $ git config --global core.editor "'D:/Path To/EditPadPro.exe' //newinstance"
   

   This is also valid:

   $ git config --global core.editor "'E:/Path To/editor.sh'"
   

   when editor.sh contains:

   #!/bin/sh
   "D:/Path To/EditPadPro.exe" //newinstance "$*"
   

2. Spaces in File Names

   Filenames with spaces can be a pain. If the path/filename is quoted, then it isn't usually a problem. But when setting the value of core.editor you have to either

   escape the spaces like this:

   "E:/Path\ To/editor.sh"
   

   or quote it twice like this:

   "'E:/Path To/editor.sh'"
   

   Without the extra quotes (or backslash escapes), you will have no problem setting the value, but it will fail when it's used because the outer quotes are not part of the value.

   EDIT: Latter method (quoting twice) seems safer. See the edit at the bottom for more explanation.

3. Windows Path Separator

   The filename that is being passed to the editor can be a relative path (i.e. .git/COMMIT_EDITMSG) or absolute path (i.e. e:/path to/.git/rebase-merge/git-rebase-todo), but in both cases it is using forward slashes as a path separator. Windows can usually accept forward slashes as a path separator, especially if the path is quoted. Perhaps the older version of EditPad Pro is unable to accept the forward slashes in combination with the hidden directory. A little bit of preprocessing can fix this.

   Note: Hardcoded paths with forward slashes and no hidden directory seem to work fine. Hardcoded paths with hidden directories and backslashes seem to work fine.

Окончательное решение

Я не очень разбираюсь в сценариях оболочки, но для меня сейчас работает следующее.

Файл editor.sh содержит:

#!/bin/sh
fullpath=`echo "$*" | tr '/' '\\\'`
"D:/Program Files/JGsoft/EditPadPro5/EditPadPro.exe" //newinstance "$fullpath"

и конфигурация устанавливается следующим образом:

$ git config --global core.editor "'E:/Path To/editor.sh'"

Моя копия EditPad Pro 5.3.2 теперь открывается с уже загруженными файлами, независимо от того, какая команда git запускает редактор.

EDIT: I had to change the value of core.editor. I had used backslashes to escape spaces in the path and this opened the editor properly. However, when a GIt command passed a fielname with a relative path (beginning with a dot) to my shell script, the value of $* was [email protected] rather than the filename, which caused the editor to open with a blank file named [email protected]. I thought I tested that combination, but apparently not. Using the quote twice method works.