unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: rgm@gnu.org, emacs-devel@gnu.org
Subject: Re: Characterset for Abbrevation names limited
Date: Wed, 27 Jun 2007 15:49:52 -0400	[thread overview]
Message-ID: <E1I3dWS-0006I9-Kw@fencepost.gnu.org> (raw)
In-Reply-To: <jwvr6nyp2h3.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Tue, 26 Jun 2007 22:19:19 -0400)

    I can't recover the original email so I'm not sure what was suggested, but
    if the suggestion is to make define-abbrev signal an error if the abbrev
    uses chars that are not word constituents, this will be problematic because
    the criterion depends on the syntax-table in use and that one may not be the
    same during define-abbrev as during expand-abbrev (some code in Emacs even
    uses pre-abbrev-expand-hook to change the syntax-table used during
    expand-abbrev independently from the syntax-table used otherwise in the
    buffer).

We could leave define-abbrev alone and make the user level commands,
define-global-abbrev and define-mode-abbrev, do this check.

That way, ordinary users would be protected from the mistake,
and experts could still do whatever they wish.

      parent reply	other threads:[~2007-06-27 19:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <467A7A62.40202@gmx.de>
     [not found] ` <tq7ipvg5j6.fsf@fencepost.gnu.org>
     [not found]   ` <467E88DA.8020906@gmx.de>
     [not found]     ` <18048.3335.394836.510128@fencepost.gnu.org>
     [not found]       ` <E1I2ucR-00013Q-80@fencepost.gnu.org>
2007-06-26 23:57         ` Characterset for Abbrevation names limited Glenn Morris
2007-06-27  2:19           ` Stefan Monnier
2007-06-27  2:56             ` Glenn Morris
2007-06-27 19:49             ` Richard Stallman [this message]

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=E1I3dWS-0006I9-Kw@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=rgm@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).