From: Lars Ingebrigtsen <larsi@gnus.org>
To: Mauro Aranda <maurooaranda@gmail.com>
Cc: 15485@debbugs.gnu.org
Subject: bug#15485: add-abbrev: don't use hard-coded forward-word
Date: Thu, 15 Aug 2019 16:50:44 -0700 [thread overview]
Message-ID: <87a7cat2cr.fsf@mouse.gnus.org> (raw)
In-Reply-To: <CABczVwfPWM0gWoCvrv2+yM28rCef6GGXggsOB12tcypte_Lz8Q@mail.gmail.com> (Mauro Aranda's message of "Thu, 15 Aug 2019 09:41:26 -0300")
Mauro Aranda <maurooaranda@gmail.com> writes:
> I don't think the OP wanted to use `add-abbrev' in a Lisp program. What
> I understand is that the problem reported arises when someone wants to
> add an abbrev for a programming construct (in the example: "<?php ?>")
> it is likely that `add-abbrev' won't give the entire desired
> expansion.
>
> With that being said, at least in current Emacs it is easy to add that
> abbrev, by setting the mark and point properly and calling
> `add-mode-abbrev' with a 0 prefix argument.
Ah, I see.
>> 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
>
> What is nabbrev.el? I did a search in what I believe are usual places,
> but didn't found anything.
Sorry, I was completely confused. Somehow I was thinking about
advice.el/nadvice.el here. :-/
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2019-08-15 23:50 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
2019-08-15 12:41 ` Mauro Aranda
2019-08-15 14:37 ` Andreas Röhler
2019-08-15 23:50 ` Lars Ingebrigtsen [this message]
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=87a7cat2cr.fsf@mouse.gnus.org \
--to=larsi@gnus.org \
--cc=15485@debbugs.gnu.org \
--cc=maurooaranda@gmail.com \
/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.