From: Martin Becze <mjbecze@riseup.net>
To: Malte Gerdes <malte.f.gerdes@gmail.com>
Cc: 43277@debbugs.gnu.org
Subject: bug#43277: emacs-next is broke, "seq" missing
Date: Tue, 8 Sep 2020 08:17:33 -0500 [thread overview]
Message-ID: <44d34919-f529-8131-3645-e6f6ad61855e@riseup.net> (raw)
In-Reply-To: <CAMVpQiUaMptTYs832N_CoaarpeJps=GxQA-9JaXOrPo4tTmmQQ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 774 bytes --]
I just tried out emacs27 and what replicated Malte's experience. But
even after reloading my environment emacs28 doesn't work.
On 9/8/20 7:40 AM, Malte Gerdes wrote:
> Hi,
>
> I had a similar error yesterday, with emacs27. Turned out I had to
> reload my environment because some variables still pointed to emacs 26.3
> directories which didn't exist anymore.
>
> Malte
>
> On Tue, 8 Sep 2020, 14:25 Martin Becze, <mjbecze@riseup.net
> <mailto:mjbecze@riseup.net>> wrote:
>
> emacs-next recently broke. It now has this error on start up.
>
> "require: Cannot open load file: No such file or directory, seq"
>
> I think this must have happened relatively recently (with the last 3
> weeks) since it was working fine earlier.
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-09-08 13:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-08 12:13 bug#43277: emacs-next is broke, "seq" missing Martin Becze
2020-09-08 12:40 ` Malte Gerdes
2020-09-08 13:17 ` Martin Becze [this message]
2020-09-08 14:01 ` Michael Rohleder
2020-09-08 15:07 ` Martin Becze
2020-09-11 20:09 ` Pierre Langlois
2020-09-14 22:08 ` bug#43277: [PATCH] gnu: emacs-next: Fix load path and version Morgan.J.Smith
2020-09-22 13:05 ` Morgan Smith
2020-09-22 18:35 ` Pierre Langlois
2020-09-26 12:08 ` Morgan Smith
2020-10-01 15:05 ` Maxim Cournoyer
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=44d34919-f529-8131-3645-e6f6ad61855e@riseup.net \
--to=mjbecze@riseup.net \
--cc=43277@debbugs.gnu.org \
--cc=malte.f.gerdes@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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).