From: Phil Sainty <psainty@orcon.net.nz>
To: Po Lu <luangruo@yahoo.com>
Cc: emacs-devel@gnu.org, rms@gnu.org,
Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: master 5c532fe303: Recommend that the user turn off memory overcommit
Date: Sat, 09 Apr 2022 22:08:04 +1200 [thread overview]
Message-ID: <395240c80519f1bf37b3ca9e354c6ee5@webmail.orcon.net.nz> (raw)
In-Reply-To: <87wnfyoc8l.fsf@yahoo.com>
On 2022-04-09 21:08, Po Lu wrote:
> It is random, from the perspective of the user, who eventually
> develops the sinking feeling that the kernel might not kill
> IceCat but Emacs the next time it happens.
It's one thing for the user to mistakenly believe that
something is random, and it's quite another thing for our
documentation to explicitly tell them that is the case.
Describing it as "random" helps nobody and is misleading.
(I think that doing so has already misled some of the
people reading this mailing list.)
The process can still be described (in a less-misleading way),
and references to documentation can be made to inform users.
next prev parent reply other threads:[~2022-04-09 10:08 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
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 [this message]
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=395240c80519f1bf37b3ca9e354c6ee5@webmail.orcon.net.nz \
--to=psainty@orcon.net.nz \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.com \
--cc=monnier@iro.umontreal.ca \
--cc=rms@gnu.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).