From: "Daniel Colascione" <dancol@dancol.org>
To: 31852@debbugs.gnu.org, eggert@cs.ucla.edu, eggert@cs.ucla.edu
Subject: bug#31852: Make memory-limit obsolete
Date: Sat, 16 Jun 2018 08:51:47 -0700 [thread overview]
Message-ID: <be5dfedf4cf34b2a51f7999e36d03e00.squirrel@dancol.org> (raw)
In-Reply-To: <e621adb5-7caf-256f-35cc-6c51979cfd05@cs.ucla.edu>
> Eli Zaretskii wrote:
>
>> If nobody uses the function, I see no gain at all, because obsoleting
>> a function tells those who use it not to.
>
> If Emacs has useless and confusing features that consume documentation
> space and
> implementation resources, that is a net harm to current and future users.
> Omitting such features is therefore a net gain to users. The benefit to
> users by
> omitting useless and confusing features is worth the maintenance cost to
> us of
> obsoleting these features.
>
> That being said, it appears I haven't convinced you to obsolete
> memory-limit, so
> I installed patch 1 but not patch 2 and am closing the bug report.
I agree with obsoleting memory-limit. I don't like the vsize patch you
installed though: what does the amount of address space reserved actually
tell anyone? There's no relationship to actual resource consumption.
IMHO, memory-limit should return a combination of the Lisp heap size with
whatever malloc says is its own heap size.
next prev parent reply other threads:[~2018-06-16 15:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-16 1:33 bug#31852: Make memory-limit obsolete Paul Eggert
2018-06-16 6:31 ` Eli Zaretskii
2018-06-16 13:38 ` Paul Eggert
2018-06-16 15:02 ` Eli Zaretskii
2018-06-16 15:34 ` Paul Eggert
2018-06-16 15:51 ` Daniel Colascione [this message]
2018-06-16 16:27 ` Paul Eggert
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=be5dfedf4cf34b2a51f7999e36d03e00.squirrel@dancol.org \
--to=dancol@dancol.org \
--cc=31852@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
/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).