From: Noam Postavsky <npostavs@gmail.com>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Boruch Baum <boruch_baum@gmx.com>, 31091@debbugs.gnu.org
Subject: bug#31091: 25.2: Feature Request: auto exit upon memory exhaustion warning
Date: Sun, 08 Apr 2018 12:31:41 -0400 [thread overview]
Message-ID: <87in91mzgy.fsf@gmail.com> (raw)
In-Reply-To: <87sh85ekj6.fsf@linux-m68k.org> (Andreas Schwab's message of "Sun, 08 Apr 2018 18:21:33 +0200")
Andreas Schwab <schwab@linux-m68k.org> writes:
> On Apr 08 2018, Eli Zaretskii <eliz@gnu.org> wrote:
>
>>> Not my experience today / last night.
>>
>> You are experiencing a particular nasty bug.
>
> The only bug is that apropos-value uses a sub-optimal implementation
> that produces a lot of data.
No, it's probably Bug#26952, as I mentioned earlier.
next prev parent reply other threads:[~2018-04-08 16:31 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-08 7:22 bug#31091: 25.2: Feature Request: auto exit upon memory exhaustion warning Boruch Baum
2018-04-08 7:51 ` Andreas Schwab
2018-04-08 7:59 ` Boruch Baum
2018-04-08 8:36 ` Andreas Schwab
2018-04-08 8:46 ` Boruch Baum
2018-04-08 11:24 ` Andreas Schwab
2018-04-08 11:49 ` Boruch Baum
2018-04-08 16:10 ` Andreas Schwab
2018-04-08 16:17 ` Boruch Baum
2018-04-08 17:28 ` Andreas Schwab
2022-04-24 14:25 ` Lars Ingebrigtsen
2018-04-08 12:58 ` Eli Zaretskii
2018-04-08 13:21 ` Boruch Baum
2018-04-08 13:57 ` Eli Zaretskii
2018-04-08 16:21 ` Andreas Schwab
2018-04-08 16:31 ` Noam Postavsky [this message]
2018-04-08 16:37 ` Eli Zaretskii
2018-04-08 13:25 ` Noam Postavsky
2018-04-08 13:53 ` Boruch Baum
2018-04-08 15:27 ` Noam Postavsky
2018-04-08 15:54 ` Boruch Baum
2018-04-08 16:13 ` Andreas Schwab
2018-04-08 16:30 ` Noam Postavsky
2018-04-08 16:58 ` Boruch Baum
2018-04-08 17:26 ` Noam Postavsky
[not found] ` <20180408181013.6hw7ec3fi2dvfeja@E15-2016.optimum.net>
2018-04-08 21:58 ` bug#31091: [OFFLIST] " Noam Postavsky
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87in91mzgy.fsf@gmail.com \
--to=npostavs@gmail.com \
--cc=31091@debbugs.gnu.org \
--cc=boruch_baum@gmx.com \
--cc=schwab@linux-m68k.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.