From: Junio C Hamano Date: Wed, 14 Oct 2009 19:11:28 GMT Subject: Re: git-commit feature request: pass editor command line options Message-ID: <7vvdihdc4f.fsf@alter.siamese.dyndns.org> In-Reply-To: <20091014172337.GE6115@genesis.frugalware.org> Miklos Vajna writes: > On Tue, Oct 13, 2009 at 09:58:51PM -0700, Matthew Cline wrote: >> >> I'd like to be able to have git-commit pass the commit-message editor command >> line options which aren't passed to the editor for other usages. Right now >> I have "co" aliased to "!sh -c 'GIT_EDITOR=git-commit-editor git commit'", >> where git-commit-editor is a wrapper around my editor-of-choice which passes >> the editor the command line options I want, but it'd be simpler and cleaner >> if I could just set "commit.editor_options=-BAR". Or even let there be a >> separate editor for commits, so I could do "core.editor=foo" and >> "commit.editor=foo -BAR". > > 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".