From: Dan Anderson <dan@mathjunkies.com>
Subject: Re: defining long abbrevs
Date: Wed, 05 Nov 2003 15:08:41 -0500 [thread overview]
Message-ID: <1068062921.6472.9.camel@hades.syr-24-59-76-83.twcny.rr.com> (raw)
In-Reply-To: <uhe1i3bv7.fsf@standardandpoors.com>
> C-u C-x a g should work.
Perhaps I should be more specific. I can type C-x a g or C-u C-x a g
and get the last word or sentence (or even count words with ESC number
C-x a g). But the problem I'm running into is that if I do that Emacs
is "guessing" about what I want, and doesn't always guess correctly.
Is there any way to mark text and then C-x a g it? I tried M-x
abbrev-prefix-mark and all it did was insert a - into the buffer at the
text position.
I figure there has to be some way..
-Dan
next prev parent reply other threads:[~2003-11-05 20:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.3175.1067991731.21628.help-gnu-emacs@gnu.org>
2003-11-05 18:35 ` defining long abbrevs Galen Boyer
2003-11-05 20:08 ` Dan Anderson [this message]
[not found] ` <mailman.3261.1068062972.21628.help-gnu-emacs@gnu.org>
2003-11-05 21:41 ` Johan Bockgård
2003-11-04 23:19 Dan Anderson
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=1068062921.6472.9.camel@hades.syr-24-59-76-83.twcny.rr.com \
--to=dan@mathjunkies.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.
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).