From: "Jared Finder" <jfinder@crypticstudios.com>
To: "Glenn Morris" <rgm@gnu.org>, <emacs-devel@gnu.org>
Subject: RE: TAGS buffer generates spurious undo warnings
Date: Thu, 1 Nov 2007 13:47:39 -0700 [thread overview]
Message-ID: <75DAF0131F83954E9E91C128EF9C7D838A4F64@galaxy.paragon.crypticstudios.com> (raw)
In-Reply-To: <wo4pg5u54i.fsf@fencepost.gnu.org>
Still happens, but I have not been able to track down why. Ct happens
on my work box on Win32, but not on my Debian box at home. Also, it
only happens if I load my .emacs, even though I'm using the exact same
.emacs at home and at work.
-- MJF
-----Original Message-----
From: Glenn Morris [mailto:rgm@gnu.org]
Sent: Thursday, November 01, 2007 12:40 PM
To: emacs-devel@gnu.org
Cc: Jared Finder
Subject: TAGS buffer generates spurious undo warnings
Jared Finder wrote:
> Re-loading a really large TAGS buffer generates a spurious warning
> about undo info being discarded. TAGS buffers have no need for undo
> info! Why not just disable undo in TAGS and BROWSE and similar
buffers?
Can anyone see how this could happen?
It may be obvious, but I looked at the code and couldn't see how such
a wanring would come about. I'm reluctant to disable undo just for the
sake of it...
(Undo in BROWSE has already been disabled AFAIK.)
next prev parent reply other threads:[~2007-11-01 20:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-01 19:39 TAGS buffer generates spurious undo warnings Glenn Morris
2007-11-01 20:47 ` Jared Finder [this message]
2007-11-02 2:07 ` Richard Stallman
2007-11-02 8:19 ` Glenn Morris
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=75DAF0131F83954E9E91C128EF9C7D838A4F64@galaxy.paragon.crypticstudios.com \
--to=jfinder@crypticstudios.com \
--cc=emacs-devel@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 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).