unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: oub@mat.ucm.es, larsi@gnus.org, 45693@debbugs.gnu.org
Subject: bug#45693: [two word expansion works, but write-abbrev-file destroys it]
Date: Mon, 11 Jan 2021 17:26:57 +0200	[thread overview]
Message-ID: <83czybfq9q.fsf@gnu.org> (raw)
In-Reply-To: <87wnwjd9yy.fsf@gmail.com> (message from Robert Pluim on Mon, 11 Jan 2021 11:49:41 +0100)

> From: Robert Pluim <rpluim@gmail.com>
> Date: Mon, 11 Jan 2021 11:49:41 +0100
> Cc: Lars Ingebrigtsen <larsi@gnus.org>, 45693@debbugs.gnu.org
> 
> Uwe Brauer <oub@mat.ucm.es> writes:
> 
> > The part 
> >         (define-abbrev-table 'my-abbrev-table
> >       '(
> >         ("a que" "a qué" nil :count 0))
> >       "Uwe's table"
> >       :regexp "\\(\\w+ \\w+\\)")
> >
> > Is gone!
> 
> Yes, and it gets worse. You can get around the 'setq
> local-abbrev-table' issue by using the ':parents' property:
> 
>     (define-abbrev-table 'fundamental-mode-abbrev-table
>       '(
>         ("asi" "así" nil :count 0))
>       "Fundamental"
>       :parents (list my-abbrev-table))
> 
>     (define-abbrev-table 'my-abbrev-table
>       '(
>         ("a que" "a qué" nil :count 0))
>       "Uwe's table"
>       :regexp "\\(\\w+ \\w+\\)")
> 
> 
> but write-abbrev-table then produces the following abbrev file:
> 
> ;;-*-coding: utf-8;-*-
> (define-abbrev-table 'fundamental-mode-abbrev-table
>   '(
>     ("asi" "así" nil :count 1)
>    ))
> 
> (define-abbrev-table 'my-abbrev-table
>   '(
>     ("a que" "a qué" nil :count 1)
>    ))
> 
> so write-abbrev-file doesnʼt write any of the properties specified in
> define-abbrev-table to the abbrev file.

So does it mean we had better avoid describing this "feature" in the
docs, until and unless it gets fixed to be more user-friendly?





  reply	other threads:[~2021-01-11 15:26 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-06 15:54 bug#45693: 28.0.50; abbrev does not expand two words any more Uwe Brauer
2021-01-10 14:35 ` Lars Ingebrigtsen
2021-01-10 15:51   ` Uwe Brauer
2021-01-10 15:52     ` Lars Ingebrigtsen
2021-01-10 17:22       ` Uwe Brauer
2021-01-10 21:21       ` bug#45693: [two word expansion works, but write-abbrev-file destroys it] (was: bug#45693: 28.0.50; abbrev does not expand two words any more) Uwe Brauer
2021-01-11 10:49         ` bug#45693: [two word expansion works, but write-abbrev-file destroys it] Robert Pluim
2021-01-11 15:26           ` Eli Zaretskii [this message]
2021-01-11 15:50             ` Uwe Brauer
2021-01-11 17:38               ` Robert Pluim
2021-01-11 20:17                 ` Uwe Brauer
2021-01-11 20:38                   ` Robert Pluim
2021-01-11 20:48                     ` Uwe Brauer
2021-01-11 21:03                       ` Robert Pluim
2021-01-12  8:01                         ` Uwe Brauer
2021-01-12 10:34                           ` Robert Pluim
2021-01-12 13:26                             ` Uwe Brauer
2021-01-12 16:45                             ` Uwe Brauer
2021-01-12 17:59                               ` Robert Pluim
2021-01-13  7:37                                 ` Uwe Brauer
2021-01-13  9:16                                   ` Robert Pluim
2021-01-13  9:28                                     ` Uwe Brauer
2021-01-13  9:39                                       ` Robert Pluim
2021-01-13  9:51                                         ` Uwe Brauer
2021-01-13 10:09                                           ` Robert Pluim
2021-01-13 13:18                                             ` Uwe Brauer
2021-01-13 14:03                                               ` Robert Pluim
2021-01-13 16:25                                                 ` 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=83czybfq9q.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=45693@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=oub@mat.ucm.es \
    --cc=rpluim@gmail.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.
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).