all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefankangas@gmail.com>
To: Konrad Podczeck <konrad.podczeck@univie.ac.at>
Cc: 58625@debbugs.gnu.org
Subject: bug#58625: bug-gnu-emacs@gnu.org
Date: Fri, 21 Oct 2022 00:43:56 -0700	[thread overview]
Message-ID: <CADwFkm=qiKZS0S94qgfzzwyOzd5cJCi6zoRriWJ9u-5pzEbBrQ@mail.gmail.com> (raw)
In-Reply-To: <920562AA-16EB-4501-A649-F218CF60CA6B@univie.ac.at>

forcemerge 58637 58625
thanks

Konrad Podczeck <konrad.podczeck@univie.ac.at> writes:

>> This may be related to the recently fixed Bug#58637.
>
> Yes, with the latest master branch, everything is fine.

Great, thanks for checking.

> One final question: Now, e.g., latex.el., from the folder
> …/elpa/auctex-13.1.4, compiles into an eln-file, however, deleting
> afterwards the files latex.el and latex.elc from the folder
> …/elpa/auctex-13.1.4 results in an auctex with losses
> functionality. On the contrary, if, e.g., startup.el.gz and
> startup.elc are deleted from Applications/Emacs/Contents/Resources
> /lisp, the Emacs.app continues to be full functional. Can it be that
> such differences in the results of native compilation occur?

No, I think this is because startup.el is preloaded (so we don't need to
re-read that file from disk, it is already in memory when Emacs starts).





      reply	other threads:[~2022-10-21  7:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-19 10:14 bug#58625: bug-gnu-emacs@gnu.org Konrad Podczeck
2022-10-19 11:01 ` Stefan Kangas
2022-10-19 11:23   ` Konrad Podczeck
2022-10-19 11:47     ` Stefan Kangas
2022-10-19 12:05       ` Konrad Podczeck
2022-10-20 21:13         ` Stefan Kangas
2022-10-21  7:17           ` Konrad Podczeck
2022-10-21  7:43             ` Stefan Kangas [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CADwFkm=qiKZS0S94qgfzzwyOzd5cJCi6zoRriWJ9u-5pzEbBrQ@mail.gmail.com' \
    --to=stefankangas@gmail.com \
    --cc=58625@debbugs.gnu.org \
    --cc=konrad.podczeck@univie.ac.at \
    /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.