From: Drew Adams <drew.adams@oracle.com>
To: Michael Heerdegen <michael_heerdegen@web.de>, hw <hw@adminart.net>
Cc: Help GNU Emacs <help-gnu-emacs@gnu.org>
Subject: RE: [External] : Re: how to force auto-save of buffers not visiting files, right now?
Date: Wed, 16 Mar 2022 01:45:41 +0000 [thread overview]
Message-ID: <SJ0PR10MB5488F6A49E651E85AA7214BBF3119@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <87zglq200a.fsf@web.de>
> Normally you should be able to `undo' if
> something went wrong. Even when the buffer
> has no associated file.
Yes. Yet another reason that buffers such as
*Pp Eval Output*, and even read-only buffers
such as *Messages*, should have undo by default.
Visited buffers are sometimes usefully edited.
We're not gaining much nowadays, I think, by
omitting undo from such buffers by default.
(In `pp+.el' I added undo to *Pp Eval Output*,
at least.)
next prev parent reply other threads:[~2022-03-16 1:45 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-14 4:55 how to force auto-save of buffers not visiting files, right now? hw
2022-03-14 12:48 ` Eli Zaretskii
2022-03-15 5:20 ` hw
2022-03-15 6:47 ` Jean Louis
2022-03-15 7:24 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-03-17 4:35 ` hw
2022-03-17 5:00 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-03-18 7:31 ` hw
2022-03-18 14:45 ` [External] : " Drew Adams
2022-03-19 2:33 ` hw
2022-03-19 2:38 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-03-15 14:07 ` Eli Zaretskii
2022-03-16 0:51 ` Michael Heerdegen
2022-03-16 1:45 ` Drew Adams [this message]
2022-03-17 19:23 ` hw
2022-03-17 22:07 ` Michael Heerdegen
2022-03-18 8:28 ` hw
2022-03-19 1:18 ` Michael Heerdegen
2022-03-19 3:14 ` hw
2022-03-19 3:47 ` Michael Heerdegen
2022-03-19 6:24 ` hw
2022-03-19 7:34 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-03-19 7:51 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-03-20 6:02 ` hw
2022-03-20 6:26 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-03-19 9:58 ` Michael Albinus
2022-03-20 6:36 ` hw
2022-03-20 7:04 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-03-21 16:22 ` [External] : " Drew Adams
2022-03-20 7:29 ` tomas
2022-03-20 8:05 ` volatile /tmp [was: how to force auto-save of buffers not visiting files, right now?] tomas
2022-03-20 10:36 ` hw
2022-03-20 11:13 ` tomas
2022-03-21 3:41 ` hw
2022-03-21 5:53 ` tomas
2022-03-21 8:47 ` Michael Albinus
2022-03-20 9:57 ` how to force auto-save of buffers not visiting files, right now? Michael Albinus
2022-03-20 10:21 ` tomas
2022-03-20 10:19 ` hw
2022-03-20 10:30 ` tomas
2022-03-21 3:55 ` hw
2022-03-21 4:13 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-03-21 12:22 ` Eli Zaretskii
2022-03-23 6:12 ` hw
2022-03-23 9:25 ` Michael Albinus
2022-03-20 0:21 ` Michael Heerdegen
2022-03-20 4:56 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-03-20 7:39 ` hw
2022-03-20 8:08 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-03-22 7:06 ` hw
2022-03-22 19:50 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-03-22 21:45 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-03-21 7:22 ` Jean Louis
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=SJ0PR10MB5488F6A49E651E85AA7214BBF3119@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=help-gnu-emacs@gnu.org \
--cc=hw@adminart.net \
--cc=michael_heerdegen@web.de \
/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.
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).