unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: "Gerd Möllmann" <gerd.moellmann@gmail.com>,
	acm@muc.de, "Eli Zaretskii" <eliz@gnu.org>,
	68200@debbugs.gnu.org
Subject: bug#68200: 30.0.50; Emacs reloads init file when calling `documentation'
Date: Mon, 8 Jan 2024 21:22:16 +0000	[thread overview]
Message-ID: <ZZxniDKON97bG_ew@ACM> (raw)
In-Reply-To: <877ckloxos.fsf@web.de>

Hello, Michael.

On Sun, Jan 07, 2024 at 18:33:39 +0100, Michael Heerdegen wrote:
> Eli Zaretskii <eliz@gnu.org> writes:

> > > 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.

> Looks like

>   6a01a1a856f ".elc format: Record lambdas' doc strings lazily, not
>   inline" (Alan Mackenzie <acm@muc.de> 2023-11-26)

> would be related.

> Alan, could this be the case?

Yes, I think it could.  I've not yet got my brain into that commit from
November (which was quite a long time ago), but ....

In an age when a computer with 1 GB RAM is regarded as small indeed, why
are we so concerned about the, at most, few hundred bytes occupied by
each doc string?  Even if certain libraries were given adequate doc
strings, that still wouldn't swell the occupied storage to more than...
Well, I think there are around 40,000 defuns (etc.) in Emacs (I did scan
the source files for this at one time).  If each doc string were on
average 1024 bytes, that would come to around 40 MB.  That's negligible
these days, surely.

Eli, what would you say to changing the default of the custom variable
byte-compile-dynamic-docstrings to nil?

And I'll have a look at why that variable no longer appears to be
working (though I have rather a lot on in the next few days).

> TIA,

> Michael.

-- 
Alan Mackenzie (Nuremberg, Germany).





  reply	other threads:[~2024-01-08 21:22 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
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 [this message]
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=ZZxniDKON97bG_ew@ACM \
    --to=acm@muc.de \
    --cc=68200@debbugs.gnu.org \
    --cc=eliz@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).