From: Po Lu <luangruo@yahoo.com>
To: Brian Cully <bjc@spork.org>
Cc: "Óscar Fuentes" <ofv@wanadoo.es>, emacs-devel@gnu.org
Subject: Re: master 5c532fe303: Recommend that the user turn off memory overcommit
Date: Fri, 08 Apr 2022 21:57:41 +0800 [thread overview]
Message-ID: <87wnfzr82y.fsf@yahoo.com> (raw)
In-Reply-To: <87lewfbsa0.fsf@ditto.jhoto.spork.org> (Brian Cully's message of "Fri, 08 Apr 2022 09:42:44 -0400")
Brian Cully <bjc@spork.org> writes:
> These features prevent Emacs from building, and I’d argue,
> constitute evidence of bugs in Emacs, as it’s operation is at odds with
> standard and necessary computer security. The wording in etc/PROBLEMS
> echoes this sentiment.
Whatever they might constitute, those changes might be required for
Emacs to build correctly.
> Your proposal crosses a line into how people should administer
> their systems even when Emacs functions as expected within the context
> of that system. ie, if I’m on Linux, overcommit is standard and I
> presumably know how to deal with it or am ignorant of it. In either
> event it is not the place of my text editor to tell me that memory
> overcommit is bad. There are countless opinion pieces on the web that
> will do that job just fine, should I seek them out.
None of this says that memory overcommit is "bad", it says that it's
detrimental to the correct functioning of Emacs. (And "correct" here
means memory_full being called before Emacs is killed by the OOM
killer.)
next prev parent reply other threads:[~2022-04-08 13:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <164941780605.21656.13343783431945268284@vcs2.savannah.gnu.org>
[not found] ` <20220408113647.815ACC051D6@vcs2.savannah.gnu.org>
2022-04-08 12:58 ` master 5c532fe303: Recommend that the user turn off memory overcommit Stefan Monnier
2022-04-08 13:23 ` Óscar Fuentes
2022-04-08 13:31 ` Po Lu
2022-04-08 13:42 ` Brian Cully
2022-04-08 13:57 ` Po Lu [this message]
2022-04-08 15:03 ` Stefan Monnier
2022-04-08 19:59 ` Eli Zaretskii
2022-04-08 13:46 ` Óscar Fuentes
2022-04-09 0:23 ` Po Lu
2022-04-09 1:28 ` Óscar Fuentes
2022-04-08 19:17 ` Eli Zaretskii
2022-04-09 4:17 ` Richard Stallman
2022-04-09 5:51 ` Tim Cross
2022-04-09 8:42 ` Phil Sainty
2022-04-09 9:08 ` Po Lu
2022-04-09 10:08 ` Phil Sainty
2022-04-09 10:27 ` Achim Gratz
2022-04-09 9:56 ` Eli Zaretskii
2022-04-09 10:28 ` Phil Sainty
2022-04-09 10:41 ` Eli Zaretskii
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=87wnfzr82y.fsf@yahoo.com \
--to=luangruo@yahoo.com \
--cc=bjc@spork.org \
--cc=emacs-devel@gnu.org \
--cc=ofv@wanadoo.es \
/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).