From: Richard Stallman <rms@gnu.org>
To: Miles Bader <miles@gnu.org>
Cc: rgm@gnu.org, lennart.borgman@gmail.com, emacs-devel@gnu.org
Subject: Re: The *Warnings* buffer and undo
Date: Sat, 31 Mar 2007 16:43:00 -0400 [thread overview]
Message-ID: <E1HXkPc-0003eR-R2@fencepost.gnu.org> (raw)
In-Reply-To: <87ejn6z6qr.fsf@catnip.gol.com> (message from Miles Bader on Sat, 31 Mar 2007 07:50:04 +0900)
I don't know about the *Warning* buffer (I don't think I've ever even seen
it), but in the case of comint:
(1) If you use `comint-truncate-buffer' (in comint-output-filter-functions)
to keep comint buffers from getting too big (and in many cases it's a
very good idea), a line gets deleted at the beginning of the buffer for
every new line that gets inserted at the end, which can use massive
amounts of space in the undo list.
Perhaps `comint-truncate-buffer' should discard its own undo entries.
It could use `inhibit-undo', if we add such a feature.
Alternatively we could add a feature which says, "discard this undo entry,
and fix up the older entries so that they still work." That could
be written in Lisp.
next prev parent reply other threads:[~2007-03-31 20:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-24 20:01 The *Warnings* buffer and undo Lennart Borgman (gmail)
2007-03-25 17:27 ` Richard Stallman
2007-03-28 0:47 ` Glenn Morris
2007-03-28 19:36 ` David Kastrup
2007-03-28 20:52 ` Glenn Morris
2007-03-29 17:59 ` Richard Stallman
2007-03-29 18:35 ` David Kastrup
2007-03-30 12:42 ` Richard Stallman
2007-03-30 19:18 ` Glenn Morris
2007-03-30 19:53 ` Lennart Borgman (gmail)
2007-03-31 7:20 ` Richard Stallman
2007-03-31 19:41 ` Glenn Morris
2007-03-31 23:21 ` Richard Stallman
2007-03-29 22:07 ` Miles Bader
2007-03-30 21:23 ` Richard Stallman
2007-03-30 21:45 ` Glenn Morris
2007-03-30 22:50 ` Miles Bader
2007-03-31 20:43 ` Richard Stallman [this message]
2007-04-01 0:22 ` Miles Bader
2007-04-01 0:44 ` Miles Bader
2007-03-29 15:32 ` Richard Stallman
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=E1HXkPc-0003eR-R2@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=lennart.borgman@gmail.com \
--cc=miles@gnu.org \
--cc=rgm@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 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.