From: Lars Ingebrigtsen <larsi@gnus.org>
To: Glenn Linderman <v+python@g.nevcal.com>
Cc: 32581@debbugs.gnu.org
Subject: bug#32581: 24.4; make recover-file a prompt instead of a warning
Date: Sun, 14 Jul 2019 14:50:46 +0200 [thread overview]
Message-ID: <m3y3104w61.fsf@gnus.org> (raw)
In-Reply-To: <7128dbb2-de2c-45e2-2cd6-fd55bc8bb6ab@g.nevcal.com> (Glenn Linderman's message of "Sat, 13 Jul 2019 19:10:56 -0700")
Glenn Linderman <v+python@g.nevcal.com> writes:
> This is a very interesting idea. It is only when you go to edit that
> you would lose the auto-save file, so that would be a "last-chance" to
> retrieve your data, and you would be interacting with the file at that
> point anyway, so a forced interaction would be less intrusive than at
> load time.
Yes, I think that warning about the auto-saved file when you try to edit
the new file has possibilities... I'm wondering whether there would be
any adverse effects somehow. Emacs has a number of things that warn
about editing files -- that it's changed on disk, or that another Emacs
process has the file locked, and now checking for auto-saved files in
the same area would perhaps add unforeseen complications.
But perhaps we should just try and see what it feels like in practice.
> My thought was more along the lines of some sort of message priority, where
> informational messages like the abbrev-file-name warning could not override a
> more important message... Of course, everyone thinks there message is most
> important, so that might be difficult to enforce or rank.
We do have a very primitive sort of message priority -- i.e., we have
some things that are so bad that we pop up the *Warnings* buffer. But I
think that's too intrusive for auto-saved files.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2019-07-14 12:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-30 4:34 bug#32581: 24.4; make recover-file a prompt instead of a warning Glenn Linderman
2019-07-13 2:42 ` Lars Ingebrigtsen
2019-07-13 3:48 ` Glenn Linderman
2019-07-13 13:35 ` Lars Ingebrigtsen
2019-07-13 16:26 ` Andreas Röhler
2019-07-14 12:55 ` Lars Ingebrigtsen
2019-07-14 17:06 ` Andreas Röhler
2019-07-14 17:18 ` Lars Ingebrigtsen
2019-07-14 2:10 ` Glenn Linderman
2019-07-14 12:50 ` Lars Ingebrigtsen [this message]
2022-02-07 4:13 ` Lars Ingebrigtsen
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=m3y3104w61.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=32581@debbugs.gnu.org \
--cc=v+python@g.nevcal.com \
/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.