From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: non-functioning abbrev mode
Date: Sun, 12 Jan 2020 21:43:45 +0200 [thread overview]
Message-ID: <837e1w795a.fsf@gnu.org> (raw)
In-Reply-To: <d8f5244f-b453-6d55-0cdf-f9af0e7466e8@mousecar.com> (message from ken on Sun, 12 Jan 2020 14:20:04 -0500)
> From: ken <gebser@mousecar.com>
> Date: Sun, 12 Jan 2020 14:20:04 -0500
>
> It must be twenty years now that I've been using abbrev mode, never with
> a problem. But a few days ago it ceased working. For instance, one
> common abbrev "wtih" is automatically replaced by "with". This has
> always worked fine. But now, although it says "Abbrev" on the status
> line, nothing happens when I type "wtih".
Crystal ball says your abbrev_defs file disappeared or got corrupted.
> Perhaps a related problem, the "abbrev-save" function appears to no
> longer exist.
There was never such a function in Emacs, AFAICT. Maybe it's
something you defined in your init files? There's a _variable_ named
save-abbrevs, though.
next prev parent reply other threads:[~2020-01-12 19:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-12 19:20 non-functioning abbrev mode ken
2020-01-12 19:43 ` Eli Zaretskii [this message]
2020-01-24 0:36 ` ken
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=837e1w795a.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=help-gnu-emacs@gnu.org \
/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).