all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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 10:39:38 +0100	[thread overview]
Message-ID: <87bldtqip1.fsf@gmail.com> (raw)
In-Reply-To: <87a6tdyyn0.fsf@mat.ucm.es> (Uwe Brauer's message of "Wed, 13 Jan 2021 10:28:03 +0100")

Uwe Brauer <oub@mat.ucm.es> writes:

>> So itʼs explicitly documented that 'local-abbrev-table' can be a
>> *list* of abbrev tables, but lots of the abbrev code assumes that
>> it gets passed a single table.
>
>> Itʼs easy enough to check for 'consp' in such cases, but then which of
>> tables in that list should we add the abbrev to? The first one? All of
>> them?
>
>> Iʼm leaning towards "first, and document that you should put the most
>> specific table at the front of the list of local abbrev tables", but
>> Iʼd welcome opinions from others.
>
> I am not entirely sure, I understand the logic behind this. To give you
> a concrete example. (That enters now the flyspell problem).
>
> I have defined for each language I use flypsell/ispell a minor mode and
> a corresponding local-abbrev table.
>
>     1. American
>
>     2. British
>
>     3. German
>
>     4. Spanish
>
>     5. French
>
>     6. And even Hebrew (but we can leave that may out for the moment).
>
> Now say I am in latex mode and turn spelling for American on (which in
> turn turn the minor mode american-spelling on), is then the local abbrev
> table the first in that list?

Thatʼs under the control of your code, no? Itʼs whatever does 'setq
local-abbrev-table (list ... ...)'

Robert





  reply	other threads:[~2021-01-13  9:39 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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87bldtqip1.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.