unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Alan Mackenzie <acm@muc.de>
Cc: 53164@debbugs.gnu.org
Subject: bug#53164: After an ELC+ELN build, don't load the source file into a buffer.
Date: Mon, 10 Jan 2022 20:01:01 +0200	[thread overview]
Message-ID: <83wnj78o82.fsf@gnu.org> (raw)
In-Reply-To: <Ydxj8GvsGFlZNrKf@ACM> (message from Alan Mackenzie on Mon, 10 Jan 2022 16:50:56 +0000)

> Date: Mon, 10 Jan 2022 16:50:56 +0000
> From: Alan Mackenzie <acm@muc.de>
> 
> emacs-28 and master branches.
> 
> In batch-byte+native-compile (lisp/emacs-lisp/comp.el), the code fails
> to remove the source file argument from command-line-args-left, thus
> causing Emacs (or bootstrap-emacs) to regard this argument as a file to
> be visited after the compilation is complete.
> 
> This can lead (and has led) to bugs.
> 
> Remove this element from command-line-args-left at the end of
> batch-byte+native-compile.

Please show the smallest recipe to reproduce this.  Because I don't
think I follow your description, and in particular I saw no such
problems when building Emacs.

Thanks.





      parent reply	other threads:[~2022-01-10 18:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-10 16:50 bug#53164: After an ELC+ELN build, don't load the source file into a buffer Alan Mackenzie
2022-01-10 17:15 ` bug#53164: (After an ELC+ELN build, don't load the source file into a buffer.) fixed Alan Mackenzie
2022-01-10 18:05   ` Eli Zaretskii
2022-01-10 19:34     ` Alan Mackenzie
2022-01-10 19:53       ` Eli Zaretskii
2022-01-10 20:21         ` Alan Mackenzie
2022-01-11 12:27           ` Eli Zaretskii
2022-01-11 18:03             ` Alan Mackenzie
2022-01-11 18:45               ` Eli Zaretskii
2022-01-10 18:01 ` 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=83wnj78o82.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=53164@debbugs.gnu.org \
    --cc=acm@muc.de \
    /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).