From: Pierre Neidhardt <ambrevar@gmail.com>
To: Chris Marusich <cmmarusich@gmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Magit interactive rebase error: perl not found
Date: Sat, 04 Aug 2018 19:38:56 +0200 [thread overview]
Message-ID: <87zhy2xc9b.fsf@gmail.com> (raw)
In-Reply-To: <874lgcxjmq.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 679 bytes --]
OK, I figured it out, it's in the `magit--cherry-move' function:
--8<---------------cut here---------------start------------->8---
(push (format "%s=perl -i -ne '/^pick (%s)/ or print'"
"GIT_SEQUENCE_EDITOR"
(mapconcat #'magit-rev-abbrev commits "|"))
process-environment)
--8<---------------cut here---------------end--------------->8---
This "perl" could not be automatically detected by the Guix path-patchers.
We could patch this but I think this also deserves an upstream fix:
https://github.com/magit/magit/issues/3537
--
Pierre Neidhardt
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
prev parent reply other threads:[~2018-08-04 17:39 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
2018-08-04 17:38 ` Pierre Neidhardt [this message]
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=87zhy2xc9b.fsf@gmail.com \
--to=ambrevar@gmail.com \
--cc=cmmarusich@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).