From: Camden Narzt <camden.narzt@gmail.com>
To: Robert Pluim <rpluim@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Error 255 while preparing to dump
Date: Thu, 3 Sep 2020 11:34:02 -0600 [thread overview]
Message-ID: <CFCC5513-19C5-4617-9113-A165F26970EA@gmail.com> (raw)
In-Reply-To: <m2ft7z0xuc.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1479 bytes --]
Thanks, that did the trick.
Cheers,
Camden Narzt
> On Sep 3, 2020, at 7:54 AM, Robert Pluim <rpluim@gmail.com> wrote:
>
>>>>>> On Wed, 2 Sep 2020 10:31:36 -0600, Camden Narzt <camden.narzt@gmail.com> said:
>
> Camden> (require 'seq)
> Camden> (setq exec-path (seq-filter (lambda (haystack) (not (string-match-p (regexp-quote "Homebrew/shims") haystack))) exec-path))
> Camden> (setenv "PATH" (string-join (seq-filter (lambda (haystack) (not (string-match-p (regexp-quote "Homebrew/shims") haystack))) (split-string (getenv "PATH") ":")) ":"))
>
> Camden> The error:
>
> Camden> Loading site-load.el (source)...
> Camden> (require seq) while preparing to dump
> Camden> make[1]: *** [emacs.pdmp] Error 255
> Camden> make: *** [src] Error 2
>
> Camden> Can anyone who is more knowledgeable about the new portable dumper system please steer me in the right direction?
>
> This doesnʼt really have anything to do with the portable dumper. When
> dumping the portion of emacs lisp that you can use is fairly limited,
> so you canʼt just go loading seq.el. Try something along the lines of
> (untested):
>
> (setq exec-path (delete nil
> (mapcar
> (lambda (elt)
> (unless (string-match-p "Homebrew/shims" elt) elt))
> exec-path)))
>
> I donʼt think you need to do anything with PATH, Emacs doesnʼt store
> that anywhere.
>
> Robert
[-- Attachment #2: Type: text/html, Size: 3550 bytes --]
prev parent reply other threads:[~2020-09-03 17:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-02 16:31 Error 255 while preparing to dump Camden Narzt
2020-09-03 13:54 ` Robert Pluim
2020-09-03 17:34 ` Camden Narzt [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CFCC5513-19C5-4617-9113-A165F26970EA@gmail.com \
--to=camden.narzt@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=rpluim@gmail.com \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.