From: Eli Zaretskii <eliz@gnu.org>
To: "Gerd Möllmann" <gerd.moellmann@gmail.com>
Cc: michael_heerdegen@web.de, 68200@debbugs.gnu.org
Subject: bug#68200: 30.0.50; Emacs reloads init file when calling `documentation'
Date: Sun, 07 Jan 2024 09:33:08 +0200 [thread overview]
Message-ID: <8334v9simj.fsf@gnu.org> (raw)
In-Reply-To: <m2bk9xn1fa.fsf@Pro.fritz.box> (message from Gerd Möllmann on Sun, 07 Jan 2024 06:43:37 +0100)
> From: Gerd Möllmann <gerd.moellmann@gmail.com>
> Cc: Eli Zaretskii <eliz@gnu.org>, 68200@debbugs.gnu.org
> Date: Sun, 07 Jan 2024 06:43:37 +0100
>
> Michael Heerdegen <michael_heerdegen@web.de> writes:
>
> > | #13 0x000055555581b5d4 in Fload (file=XIL(0x555556242004), noerror=XIL(0x30), nomessage=XIL(0x30), nosuffix=XIL(0x30), must_suffix=XIL(0)) at lread.c:1792
> > | #14 0x000055555581b89a in save_match_data_load (file=XIL(0x555556242004), noerror=XIL(0x30), nomessage=XIL(0x30), nosuffix=XIL(0x30), must_suffix=XIL(0)) at lread.c:1841
> > | #15 0x00005555557c9db7 in reread_doc_file (file=XIL(0x555556242004)) at doc.c:355
> > | #16 0x00005555557c9fc5 in Fdocumentation (function=XIL(0x2ae8b20),
> > | raw=XIL(0x30)) at doc.c:399
>
> Looks to me like Fdocumentation detects that the file containing the doc
> has changed, and that it needs to reload it. I think you mentioned that
> this happens when you change the file and existing Emacs sessions do the
> reload? In that case, this looks like normal behaviour to me, unless I'm
> overlooking something?
Right.
next prev parent reply other threads:[~2024-01-07 7:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-02 1:53 bug#68200: 30.0.50; Emacs reloads init file when calling `documentation' Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-02 2:33 ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-02 13:09 ` Eli Zaretskii
2024-01-07 1:40 ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-07 5:43 ` Gerd Möllmann
2024-01-07 7:33 ` Eli Zaretskii [this message]
2024-01-07 17:20 ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-07 17:33 ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-08 21:22 ` Alan Mackenzie
2024-01-08 23:09 ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-09 11:26 ` Alan Mackenzie
2024-01-10 3:28 ` bug#68200: File local byte-compile-dynamic-docstrings:nil ignored (was: bug#68200: 30.0.50; Emacs reloads init file when calling `documentation') Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-11 17:59 ` Alan Mackenzie
2024-01-09 12:36 ` bug#68200: 30.0.50; Emacs reloads init file when calling `documentation' Eli Zaretskii
2024-01-11 18:10 ` Alan Mackenzie
2024-01-11 19:22 ` Eli Zaretskii
2024-01-11 19:40 ` Alan Mackenzie
2024-01-11 19:54 ` Stefan Kangas
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=8334v9simj.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=68200@debbugs.gnu.org \
--cc=gerd.moellmann@gmail.com \
--cc=michael_heerdegen@web.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).