From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: syntax-after
Date: Fri, 12 Nov 2004 16:25:21 -0500 [thread overview]
Message-ID: <E1CSiv3-0000kT-6i@fencepost.gnu.org> (raw)
In-Reply-To: <87mzxoc8bi.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Thu, 11 Nov 2004 17:51:04 -0500)
It seems really gratuitous. There are already 2 ways to represent the
syntax info of a char: as a cons cell and as a string. Both are documented
in the elisp manual.
The above change introduces yet a third representation, and an undocumented
one at that. Was that really necessary?
It is not new. My change makes it compatible with char-syntax, which
is why I did it. It is also more comparible with the way
modify-syntax-entry works, since the same character is used now by both.
This change reduces the number of representations of the syntax by
one, as far as I know. Or is there some other function that uses the
old representation of syntax-after? If so, perhaps it should be
changed too.
I just saw that the above change caused Juri to install a fix to
descr-text.el that replaces a call to syntax-after with a copy of its
(previous) body.
That is strange, I searched for all the calls and only found them in
paren.el.
next prev parent reply other threads:[~2004-11-12 21:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-11 22:51 syntax-after Stefan Monnier
2004-11-11 23:38 ` syntax-after Juri Linkov
2004-11-12 21:25 ` Richard Stallman [this message]
2004-11-13 10:57 ` syntax-after Juri Linkov
2004-11-13 23:55 ` syntax-after Stefan
2004-11-16 16:49 ` syntax-after Richard Stallman
2004-11-22 5:57 ` syntax-after Stefan Monnier
2004-11-22 10:27 ` syntax-after Kim F. Storm
2004-11-22 17:15 ` syntax-after Stefan Monnier
2004-11-23 6:27 ` syntax-after Juri Linkov
2004-11-23 13:55 ` syntax-after Stefan
2004-11-23 16:30 ` syntax-after Richard Stallman
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1CSiv3-0000kT-6i@fencepost.gnu.org \
--to=rms@gnu.org \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.