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: Wed, 13 Jan 2021 15:03:07 +0100 [thread overview]
Message-ID: <87sg75ue78.fsf@gmail.com> (raw)
In-Reply-To: <87pn29x9ea.fsf@mat.ucm.es> (Uwe Brauer's message of "Wed, 13 Jan 2021 14:18:37 +0100")
>>>>> On Wed, 13 Jan 2021 14:18:37 +0100, Uwe Brauer <oub@mat.ucm.es> said:
>> Uwe Brauer <oub@mat.ucm.es> writes:
>> Based on the code above, there is no list: youʼre unconditionally
>> setting local-abbrev-table to a single table. You'd want something
>> like:
>> (define-minor-mode american-minor-mode
>> nil nil nil nil
>> (setq local-abbrev-table
>> (if american-minor-mode
>> (list american-minor-mode-abbrev-table local-abbrev-table))))
Uwe> Ok I did not think that through, you were referring to
Uwe> (setq local-abbrev-table (list my-abbrev-table fundamental-mode-abbrev-table))
Uwe> And the question is what comes first in that list, right?
Uwe> You asked whether to take the first or all elements of the list, would
Uwe> it be very resource consuming to take all?
Not really, but people might find it confusing when 'add a local
abbrev' results in modifying more than one abbrev table.
Robert
next prev parent reply other threads:[~2021-01-13 14:03 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
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 [this message]
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=87sg75ue78.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).