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

Re: git-commit feature request: pass editor command line options

From
Jeff King <peff@peff.net>
Date
Oct 14, 2009, 21:12 UTC
Message-ID
<20091014211245.GA21670@sigill.intra.peff.net>
In-Reply-To
<7vvdihdc4f.fsf@alter.siamese.dyndns.org>
On Wed, Oct 14, 2009 at 12:11:28PM -0700, Junio C Hamano wrote:
Show 8 quoted lines
> > Hmm, what is the use-case when using an option --foo is useful when
> > creating a commit, but not useful when crating a tag?
> >
> > Apart from introducing inconsistency...
> 
> Not between commit and tag, but I can see you may want to auto-wrap for
> log message but forbid auto-wrap when editing rebase insn sheet during
> "rebase -i".

I think most people who want that just have their editor automagically recognize the different situations based on the file name or contents. I don't think the original author is wrong to want to be able to use command-line options to do so, but if he is using a common editor like vim or emacs, I think such autodetection has already been written.

-Peff
Previous: Junio C HamanoNext: Matthew Cline
Message 4 of 6 in “git-commit feature request: pass editor command line options”
  1. Matthew ClineOct 14, 2009
  2. Miklos VajnaOct 14, 2009
  3. Junio C HamanoOct 14, 2009
  4. Jeff KingOct 14, 2009
  5. Matthew ClineOct 14, 2009
  6. Miklos VajnaOct 14, 2009

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.