From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: emacs-devel@gnu.org
Subject: Re: mailabbrev.el, mailalias.el and related package.
Date: Sun, 17 Feb 2002 13:13:27 -0600 (CST) [thread overview]
Message-ID: <200202171913.NAA01240@eel.dms.auburn.edu> (raw)
In-Reply-To: <200202171648.g1HGmlu10290@aztec.santafe.edu> (message from Richard Stallman on Sun, 17 Feb 2002 09:48:47 -0700 (MST))
I may have to correct, or at least amend, certain comments I made
about mail-mode-header-syntax-table in a previous message concerning
the aggressive mailabbrev expansion problem.
The analysis of the problem with aggressive mailabbrev expansion was,
I believe, correct. However my interpretation of the importance of
mail-mode-header-syntax-table in the mailabbrev expansion process may
not have been. What definitely is important is the step performed
there in the definition of mail-abbrev-syntax-table.
First of all, what I erroneously referred to as "the documentation
string" were actually the comments.
Secondly, it probably is possible to perform mailabbrev expansion
correctly using only mail-abbrev-syntax-table, by invoking the lines:
(or (and (integerp last-command-char)
(eq (char-syntax last-command-char) ?_))
AFTER establishing the correct mail-abbrev-syntax-table and replacing
the ?_ in this code by ?w
That should be carefully checked, however.
The intent of mail-mode-header-syntax-table as a separate syntax-table
may indeed only have been the forward-sexp stuff. That is not the
only intent of the syntactic changes performed there, however.
To determine whether I keep or eliminate mail-mode-header-syntax-table
in my new package, I will have to check whether I need it elsewhere.
In essence, in my previous message, I confused the syntax table itself
with the actual syntactic steps performed there.
On another topic, in a previous message I sent to you, I
unintentionally deleted the CC field. When I noticed this, I sent a
separate copy to emacs-devel@gnu.org. I am sorry if this caused any
problems or confusion.
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel
next prev parent reply other threads:[~2002-02-17 19:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-14 4:40 mailabbrev.el, mailalias.el and related package Luc Teirlinck
2002-02-15 10:36 ` Richard Stallman
2002-02-16 3:53 ` Luc Teirlinck
2002-02-17 16:48 ` Richard Stallman
2002-02-16 4:47 ` Luc Teirlinck
2002-02-16 5:36 ` Karl Eichwalder
2002-02-16 16:10 ` Luc Teirlinck
2002-02-16 19:04 ` Karl Eichwalder
2002-02-16 20:18 ` Luc Teirlinck
2002-02-17 16:48 ` Richard Stallman
2002-02-17 19:13 ` Luc Teirlinck [this message]
2002-02-17 2:32 ` Luc Teirlinck
2002-02-17 5:25 ` Luc Teirlinck
-- strict thread matches above, loose matches on Subject: below --
2002-02-14 5:19 Luc Teirlinck
2002-02-14 21:13 Luc Teirlinck
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=200202171913.NAA01240@eel.dms.auburn.edu \
--to=teirllm@dms.auburn.edu \
--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).