From: Lars Ingebrigtsen <larsi@gnus.org>
To: Andrea Corallo <akrl@sdf.org>
Cc: Glenn Morris <rgm@gnu.org>,
Arne Babenhauserheide <arne_bab@web.de>,
16242@debbugs.gnu.org, Noam Postavsky <npostavs@gmail.com>
Subject: bug#16242: 24.3; wish: set init directory (.emacs.d) by commandline flag for easy custom environments
Date: Thu, 27 Jan 2022 16:58:21 +0100 [thread overview]
Message-ID: <87pmodmaqq.fsf@gnus.org> (raw)
In-Reply-To: <xjfilu5zdhv.fsf@ma.sdf.org> (Andrea Corallo's message of "Thu, 27 Jan 2022 10:20:28 +0000")
Andrea Corallo <akrl@sdf.org> writes:
> I don't see anything any obvious here. Well to be honest I don't find
> many obvious things in our startup in general :)
>
> I can only imagine that Emacs is not finding the source to compile from,
> in that case we should get warnings, do you find trace of these?
I think I may have found what I did wrong in setting up the eln
directory, but currently the build doesn't work well with nativecomp
even without my changes -- require complaints about require loading
itself recursively, or something. (I think there's a separate bug
report about that...)
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-01-27 15:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-24 15:46 bug#16242: 24.3; wish: set init directory (.emacs.d) by commandline flag for easy custom environments Arne Babenhauserheide
2019-08-15 2:12 ` Lars Ingebrigtsen
2019-08-15 4:18 ` Glenn Morris
2019-08-15 4:33 ` Lars Ingebrigtsen
2019-08-15 14:29 ` Noam Postavsky
2019-08-15 23:13 ` Lars Ingebrigtsen
2022-01-26 16:44 ` Lars Ingebrigtsen
2022-01-27 10:20 ` Andrea Corallo
2022-01-27 15:58 ` Lars Ingebrigtsen [this message]
2022-01-27 22:36 ` Lars Ingebrigtsen
2022-01-27 23:30 ` Glenn Morris
2019-08-15 14:44 ` 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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pmodmaqq.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=16242@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=arne_bab@web.de \
--cc=npostavs@gmail.com \
--cc=rgm@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.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).