From: Lars Ingebrigtsen <larsi@gnus.org>
To: "Andreas Röhler" <andreas.roehler@easy-emacs.de>
Cc: 15485@debbugs.gnu.org
Subject: bug#15485: add-abbrev: don't use hard-coded forward-word
Date: Wed, 14 Aug 2019 20:29:32 -0700 [thread overview]
Message-ID: <87pnl73y3n.fsf@mouse.gnus.org> (raw)
In-Reply-To: <524849DB.4090407@easy-emacs.de> ("Andreas \=\?utf-8\?Q\?R\=C3\=B6h\?\= \=\?utf-8\?Q\?ler\=22's\?\= message of "Sun, 29 Sep 2013 17:40:11 +0200")
Andreas Röhler <andreas.roehler@easy-emacs.de> writes:
> add-abbrev uses forward-word to catch the expansion, which isn't good
> for programming code.
>
> See
>
> http://stackoverflow.com/questions/19073674/how-can-i-add-my-personal-abbreviation-to-emmet-mode-in-emacs/19079683#19079683
>
> Suggest to use forward-symbol instead, or still better to make if customizable:
(I'm going through old bug reports that have unfortunately gotten no
responses yet.)
`add-abbrev' doesn't have a doc string itself, but as all the in-tree
callers of this function says:
---
Don't use this function in a Lisp program; use `define-abbrev' instead.
---
So you probably shouldn't use this programmatically, either.
However, it's possible that the `forward-word' should perhaps be
changed, but on the other hand, abbrev.el will probably be deprecated
any year now in favour of nabbrev.el, so I don't think it's a good idea
to change anything here, and I'm closing this bug report.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2019-08-15 3:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-29 15:40 bug#15485: add-abbrev: don't use hard-coded forward-word Andreas Röhler
2019-08-15 3:29 ` Lars Ingebrigtsen [this message]
2019-08-15 12:41 ` Mauro Aranda
2019-08-15 14:37 ` Andreas Röhler
2019-08-15 23:50 ` Lars Ingebrigtsen
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=87pnl73y3n.fsf@mouse.gnus.org \
--to=larsi@gnus.org \
--cc=15485@debbugs.gnu.org \
--cc=andreas.roehler@easy-emacs.de \
/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.