unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Mark A. Hershberger" <mah@nichework.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "Mark A. Hershberger" <mah@everybody.org>, 55714@debbugs.gnu.org
Subject: bug#55714: 29.0.50; eval-when-compile leaves behind artifacts in init.el?
Date: Mon, 30 May 2022 08:40:23 -0700 (PDT)	[thread overview]
Message-ID: <622622085.200972.1653925223438.JavaMail.zimbra@nichework.com> (raw)
In-Reply-To: <83o7zfkba6.fsf@gnu.org>

Hrm... I can't seem to reproduce this now.

I'm gonna put this down to some stray .elc files or something after I re-compiled emacs.

This can be closed.

----- On May 29, 2022, at 10:24 PM, Eli Zaretskii eliz@gnu.org wrote:

>> Date: Sun, 29 May 2022 15:43:43 -0400
>> From:  "Mark A. Hershberger" via "Bug reports for GNU Emacs,
>>  the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>> 
>> 
>> I've recently found “M-x woman RET” fails. In resolving this, it looks
>> like it caused by the presense of
>> 
>>      (eval-when-compile
>>          ....
>>          (defvar dired-mode-map nil
>>          ....
>> 
>> The only reason I had this was to avoid warnings during compilation.
>> Previously, it did not cause problems, but now it looks like it is
>> (maybe?) stored in the compiled init.el and re-used in latter emacs
>> start ups.
> 
> Thanks, but could you perhaps present a recipe for reproducing the
> problem starting from the smallest init.el?





  reply	other threads:[~2022-05-30 15:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-29 19:43 bug#55714: 29.0.50; eval-when-compile leaves behind artifacts in init.el? Mark A. Hershberger via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-30  2:24 ` Eli Zaretskii
2022-05-30 15:40   ` Mark A. Hershberger [this message]
2022-05-30 16:00     ` 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=622622085.200972.1653925223438.JavaMail.zimbra@nichework.com \
    --to=mah@nichework.com \
    --cc=55714@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=mah@everybody.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).