threads / discuss / 21238

git-commit feature request: pass editor command line options

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

## tl;dr

6 messages between Oct 14, 2009 and Oct 14, 2009.

replies: 5people: 4as markdown or json

Matthew Cline· Oct 14, 2009, 04:58 UTC · lore

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".

-- 
View this message in context: http://www.nabble.com/git-commit-feature-request%3A-pass-editor-command-line-options-tp25885354p25885354.html
Sent from the git mailing list archive at Nabble.com.

Miklos Vajna· Oct 14, 2009, 17:23 UTC · re: Matthew Cline · lore

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

On Tue, Oct 13, 2009 at 09:58:51PM -0700, Matthew Cline <matt@nightrealms.com> wrote:

Show 9 quoted lines

> 
> 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...

Junio C Hamano· Oct 14, 2009, 19:11 UTC · re: Miklos Vajna · lore

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

Miklos Vajna <vmiklos@frugalware.org> writes:

Show 15 quoted lines

> On Tue, Oct 13, 2009 at 09:58:51PM -0700, Matthew Cline <matt@nightrealms.com> 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".

Jeff King· Oct 14, 2009, 21:12 UTC · re: Junio C Hamano · lore

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

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

Matthew Cline· Oct 14, 2009, 20:03 UTC · re: Miklos Vajna · lore

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

On Wednesday 14 October 2009 10:23:38 am Miklos Vajna wrote:

> Hmm, what is the use-case when using an option --foo is useful when
> creating a commit, but not useful when crating a tag?

In my case, it's using a commit template which starts with a comment, so I want to move the cursor down to the line below the comment.

Miklos Vajna· Oct 14, 2009, 22:12 UTC · re: Matthew Cline · lore

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

On Wed, Oct 14, 2009 at 01:03:01PM -0700, Matthew Cline <matt@nightrealms.com> wrote:

Show 7 quoted lines

> On Wednesday 14 October 2009 10:23:38 am Miklos Vajna wrote:
> 
> > Hmm, what is the use-case when using an option --foo is useful when
> > creating a commit, but not useful when crating a tag?
> 
> In my case, it's using a commit template which starts with a comment, so I 
> want to move the cursor down to the line below the comment.

Then rebase, tag, add -e and even commit --amend would use core.editor, while commit alone would use commit.editor, right?

A minor confusion would be that git commit --amend would not use commit.editor. ;-)