From: Stefan Kangas <stefankangas@gmail.com>
To: Alan Mackenzie <acm@muc.de>,
Michael Heerdegen <michael_heerdegen@web.de>
Cc: "Gerd Möllmann" <gerd.moellmann@gmail.com>,
"Eli Zaretskii" <eliz@gnu.org>,
68200@debbugs.gnu.org
Subject: bug#68200: 30.0.50; Emacs reloads init file when calling `documentation'
Date: Thu, 11 Jan 2024 11:54:38 -0800 [thread overview]
Message-ID: <CADwFkmk17GLwU56u8H7d_Ok3Da-pwkj7nQfavSGrmk2hDrSxcg@mail.gmail.com> (raw)
In-Reply-To: <ZZxniDKON97bG_ew@ACM>
Alan Mackenzie <acm@muc.de> writes:
> 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?
Could you come up with a more accurate number? Maybe I'm missing
something, but 40 MB sounds like a lot to me. Most docstrings should be
much smaller than 1024 bytes (15 full rows with our 65 character width).
prev parent reply other threads:[~2024-01-11 19:54 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
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 [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=CADwFkmk17GLwU56u8H7d_Ok3Da-pwkj7nQfavSGrmk2hDrSxcg@mail.gmail.com \
--to=stefankangas@gmail.com \
--cc=68200@debbugs.gnu.org \
--cc=acm@muc.de \
--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).