From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: New installation of GNU Emacs 28.2, (Debian bookworm,) error
Date: Fri, 15 Mar 2024 09:03:15 +0200 [thread overview]
Message-ID: <865xxo9du4.fsf@gnu.org> (raw)
In-Reply-To: <20240314204108.11686.qmail@panix.com> (conover@panix.com)
> Date: Thu, 14 Mar 2024 13:41:07 -0700
> From: conover@panix.com (John Conover)
>
> Eli Zaretskii writes:
> >
> > But anyway: why are you compiling your init file? It isn't supposed
> > to include any significant Lisp code that is worth compiling.
>
> I didn't recompile it. Emacs 28 did not recognize ~/.emacs as the
> source, but did recognize the ~/.emacs.elc file.
That's very strange: I've been using all the versions of Emacs since
19.30 till now with ~/.emacs, and never had any problems with its
recognizing this init file.
> I had to ln -s .emacs .emacs.el to make it work; it then compiled
> ~.emacs.el into ~/.emacs.d/eln-cache/*.
>
> Seems odd to be shuffling around file names and directories for a
> program that is 40 years old this year.
Indeed, and it shouldn't be necessary. Perhaps there's something
special in your arrangement of files and/or directories of importance
to Emacs, which causes this. If you can find out what that is, please
submit a bug report, if Emacs 29 still doesn't recognize ~/.emacs
(after you delete .emacs.el, .emacs.elc, and the corresponding .eln
file).
prev parent reply other threads:[~2024-03-15 7:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-14 18:55 New installation of GNU Emacs 28.2, (Debian bookworm,) error John Conover
2024-03-14 19:00 ` Eli Zaretskii
2024-03-14 19:19 ` John Conover
2024-03-14 20:03 ` Eli Zaretskii
2024-03-14 20:41 ` John Conover
2024-03-15 7:03 ` Eli Zaretskii [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://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=865xxo9du4.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=help-gnu-emacs@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).