unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Emanuel Berg via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: non word abbrevs
Date: Sun, 07 Nov 2021 05:11:57 +0100	[thread overview]
Message-ID: <871r3sob8y.fsf@zoho.eu> (raw)
In-Reply-To: B6E5EBFC-D563-48C6-AF58-57206E98F954@traduction-libre.org

Jean-Christophe Helary wrote:

>> On Nov 7, 2021, at 12:15, Stefan Monnier via Users list for
>> the GNU Emacs text editor <help-gnu-emacs@gnu.org> wrote:
>
>> Not completely: the original motivation for adding that `:regexp`
>> keyword was to handle abbrevs of the form "`foo" as well as others of
>> the form "foo/bar" ;-)
>
> And the overall feature seems severely under-documented...
> Honestly, I barely understood your explanations...

It doesn't execute if the last char is for example a dash ...

Try an abbrev that is "a-b" (not "a to b", the chars a, dash,
and b), the "a-b" abbrev will work as b is the last char, not
the dash this time.

(dash is "HYPHEN-MINUS" officially :))

> Maybe expecting to have abbrevs work way was a mistake, but
> it does not seem possible to have (easy...) arbitrary string
> expansion in out-of-the-box-emacs without abbrevs.

It is easy! Try setup an abbrev that is "aaaz" to "bbbz", with
the punctuation chars it doesn't work since it doesn't
trigger, that's a bug, good work YOU for finding it! Your code
works fine with "aaaz" to "bbbz", well, details aside since
you tried to do something else.

> Would there be another more idiomatic way ?

No, you did it the right way, Emacs did it the wrong way, but
as long as we have our captain going at - I don't know how
many percent? - but surely plenty enough to fix these kind of
bugs :)

-- 
underground experts united
https://dataswamp.org/~incal




  reply	other threads:[~2021-11-07  4:11 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
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 [this message]
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=871r3sob8y.fsf@zoho.eu \
    --to=help-gnu-emacs@gnu.org \
    --cc=moasenwood@zoho.eu \
    /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).