unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Matthias Pfeifer <mpfeifer77@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: About abbrevs and spaces at end of line
Date: Tue, 10 Dec 2013 12:53:08 +0100	[thread overview]
Message-ID: <CAPzsW6jSSTKuPC=jo4xG1KXYfCLAFLA+tEF7ahkzjcMa2FwfwA@mail.gmail.com> (raw)
In-Reply-To: <52A6FF60.3000101@easy-emacs.de>

Hi Harry,

If you take some time to get comfortable with emacs hippie-expand that
might be an option, too. hippie-expand overloads the tab key with a list of
functions and chooses one that fits to the current position. There is also
a function that expands abbrevs before point.

matthias



2013/12/10 Andreas Röhler <andreas.roehler@easy-emacs.de>

> Am 10.12.2013 12:08, schrieb Harry Putnam:
>
>  Andreas Röhler <andreas.roehler@easy-emacs.de> writes:
>>
>>  Am 09.12.2013 22:46, schrieb Harry Putnam:
>>>
>>>> Is there some smooth way to avoid having a space at the end of line
>>>> when activating an abbrev as the last thing done before newline?
>>>>
>>>
>> [...]
>>
>>  The short and long is: Invoking with spc leaves unsightly marks like
>>>> an underscore if done at the end of a line and invoking with <RET> is
>>>> not always desirable if a new line is not needed.
>>>>
>>>
>> [...]
>>
>>
>>>> I have visions of some tricky way of setting up an abbrev with hardly
>>>> any more effort than the normal
>>>>
>>>>      M-x edit-abbrevs <RET>
>>>>
>>>>      "tru"       0          "\"TRUE\";"
>>>>
>>>> In the cperl-table, then pressing C-c
>>>>
>>>> Where I only need to edit the cperl abbrev table.
>>>>
>>>>
>>>>
>>>>
>>>>
>>> Problem results from binding abbrev-expand to SPACE.
>>> Abbrev is expanded, than SPACE is inserted, as you typed it.
>>>
>>> Solution: abbrev-mode off. Use any other key to M-x expand-abbrev RET.
>>> This will expand it, but not insert a space.
>>>
>>
>> Thank you.
>>
>> After looking into this a bit, I'm not seeing a handy way to set
>> something else permanently.
>>
>> In fact it appears there are nearly half a dozen ways to invoke
>> expansion.
>>
>> space, <RET>, C-x ' (At least two more key combos that I already
>> forgot)
>>
>> So there must be a list or regex or something.
>>
>>
> Do you mean "list of keys"?
>
>
>  I'd like to add some other char to the list somehow.
>>
>>
> Are you asking how to bind another key onto expand-abbrev command?
>
>
>  Any clues how I might do that?
>>
>>
>>
>>
> BTW another solution might advice abbrev-expand with (delete-char -1) -
> which would DTRT with <space> only.
>
>
>


  reply	other threads:[~2013-12-10 11:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-09 21:46 About abbrevs and spaces at end of line Harry Putnam
2013-12-10  8:07 ` Andreas Röhler
2013-12-10 11:08   ` Harry Putnam
2013-12-10 11:47     ` Andreas Röhler
2013-12-10 11:53       ` Matthias Pfeifer [this message]
2013-12-11 12:29       ` Harry Putnam
2013-12-11 13:03         ` Andreas Röhler
     [not found] <mailman.8702.1386625654.10748.help-gnu-emacs@gnu.org>
2013-12-11 20:54 ` duthen.mac.01
2013-12-11 20:55 ` duthen.mac.01

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='CAPzsW6jSSTKuPC=jo4xG1KXYfCLAFLA+tEF7ahkzjcMa2FwfwA@mail.gmail.com' \
    --to=mpfeifer77@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    /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).