git/list[1] front-page[2] threads[3] people[4] search[5] about
 

interactive rebase editor pathname variable

From
NKNeal Kreitzinger <neal@rsss.com>
Date
May 13, 2010, 18:32 UTC
Message-ID
<hshglg$p2q$1@dough.gmane.org>
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

Next: Jonathan Nieder
Message 1 of 3 in “interactive rebase editor pathname variable”
  1. Neal KreitzingerMay 13, 2010
  2. Jonathan NiederMay 14, 2010
  3. Bert WesargMay 14, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.