unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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 15:35:59 +0200	[thread overview]
Message-ID: <m3h87qoy4g.fsf@gnus.org> (raw)
In-Reply-To: <81bd4ae4-60de-7a64-24e6-d6e43c89c13f@g.nevcal.com> (Glenn Linderman's message of "Fri, 12 Jul 2019 20:48:26 -0700")

Glenn Linderman <v+python@g.nevcal.com> writes:

> I think you understood correctly.  I'm not sure what version of which
> Python-mode I have, but could probably figure it out somehow (I love emacs,
> because it has extensions, but I'm not real good at writing or understanding
> elisp: I use other people's extensions, mostly, and a bit of cut-n-paste
> programming for a few more customizations).
>
> Probably the following message, that I get every time I open the file.
>
> "Warning: no abbrev-file found, customize `abbrev-file-name' in order to make
> mode-specific abbrevs work."

Right.  Some modes are chatty at startup and hides warnings you're
interested in.

It's perfectly valid to not want to load an autosaved file, and making
Emacs prompt would be an inconvenience, in my opinion.

Perhaps Emacs should treat auto-saved files a bit more like what it does
with files that have changed?  I.e., if you try to edit a file with an
auto-save file, it should prompt you something like "foo has auto save
data; really edit the buffer?" or something?

Would that make sense?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2019-07-13 13:35 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 [this message]
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=m3h87qoy4g.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 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).