unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Uwe Brauer <oub@mat.ucm.es>
To: emacs-devel@gnu.org
Subject: Re: did the abbrev mechanism ever expand «two words» to «two different words».
Date: Fri, 08 Jan 2021 09:20:17 +0100	[thread overview]
Message-ID: <87ft3blu0u.fsf@mat.ucm.es> (raw)
In-Reply-To: jwvv9c8mqov.fsf-monnier+emacs@gnu.org

[-- Attachment #1: Type: text/plain, Size: 1327 bytes --]

>>> "SM" == Stefan Monnier <monnier@iro.umontreal.ca> writes:

>> An “abbrev” is a word that has been defined to “expand” into a specified
>> “expansion”.  When you insert a word-separator character following the
>> abbrev, that expands the abbrev—replacing the abbrev with its expansion.
>> For example, if ‘foo’ is defined as an abbrev expanding to ‘find outer
>> otter’, then typing ‘f o o .’ will insert ‘find outer otter.’.
>> 
>> This mean a word-separator character cannot be part of an abbrev.

> That's true for the default behavior.
> Since Emacs-24, abbrev tables do support abbrevs whose name includes
> non-word characters, but it requires extra work on the part of the user
> in order to characterize the possible names via the `:regexp` property
> (see `C-h o define-abbrev-table`).

Thanks, I read the documentation but I am unable to figure out, what
regexp has to be used for that regexp I should use in order to make a
two word expansion work. 

All regexp I tried returned error.

So this 

(define-abbrev-table 'fundamental-mode-abbrev-table
  '(
    ("a que" "a qué" :regexp 1 :count 0)))


Does not return error but does not work as well.

May I suggest to add an example in the documentation of 

`C-h o define-abbrev-table`

Thanks 


[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5673 bytes --]

  parent reply	other threads:[~2021-01-08  8:20 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-07 20:10 did the abbrev mechanism ever expand «two words» to «two different words» Uwe Brauer
2021-01-07 20:15 ` Eli Zaretskii
2021-01-07 20:29   ` Uwe Brauer
2021-01-07 20:36   ` Stefan Monnier
2021-01-07 20:40     ` Eli Zaretskii
2021-01-08  8:20     ` Uwe Brauer [this message]
2021-01-08 10:55       ` Robert Pluim
2021-01-08 13:28         ` Uwe Brauer
2021-01-08 14:05           ` Robert Pluim
2021-01-08 15:23             ` Uwe Brauer
2021-01-08 18:05               ` Robert Pluim
2021-01-08 18:48                 ` Uwe Brauer
2021-01-08 20:29                 ` Stefan Monnier
2021-01-08 21:06                   ` Uwe Brauer
2021-01-09 12:14                     ` Eric S Fraga
2021-01-09 13:39                       ` Uwe Brauer
2021-01-09 13:42                 ` [BUG? write-abbrev-file destroys this construction] (was: did the abbrev mechanism ever expand «two words» to «two different words».) Uwe Brauer
2021-01-09  6:37   ` did the abbrev mechanism ever expand «two words» to «two different words» Richard Stallman
2021-01-09  8:11     ` [adding abbrev using two-word-expansions] (was: did the abbrev mechanism ever expand «two words» to «two different words».) Uwe Brauer

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=87ft3blu0u.fsf@mat.ucm.es \
    --to=oub@mat.ucm.es \
    --cc=emacs-devel@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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).