From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Jean-Christophe Helary <lists@traduction-libre.org>
Cc: help-gnu-emacs <help-gnu-emacs@gnu.org>
Subject: Re: non word abbrevs
Date: Sat, 06 Nov 2021 18:32:59 -0400 [thread overview]
Message-ID: <jwv7ddkc40t.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <2067AA83-8EC0-4429-9189-9E3CCCFD06BB@traduction-libre.org> (Jean-Christophe Helary's message of "Sat, 6 Nov 2021 17:20:58 +0900")
Jean-Christophe Helary [2021-11-06 17:20:58] wrote:
> Ok, so this time I try your regexp (thank you by the way):
>> On Nov 1, 2021, at 21:13, Jean-Christophe Helary <lists@traduction-libre.org> wrote:
> (define-abbrev-table 'arrows-abbrev-table
> '(("->" "→")
> ("<-" "←")
> ("<->" "⇆")
> ("==>" "⇒")
> ("<==" "⇐")
> ("<=>" "⇔")
> )
> "Arrows as defined on my macOS side."
> :regexp "[^<>=-]\\([<>=-]+\\)")
>
> (setq local-abbrev-table arrows-abbrev-table)
>
> and I have the abbrev-mode enabled in the *scratch* buffer where I run
> that, and nothing happens when I type -> for ex... 😢
I tried the above and then `M-x expand-abbrev` and it worked for my test
case, so I guess the problem is in the auto-triggering of abbrevs down
in `self-insert-command`.
And indeed I see:
if (!NILP (BVAR (current_buffer, abbrev_mode))
&& synt != Sword
&& NILP (BVAR (current_buffer, read_only))
&& PT > BEGV
&& (SYNTAX (!NILP (BVAR (current_buffer, enable_multibyte_characters))
? XFIXNAT (Fprevious_char ())
: UNIBYTE_TO_CHAR (XFIXNAT (Fprevious_char ())))
== Sword))
so it looks like the "auto expand abbrev" feature only works right after
a word char, so basically only works for abbrevs whose last char has
word syntax.
You might want to `M-x report-emacs-bug` and request that this
constraint be made more flexible.
Stefan
next prev parent reply other threads:[~2021-11-06 22:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-31 5:45 non word abbrevs Jean-Christophe Helary
2021-10-31 19:04 ` Stefan Monnier via Users list for the GNU Emacs text editor
2021-11-01 7:57 ` Jean-Christophe Helary
2021-11-01 10:54 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-11-01 12:03 ` Stefan Monnier
2021-11-01 12:13 ` Jean-Christophe Helary
2021-11-01 12:43 ` Stefan Monnier via Users list for the GNU Emacs text editor
2021-11-01 13:17 ` Jean-Christophe Helary
2021-11-01 13:49 ` Leo Butler
2021-11-01 14:03 ` tomas
2021-11-01 17:58 ` Stefan Monnier
2021-11-06 8:20 ` Jean-Christophe Helary
2021-11-06 22:32 ` Stefan Monnier [this message]
2021-11-07 0:01 ` Jean-Christophe Helary
2021-11-07 3:15 ` Stefan Monnier via Users list for the GNU Emacs text editor
2021-11-07 3:24 ` Jean-Christophe Helary
2021-11-07 4:11 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-11-08 5:36 ` Kevin Vigouroux via Users list for the GNU Emacs text editor
2021-11-08 7:18 ` Jean-Christophe Helary
2021-11-08 23:29 ` Stefan Monnier via Users list for the GNU Emacs text editor
2021-11-07 4:06 ` Emanuel Berg via Users list for the GNU Emacs text editor
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=jwv7ddkc40t.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=help-gnu-emacs@gnu.org \
--cc=lists@traduction-libre.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).