From: Chris Marusich <cmmarusich@gmail.com>
To: Pierre Neidhardt <ambrevar@gmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Magit interactive rebase error: perl not found
Date: Thu, 02 Aug 2018 19:35:09 -0700 [thread overview]
Message-ID: <874lgcxjmq.fsf@gmail.com> (raw)
In-Reply-To: <87in4zepge.fsf@gmail.com> (Pierre Neidhardt's message of "Sat, 28 Jul 2018 10:26:09 +0200")
[-- Attachment #1: Type: text/plain, Size: 1199 bytes --]
Pierre Neidhardt <ambrevar@gmail.com> writes:
> When rebasing interactively with Magit, I get the following error
>
> 1 git … rebase -i d64bc3b\^
> /home/ambrevar/.guix-profile/libexec/git-core/git-rebase--interactive: line 277: perl: command not found
> Could not execute editor
>
> From commandline it works fine. If I install perl in my user profile,
> it works too.
>
> I suspect some defvar patch to be missing.
>
> Anyone else?
I don't use Magit, so I can't say. What's in the
git-rebase--interactive file on line 277? In my case, it's this:
267 git_sequence_editor () {
268 if test -z "$GIT_SEQUENCE_EDITOR"
269 then
270 GIT_SEQUENCE_EDITOR="$(git config sequence.editor)"
271 if [ -z "$GIT_SEQUENCE_EDITOR" ]
272 then
273 GIT_SEQUENCE_EDITOR="$(git var GIT_EDITOR)" || return $?
274 fi
275 fi
276
277 eval "$GIT_SEQUENCE_EDITOR" '"$@"'
278 }
Assuming it's the same for you, it would be interesting to see what the
value of $GIT_SEQUENCE_EDITOR and $@ are in this case. Maybe you could
hack together a custom Git package to figure it out?
--
Chris
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2018-08-03 2:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-28 8:26 Magit interactive rebase error: perl not found Pierre Neidhardt
2018-08-03 2:35 ` Chris Marusich [this message]
2018-08-04 17:38 ` Pierre Neidhardt
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874lgcxjmq.fsf@gmail.com \
--to=cmmarusich@gmail.com \
--cc=ambrevar@gmail.com \
--cc=help-guix@gnu.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).