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: Sat, 13 Jul 2019 04:42:55 +0200 [thread overview]
Message-ID: <87sgrazmc0.fsf@mouse.gnus.org> (raw)
In-Reply-To: <4cb978b3-9453-29c5-4757-4ef804bf5c54@g.nevcal.com> (Glenn Linderman's message of "Wed, 29 Aug 2018 21:34:52 -0700")
Glenn Linderman <v+python@g.nevcal.com> writes:
> I have emacs open a certain large file at boot-time startup, because
> the Python mode takes so long to parse it. So I guess I forgot to save
> last night, did a windows shutdown, and this morning my work wasn't
> there... but while emacs probably gave the warning, it was probably
> wiped out by the next warning from the Python mode, and I don't sit
> there and watch my computer boot up. So by the time I noticed stuff
> from last night was missing, the recover file had been rewritten with
> the new edits.
If I understand you correctly (and I may not), you're saying that when
you open a Python file that has an auto-saved file, then Emacs says that
an auto-saved file exists... and then Python mode issues a message that
overwrites that message?
What is that Python-mode message?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2019-07-13 2:42 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 [this message]
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
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
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=87sgrazmc0.fsf@mouse.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 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).