From: sandipchitale@yahoo.com (Sandip Chitale)
Subject: Re: suppress insertion of SPC after SPC expands abbrev
Date: 23 Jun 2004 15:17:13 -0700 [thread overview]
Message-ID: <b607d812.0406231417.7a2148b1@posting.google.com> (raw)
In-Reply-To: 87vfhi4d8s.fsf@osu.edu
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.
>
> The following thread from 1992 discusses this:
>
> http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&threadm=WMESARD.92Sep4121833%40tofu.oracle.com&rnum=1&prev=/groups%3Fhl%3Den%26lr%3D%26ie%3DUTF-8%26q%3Demacs%2Babbrev%2Bsuppress%2Bspace%26btnG%3DSearch
>
> None of those solutions looked very clean. Is there any way in
> current emacs to do this?
Look into:
The 'no-self-insert property of the tempo-template-* defuns. Does that help?
next prev parent reply other threads:[~2004-06-23 22:17 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 [this message]
2004-06-27 16:18 ` Benjamin Rutt
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=b607d812.0406231417.7a2148b1@posting.google.com \
--to=sandipchitale@yahoo.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).