From: Robert Pluim <rpluim@gmail.com>
To: Uwe Brauer <oub@mat.ucm.es>
Cc: larsi@gnus.org, 45693@debbugs.gnu.org
Subject: bug#45693: [two word expansion works, but write-abbrev-file destroys it]
Date: Tue, 12 Jan 2021 18:59:22 +0100 [thread overview]
Message-ID: <87y2gyxchx.fsf@gmail.com> (raw)
In-Reply-To: <87h7nmumrq.fsf@mat.ucm.es> (Uwe Brauer's message of "Tue, 12 Jan 2021 17:45:45 +0100")
Uwe Brauer <oub@mat.ucm.es> writes:
>> Uwe Brauer <oub@mat.ucm.es> writes:
>
>> What's your 'abbrev-file-name' set to? Emacs uses 'load' to read it,
>> so it should be a complete pathname, ie "~/.abbrev_defs", or it should
>> be in your 'load-path' somewhere.
>
> Good and bad news. I repeated the test carefully looking around for old
> abbrev.el or .abbrev_defs file.
>
> 1. Good, I can confirm that your patched abbrev.el works in the
> sense that write-abbrev-file does not destroy the properties of
> the table.
>
> 2. However I tried to add a local abbrev (or an inverse local
> abbrev) in the fundamental mode, but I obtain
>
> obarray-get: Wrong type argument: vectorp, ([## 0 0 0 0 0 0 0 0 0 ...] [## 0 0 0 0 0 0 0 0 0 ...]) [2 times]
Could you tell me exactly what you did? I suspect there are more
places that are not aware of the :parents property that need fixing.
> That is maybe the reason I run into difficulties if I want to use
> flyspell's abbrev mode if a correction occurs.
I donʼt use flyspell. Tell me more and we can look at fixing that as
well.
Robert
next prev parent reply other threads:[~2021-01-12 17:59 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-06 15:54 bug#45693: 28.0.50; abbrev does not expand two words any more Uwe Brauer
2021-01-10 14:35 ` Lars Ingebrigtsen
2021-01-10 15:51 ` Uwe Brauer
2021-01-10 15:52 ` Lars Ingebrigtsen
2021-01-10 17:22 ` Uwe Brauer
2021-01-10 21:21 ` bug#45693: [two word expansion works, but write-abbrev-file destroys it] (was: bug#45693: 28.0.50; abbrev does not expand two words any more) Uwe Brauer
2021-01-11 10:49 ` bug#45693: [two word expansion works, but write-abbrev-file destroys it] Robert Pluim
2021-01-11 15:26 ` Eli Zaretskii
2021-01-11 15:50 ` Uwe Brauer
2021-01-11 17:38 ` Robert Pluim
2021-01-11 20:17 ` Uwe Brauer
2021-01-11 20:38 ` Robert Pluim
2021-01-11 20:48 ` Uwe Brauer
2021-01-11 21:03 ` Robert Pluim
2021-01-12 8:01 ` Uwe Brauer
2021-01-12 10:34 ` Robert Pluim
2021-01-12 13:26 ` Uwe Brauer
2021-01-12 16:45 ` Uwe Brauer
2021-01-12 17:59 ` Robert Pluim [this message]
2021-01-13 7:37 ` Uwe Brauer
2021-01-13 9:16 ` Robert Pluim
2021-01-13 9:28 ` Uwe Brauer
2021-01-13 9:39 ` Robert Pluim
2021-01-13 9:51 ` Uwe Brauer
2021-01-13 10:09 ` Robert Pluim
2021-01-13 13:18 ` Uwe Brauer
2021-01-13 14:03 ` Robert Pluim
2021-01-13 16:25 ` Uwe Brauer
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=87y2gyxchx.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=45693@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=oub@mat.ucm.es \
/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).