From: "Mark A. Hershberger" via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Teika Kazura <teika@gmx.com>, 62136@debbugs.gnu.org
Subject: bug#62136: a further update: straight.el & nativecomp interaction?
Date: Thu, 06 Apr 2023 13:25:52 -0400 [thread overview]
Message-ID: <0a7d42d74701ea0b24fafbc1c02a26d9c795f932.camel@everybody.org> (raw)
In-Reply-To: <20230406.070410.1662312281664790517.teika@gmx.com>
I've gone through my init.el and removed all references to straight
which means that some packages I was installing with use-
package+straight are not available. For now, the problem seems to have
disappeared.
But, assuming one of those packages isn't at fault here, maybe this
inidicates a problem with use-package+straight and native-comp?
next prev parent reply other threads:[~2023-04-06 17:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-12 5:06 bug#62136: 30.0.50; byte-compiled init.el loads correctly, but native compiled init.eln loads incompletely Mark A. Hershberger via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-12 7:24 ` Eli Zaretskii
2023-03-13 5:40 ` Mark A. Hershberger via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-05 22:04 ` bug#62136: (no subject) Teika Kazura
2023-04-06 15:21 ` bug#62136: init.el partial execution Mark A. Hershberger via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-06 17:25 ` Mark A. Hershberger via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-04-06 17:33 ` bug#62136: a further update: straight.el & nativecomp interaction? Eli Zaretskii
2023-04-06 18:07 ` Mark A. Hershberger via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-06 18:24 ` Eli Zaretskii
2023-05-05 6:41 ` Eli Zaretskii
2023-05-05 12:31 ` Mark A. Hershberger via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-05 13:31 ` Eli Zaretskii
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=0a7d42d74701ea0b24fafbc1c02a26d9c795f932.camel@everybody.org \
--to=bug-gnu-emacs@gnu.org \
--cc=62136@debbugs.gnu.org \
--cc=mah@everybody.org \
--cc=teika@gmx.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.