From: Junio C Hamano <gitster@pobox.com>
To: Peter Oberndorfer <kumbayo84@arcor.de>
Cc: git@vger.kernel.org
Subject: Re: [RFC/WIP PATCH] Use config value rebase.editor as editor when starting git rebase -i
Date: Tue, 11 Oct 2011 11:37:55 -0700 [thread overview]
Message-ID: <7vipnvfk70.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <201110111956.08829.kumbayo84@arcor.de> (Peter Oberndorfer's message of "Tue, 11 Oct 2011 19:56:08 +0200")
Peter Oberndorfer <kumbayo84@arcor.de> writes:
> Using $GIT_EDITOR or core.editor config var for this is not possible
> since it is also used to start the commit message editor for reword action.
Your tool _could_ be smart about this issue and inspect the contents to
launch a real editor when it is fed a material not for sequencing, but
that feels hacky.
> * GIT_EDITOR env var is not honored anymore after this change.
Care to explain? "git var" knows magic about a few variables like
GIT_EDITOR and GIT_PAGER.
$ git config core.editor vim
$ GIT_EDITOR=vi EDITOR=emacs git var GIT_EDITOR
vi
$ unset GIT_EDITOR; EDITOR=emacs git var GIT_EDITOR
emacs
> * Should git_rebase_editor be in git-rebase--interactive.sh instead
Probably yes.
> * How should the config be called?
Given that in the longer term we would be using a unified sequencer
machinery for not just rebase-i but for am and cherry-pick, I would advise
against calling this anything "rebase". How does "sequence.edit" sound?
You need to be prepared to adjust your code to deal with new kinds of
sequencing insns in the insn sheet and possibly a format change of the
insn sheet itself.
next prev parent reply other threads:[~2011-10-11 18:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-11 17:56 [RFC/WIP PATCH] Use config value rebase.editor as editor when starting git rebase -i Peter Oberndorfer
2011-10-11 18:15 ` Phil Hord
2011-10-11 18:37 ` Junio C Hamano [this message]
2011-10-11 21:16 ` Peter Oberndorfer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vipnvfk70.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=kumbayo84@arcor.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox