From: "Björn Lindqvist" <bjourne@gmail.com>
To: phillip.wood@dunelm.org.uk
Cc: git@vger.kernel.org
Subject: Re: git rebase --continue error message is misleading
Date: Mon, 10 Feb 2025 11:19:47 +0100 [thread overview]
Message-ID: <CALG+76erpDGFinXsockB8=+GPEoEtd+xw=xVN1HCzv7=aFymoA@mail.gmail.com> (raw)
In-Reply-To: <534e8534-a9bd-428b-87f9-a512c9378b19@gmail.com>
Den fre 13 dec. 2024 kl 15:38 skrev Phillip Wood <phillip.wood123@gmail.com>:
> On 09/12/2024 13:02, Björn Lindqvist wrote:
> > $ LANG=C git rebase --continue
> > hint: Waiting for your editor to close the file... error: cannot run
> > vi: No such file or directory
> > error: unable to start editor 'vi'
> > Please supply the message using either -m or -F option.
>
> This line comes from "git commit" whenever launch_editor() fails. I
> wonder if we'd be better to recommend that the user sets up a working
> editor instead. The message is certainly unhelpful when we run "git
> commit" from "git cherry-pick/merge/rebase/revert" where we want to seed
> the message that the user edits.
Here, I don't think assuming the user has vi installed is correct.
> I don't think that is a good idea when "git commit" is being run from
> "git rebase". In that case we want to preserve the original message and
> authorship and using '-F' or '-m' would not do that.
The error should tell you about that, I think. Right now I get:
LANG=C git commit
hint: Waiting for your editor to close the file... error: cannot run
vi: No such file or directory
error: unable to start editor 'vi'
Please supply the message using either -m or -F option.
The only solution I've found is git commit -m "blah".
--
mvh/best regards Björn Lindqvist
next prev parent reply other threads:[~2025-02-10 10:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-09 13:02 git rebase --continue error message is misleading Björn Lindqvist
2024-12-13 14:38 ` Phillip Wood
2025-02-10 10:19 ` Björn Lindqvist [this message]
2025-02-10 16:59 ` Junio C Hamano
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='CALG+76erpDGFinXsockB8=+GPEoEtd+xw=xVN1HCzv7=aFymoA@mail.gmail.com' \
--to=bjourne@gmail.com \
--cc=git@vger.kernel.org \
--cc=phillip.wood@dunelm.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).