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: Mon, 07 Feb 2022 05:13:22 +0100	[thread overview]
Message-ID: <87h79bxqjh.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:

> 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."

(I'm going through old bug reports that unfortunately weren't resolved
at the time.)

I can't find that message in the Emacs tree, so I guess it's coming from
a third party package?

In any case, I think we decided to not make recover-file into a prompt,
so I think the problem here really is that warning message, which seems
unhelpful and excessive.  Therefore I don't really think there's
anything much to be done on the Emacs side, and I'm closing this bug report.

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





      parent reply	other threads:[~2022-02-07  4:13 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
2022-02-07  4:13         ` Lars Ingebrigtsen [this message]

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=87h79bxqjh.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).