From: ishikawa <chiaki.ishikawa@ubin.jp>
To: "Kim F. Storm" <storm@cua.dk>
Cc: emacs-devel@gnu.org
Subject: Re: A new(?) warning of erase-buffer, which was not seen before.
Date: Thu, 22 Mar 2007 20:08:10 +0900 [thread overview]
Message-ID: <4602639A.8030606@ubin.jp> (raw)
In-Reply-To: <m31wjk2quo.fsf@kfs-l.imdomain.dk>
Kim F. Storm wrote:
> ishikawa <chiaki.ishikawa@ubin.jp> writes:
>
>> It is only that I am a little puzzled that I didn't get this warning
>> in the previous versions 21.x (and prior), and I am wondering
>> if there is a better memory allocation/checking introduced in 22.0
>> which causes this warning to appear. In the older versions, say 21.x
>> (and prior), I have not seen this message.
>
> Those warnings are new in Emacs 22.
>
> In Emacs 21 and before, there is a risk of running out of memory and
> Emacs crashing.
>
> In Emacs 22, more checks and automatic measures like undo-outer-limit
> have been added to prevent running out of memory, and to give feedback
> to the user when those measures kick in.
>
> Here's what C-h C-n (aka NEWS) says about it:
>
> ** When the undo information of the current command gets really large
> (beyond the value of `undo-outer-limit'), Emacs discards it and warns
> you about it.
>
Thank you again.
After tinkering with new emacs, here is my suggestion for a slight improvement
for the particular warning message.
AT the end (that is,
after "You can disable the popping up of this buffer by adding the entry
(undo discard-info) to the user option `warning-suppress-types'."),
we might want to add something like the following (as rms suggested):
"
If you know what you are doing, and you don't want the buffer
to collect undo information which uses memory internally,
do M-x buffer-disable-undo, or (setq buffer-undo-list t)."
next prev parent reply other threads:[~2007-03-22 11:08 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-19 2:20 A new(?) warning of erase-buffer, which was not seen before ishikawa
2007-03-19 12:19 ` Kim F. Storm
2007-03-20 3:48 ` ishikawa
2007-03-20 9:42 ` Kim F. Storm
2007-03-22 11:08 ` ishikawa [this message]
2007-03-22 22:50 ` Richard Stallman
2007-03-22 23:21 ` Miles Bader
2007-03-23 9:47 ` ishikawa
2007-03-23 14:52 ` Davis Herring
2007-03-23 9:54 ` Johan Bockgård
2007-03-23 11:31 ` Miles Bader
2007-03-23 12:56 ` Johan Bockgård
2007-03-23 16:54 ` Stefan Monnier
2007-03-23 17:01 ` Lennart Borgman (gmail)
2007-03-23 17:35 ` martin rudalics
2007-03-24 2:41 ` Miles Bader
2007-03-24 9:09 ` martin rudalics
2007-03-19 18:10 ` Richard Stallman
2007-03-20 3:52 ` ishikawa
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=4602639A.8030606@ubin.jp \
--to=chiaki.ishikawa@ubin.jp \
--cc=emacs-devel@gnu.org \
--cc=storm@cua.dk \
/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).