GNU bug report logs -
#68200
File local byte-compile-dynamic-docstrings:nil ignored?
Previous Next
Full log
View this message in rfc822 format
Hello, Eli.
On Thu, Jan 11, 2024 at 21:22:08 +0200, Eli Zaretskii wrote:
> > Date: Thu, 11 Jan 2024 18:10:58 +0000
> > Cc: michael_heerdegen <at> web.de, gerd.moellmann <at> gmail.com, 68200 <at> debbugs.gnu.org,
> > acm <at> muc.de
> > From: Alan Mackenzie <acm <at> muc.de>
> > > No, 40MB is far from being negligible.
> > It's not negligible compared with the rest of Emacs, but is less than ΒΌ%
> > of the RAM in a machine with 16GB.
> No, it isn't, because most of those 16GB are in use at any given
> moment.
I'm sure they're not on my machine. But I'm glad RAM is now measured in
GB, not MB.
> > No, the bug has been fixed. But, as Michael pointed out, lots of things
> > are being done with doc strings now which weren't being done when the
> > dynamic doc strings were introduced. Indeed, they were surely a
> > workaround for limited RAM in machines a very long time ago.
> > Now that we're doing more with doc strings, the inconvenience of not
> > getting a doc string after editing a source file might well outweigh the
> > relatively small amount of RAM that these doc strings need.
> > Hence the suggestion to change the default.
> Since I disagree with your argument about memory being available for
> free, I also disagree with the suggestion that is based on that
> argument.
No problem. If I find annoyance with files continually reloading, like
Michael did, I can always set my own value of that variable.
Have a good evening!
--
Alan Mackenzie (Nuremberg, Germany).
This bug report was last modified 1 year and 187 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.