From: Stefan Kangas <stefan@marxist.se>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 27748@debbugs.gnu.org, Ken Raeburn <raeburn@raeburn.org>,
Noam Postavsky <npostavs@gmail.com>,
Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#27748: 26.0.50; doc strings should be in DOC file
Date: Sat, 23 Oct 2021 10:32:22 -0700 [thread overview]
Message-ID: <CADwFkmk2ixFq_j3zUJGVcv2iQSQ7jDvnNrWcM=NuNZMNDfzK_w@mail.gmail.com> (raw)
In-Reply-To: <878rzjlx4n.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sun, 26 Sep 2021 07:32:56 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Stefan Kangas <stefan@marxist.se> writes:
>
>> FWIW, I think we should get rid of it. Stefan M did an analysis of this
>> and the amount of saved memory was very small, from bytecomp.el:
>
> [...]
>
>> ;; (at the cost of around 24KB on 32bit hosts, double on 64bit
>> ;; hosts)
>
> Yes, that seems pretty insignificant.
If getting rid of DOC is what we want to eventually do, we should
probably just close this as wontfix. It hardly seems worth fixing such
problems in an area that we basically want to get rid of anyway.
next prev parent reply other threads:[~2021-10-23 17:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-18 6:47 bug#27748: 26.0.50; doc strings should be in DOC file Ken Raeburn
2017-08-06 0:09 ` npostavs
2017-08-08 1:03 ` npostavs
2017-08-13 18:04 ` npostavs
2019-06-24 22:38 ` Lars Ingebrigtsen
2019-06-24 23:00 ` Noam Postavsky
2020-08-10 15:00 ` Lars Ingebrigtsen
2021-05-10 12:09 ` Lars Ingebrigtsen
2021-09-25 15:41 ` Stefan Kangas
2021-09-26 5:32 ` Lars Ingebrigtsen
2021-10-23 17:32 ` Stefan Kangas [this message]
2021-10-24 12:59 ` Lars Ingebrigtsen
2017-08-20 22:05 ` npostavs
2017-08-29 10:09 ` Ken Raeburn
2017-08-31 0:50 ` npostavs
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='CADwFkmk2ixFq_j3zUJGVcv2iQSQ7jDvnNrWcM=NuNZMNDfzK_w@mail.gmail.com' \
--to=stefan@marxist.se \
--cc=27748@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
--cc=npostavs@gmail.com \
--cc=raeburn@raeburn.org \
/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).