From: "Richard M. Stallman" <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: "No further undo information" clutters *Messages* buffer
Date: Wed, 26 Oct 2005 21:30:22 -0400 [thread overview]
Message-ID: <E1EUwb0-0003fz-H1@fencepost.gnu.org> (raw)
In-Reply-To: <435F7197.1080108@gmx.at> (message from martin rudalics on Wed, 26 Oct 2005 14:07:51 +0200)
Eventually
Undo!
undo-more: No further undo information
occupied more than 90% of my `*Messages*' buffer which made it quite
difficult to trace more interesting error messages.
How did that happen? From one sequence of undos, you'll only
get one such message. So you must have done lots of sequences
of undos, and in each one, continued until you got an error.
It's not impossible, but it is strange and probably unusual.
Can you show us a complete, precise test case?
Ideally, I wanted `undo' issue `Undo...', `Redo...', etc. first. If the
operation succeeded it would display `Undo...done', `Redo...done', etc.
Otherwise, it would issue `Undo...', `Redo...', etc. with the according
error text appended. In any case `message_log_check_duplicate' would
take care of the rest.
It already combines duplicate Undo! messages, so that you end up
with at most one of them from any sequence of undos.
next prev parent reply other threads:[~2005-10-27 1:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-24 8:21 "No further undo information" clutters *Messages* buffer martin rudalics
2005-10-25 15:59 ` Richard M. Stallman
2005-10-26 12:07 ` martin rudalics
2005-10-26 16:11 ` Kevin Rodgers
2005-10-27 1:30 ` Richard M. Stallman [this message]
2005-10-29 9:24 ` martin rudalics
2005-10-29 20:33 ` Richard M. Stallman
2005-11-01 9:42 ` martin rudalics
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=E1EUwb0-0003fz-H1@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@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.