From: Jean-Christophe Helary <lists@traduction-libre.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: help-gnu-emacs <help-gnu-emacs@gnu.org>
Subject: Re: non word abbrevs
Date: Mon, 1 Nov 2021 21:13:24 +0900 [thread overview]
Message-ID: <4097001A-F60D-4712-B828-EA778BFCF56E@traduction-libre.org> (raw)
In-Reply-To: <jwvv91cf5n8.fsf-monnier+emacs@gnu.org>
> On Nov 1, 2021, at 21:03, Stefan Monnier <monnier@iro.umontreal.ca> wrote:
>
>> :regexp "\(<?[-=]>?\)")
>> I must be missing something.
>
> Hmmm... backslashes? ;-)
> The above string is the same as "(<?[-=]>?)" (in recentish Emacsen the
> above backslashes should presumably be highlighted in
> a font-lock-warning color for that reason).
I'm trying in *scratch* with lisp-mode on a recent "master" and I don't get that...
> Beware also that this regexp is matched backwards and stops as soon as
> it finds a match, so it finds the *shortest* match rather than the
> longest match. IOW the <? part will always match the empty string.
I've changed it to:
:regexp "\\([<>=-]+\\)"
this time using:
(setq local-abbrev-table arrows-abbrev-table)
And I get a nice message that reads like this:
[## 0 0 0 0 0 0 0 0 0 0 <== <=> 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 ==> 0 0 0 0 0 0 0 0 0 <- 0 0 0 0 0 0 0 0 <-> 0 0 0 -> 0 0 0]
And I guess that's a list that includes possible matches but I'm not seeing => / <= so I wonder.
Then, I enable abbrev-mode but nothing gets transformed...
:-( Jean-Christophe
next prev parent reply other threads:[~2021-11-01 12:13 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 [this message]
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
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=4097001A-F60D-4712-B828-EA778BFCF56E@traduction-libre.org \
--to=lists@traduction-libre.org \
--cc=help-gnu-emacs@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).