Hi, It appears that git-commit and git-tag pass a partial pathname to the core.editor, e.g. ".git/COMMIT_EDITMSG" that is relative to the working tree directory. However, git-rebase -i passes an absolute pathname to the core.editor, e.g. "home/someuser/someworkingtree/.git/rebase-merge/git-rebase-todo". This causes problems in our shop because our proprietary editor cannot handle pathnames beginning with a period (it translates the period to a slash) and therefore our entry for core.editor is 'someeditor "$PWD/$1"'. This breaks on git rebase -i when the $1 contains the full pathname. Can this be added to the bugfix list for git to make the $1 value passed to core.editor by all git commands to always be relative pathnames (or absolute pathnames). FWIW, I prefer absolute pathnames because a config entry of 'someeditor $1' is more straightforward than 'someeditor "$PWD/$1"'. (Note: the reason I must pass $1 is because the editor runs on top of a runtime and is actually called as 'someruntime someeditor "$1"') v/r, Neal -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html