From: Benjamin Rutt <rutt.4+news@osu.edu>
Subject: Re: suppress insertion of SPC after SPC expands abbrev
Date: Sun, 27 Jun 2004 12:18:08 -0400 [thread overview]
Message-ID: <87k6xt2cvz.fsf@osu.edu> (raw)
In-Reply-To: b607d812.0406231417.7a2148b1@posting.google.com
sandipchitale@yahoo.com (Sandip Chitale) writes:
> Benjamin Rutt <rutt.4+news@osu.edu> wrote in message news:<87vfhi4d8s.fsf@osu.edu>...
>> I want to prevent the SPC from getting inserted when an abbrev is
>> expanded, much like C-x ' does.
>>
> Look into:
>
> The 'no-self-insert property of the tempo-template-* defuns. Does that help?
Yes, that helps a great deal. I simply define my abbrev functions by
name (rather than anonymous) and give them the 'no-self-insert
property. I think this is the cleanest solution, thanks.
--
Benjamin Rutt
prev parent reply other threads:[~2004-06-27 16:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-23 13:26 suppress insertion of SPC after SPC expands abbrev Benjamin Rutt
2004-06-23 19:14 ` Kevin Rodgers
2004-06-23 21:10 ` Benjamin Rutt
2004-06-23 22:17 ` Sandip Chitale
2004-06-27 16:18 ` Benjamin Rutt [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
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=87k6xt2cvz.fsf@osu.edu \
--to=rutt.4+news@osu.edu \
/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).