unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Aurélien Aptel" <aurelien.aptel+emacs@gmail.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Using punctuation in abbrev
Date: Sun, 2 Jun 2013 00:49:40 +0200	[thread overview]
Message-ID: <CA+5B0FNuGWKjL7tXzkaE7EedK8gPPKzof-G0OSdeRprZXbzLpQ@mail.gmail.com> (raw)
In-Reply-To: <c4309ff1-04a0-4eff-87ce-2bd24fbcf6b3@default>

On Sat, Jun 1, 2013 at 8:42 PM, Drew Adams <drew.adams@oracle.com> wrote:
>> I want to substitute $-> with a unicode rightwards arrow (U+2192  →).
>
> 1. Does that mean that you want to type `$->' and use `expand-abbrev'
> each time to insert a Unicode right arrow?  If so, and if you don't
> really care whether you use abbrev, consider binding insertion of a
> right arrow char to a key sequence instead.

The abbrev minor mode is active in all my buffers and it doesn't have
to be triggered by a specific key, it's automatically substituted as I
type. I plan on having a lot of easy-to-remember abbreviations for
unicode chars I regularly use, all prefixed by $ or some other less
used character so that it only triggers when I want. Calling
insert-char is too cumbersome and breaks the flow.

The only thing that doesn't work is this word extraction regex...

> 2. On the other hand, if you already have lots of `$->' occurrences in
> your text and you want to change them to right arrows, consider using
> `query-replace' or `replace-string' instead.

That is not what I want.



  reply	other threads:[~2013-06-01 22:49 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-01 17:41 Using punctuation in abbrev Aurélien Aptel
2013-06-01 18:42 ` Drew Adams
2013-06-01 22:49   ` Aurélien Aptel [this message]
2013-06-02 18:48     ` Drew Adams
     [not found]   ` <mailman.841.1370126985.22516.help-gnu-emacs@gnu.org>
2013-06-02  5:02     ` Emanuel Berg
2013-06-02  5:21     ` Emanuel Berg
2013-06-02 17:17       ` Aurélien Aptel
2013-06-02 18:10         ` Jambunathan K
2013-06-03  3:44         ` Yuri Khan
     [not found]         ` <mailman.905.1370231076.22516.help-gnu-emacs@gnu.org>
2013-06-03 18:05           ` Emanuel Berg
2013-06-04  3:05             ` Yuri Khan
2013-06-04  9:14               ` Aurélien Aptel
     [not found]             ` <mailman.968.1370315124.22516.help-gnu-emacs@gnu.org>
2013-06-04 17:27               ` Emanuel Berg
2013-06-05  6:59                 ` Yuri Khan
     [not found]                 ` <mailman.1022.1370415567.22516.help-gnu-emacs@gnu.org>
2013-06-05 21:12                   ` Emanuel Berg
2013-06-04 21:39             ` Stefan Monnier
     [not found]             ` <mailman.1002.1370382007.22516.help-gnu-emacs@gnu.org>
2013-06-04 22:47               ` Emanuel Berg
     [not found]       ` <mailman.880.1370193431.22516.help-gnu-emacs@gnu.org>
2013-06-02 19:48         ` Emanuel Berg
2013-06-02 21:06           ` Stefan Monnier
2013-06-02 22:36           ` Aurélien Aptel
     [not found]           ` <mailman.901.1370212579.22516.help-gnu-emacs@gnu.org>
2013-06-03  0:10             ` Emanuel Berg
2013-06-02 14:24 ` Stefan Monnier
2013-06-02 17:00   ` Aurélien Aptel
2013-06-02 17:54     ` Andreas Röhler
2013-06-02 17:56     ` Stefan Monnier

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=CA+5B0FNuGWKjL7tXzkaE7EedK8gPPKzof-G0OSdeRprZXbzLpQ@mail.gmail.com \
    --to=aurelien.aptel+emacs@gmail.com \
    --cc=drew.adams@oracle.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).