unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: help-gnu-emacs@gnu.org
Subject: Re: Using punctuation in abbrev
Date: Sun, 02 Jun 2013 10:24:53 -0400	[thread overview]
Message-ID: <jwvmwr81tku.fsf-monnier+gmane.emacs.help@gnu.org> (raw)
In-Reply-To: CA+5B0FOyMxL4U-+LCthS0xmbeoB=0n61eETT8bvCb-vJnW2Pog@mail.gmail.com

> Here's what I put in my init file:

>   (define-abbrev-table 'global-abbrev-table '(
>                                               ("$->" "→")
>                                               ("$=>" "⇒")
>                                               ("$foo" "X")
>                                               )
>     "custom abbrev table"
>     :regexp (rx (or bos bol space) (group (+ (not space)))))
>   (setq save-abbrevs nil)
>   (setq-default abbrev-mode t)

> But only the $foo substitution works and I can't figure out why.

Actually, if you call M-x expand-abbrev RET explicitly, you'll see they
all work.  What doesn't work for the first two is the "press space after
it to cause expansion", because this is only performed right after
a word char (hence it works for "$foo" because the last char is a word
char).


        Stefan




  parent reply	other threads:[~2013-06-02 14:24 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
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 [this message]
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=jwvmwr81tku.fsf-monnier+gmane.emacs.help@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --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).