From: Eli Zaretskii <eliz@gnu.org>
To: Jean-Christophe Helary <jean.christophe.helary@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: abbrev definition (manual)
Date: Wed, 26 Jul 2017 17:29:11 +0300 [thread overview]
Message-ID: <83r2x35l1k.fsf@gnu.org> (raw)
In-Reply-To: <A69798DA-9B25-459F-A07E-D4AFAF8C2DD6@gmail.com> (message from Jean-Christophe Helary on Wed, 26 Jul 2017 08:18:46 +0900)
> From: Jean-Christophe Helary <jean.christophe.helary@gmail.com>
> Date: Wed, 26 Jul 2017 08:18:46 +0900
>
> I find the manual explanation for the definition of an abbrev confusing:
>
> The usual way to define an abbrev is to enter the text you want the abbrev to expand to, position point after it, and type C-x a g (add-global-abbrev). This reads the abbrev itself using the minibuffer, and then defines it as an abbrev for one or more words before point. Use a numeric argument to say how many words before point should be taken as the expansion. For example, to define the abbrev ‘foo’ as mentioned above, insert the text ‘find outer otter’ and then type C-u 3 C-x a g f o o RET.
>
> What about that:
>
> The usual way to define an abbrev is to enter the text you want the abbrev to expand to, position point after it, and type C-x a g (add-global-abbrev). Use a numeric argument to say how many words before point should be taken as the expansion. This prompts for the abbrev itself in the minibuffer, and then defines it as an abbrev for the words specified before point. For example, to define the abbrev 'foo' as mentioned above, insert the text 'find outer otter' and then type C-u 3 C-x a g f o o RET.
I find them both equivalent, so I'm not sure what part of the original
confused you. Was that the "reads ... using the minibuffer" part?
prev parent reply other threads:[~2017-07-26 14:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-25 23:18 abbrev definition (manual) Jean-Christophe Helary
2017-07-26 7:00 ` Colin Baxter
2017-07-26 14:29 ` Eli Zaretskii [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=83r2x35l1k.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jean.christophe.helary@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.