From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: mailabbrev.el, mailalias.el and related package.
Date: Fri, 15 Feb 2002 03:36:22 -0700 (MST) [thread overview]
Message-ID: <200202151036.g1FAaMU07264@santafe.santafe.edu> (raw)
In-Reply-To: <200202140440.WAA20427@eel.dms.auburn.edu> (message from Luc Teirlinck on Wed, 13 Feb 2002 22:40:41 -0600 (CST))
Would the Emacs maintainers in principle be willing to consider the
possibility of replacing the current dual mailalias-mailabbrev system
with one single (very customizable) system.
Yes. That sounds like a good cleanup.
I include a copy of a previously posted bug report about bugs that my
package takes care of.
Can you tell me which of the recent bugs (if any) your package
does NOT fix? And can you fix them?
How about this--can you fix this too?
Sender: ke@gnu.franken.de
To: rms@gnu.org
Cc: emacs-devel@gnu.org
Subject: Re: expanding mail aliases too aggressive (.mailrc)
In-Reply-To: <200202121523.g1CFN7507211@aztec.santafe.edu> (Richard
Stallman's message of "Tue, 12 Feb 2002 08:23:07 -0700 (MST)")
From: Karl Eichwalder <ke@gnu.franken.de>
Reply-To: Karl Eichwalder <keichwa@gmx.net>
Date: Wed, 13 Feb 2002 00:46:56 +0100
Richard Stallman <rms@gnu.org> writes:
> Does this fix the problem?
[...]
> ***************
> *** 464,469 ****
> --- 469,475 ----
> (if (equal value _)
> (set-char-table-range tab key w))))
> tab)
> + (modify-syntax-entry ?@ "w" tab)
> (setq mail-abbrev-syntax-table tab)))
>
> ;; If the character just typed was non-alpha-symbol-syntax,
>
Yes, this fixes the reported problem, but it isn't general enough.
Completing mail abbrevs must only happen for strings after
^[tT]o:[:blank:]?
or
,[:blank:]
Wondering when my .mailrc entries were transferred to
(define-abbrev-table 'mail-abbrevs '(...)) in ~/.abbrev_defs; was this
a one time action or does Emacs maintain this list?
Whenever Emacs decides to modify user files in tell the user about it
(through a message dialog the user is considered to confirm) and add a
comment.
--
ke@suse.de (work) / keichwa@gmx.net (home): |
http://www.suse.de/~ke/ | ,__o
Free Translation Project: | _-\_<,
http://www.iro.umontreal.ca/contrib/po/HTML/ | (*)/'(*)
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel
next prev parent reply other threads:[~2002-02-15 10:36 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 [this message]
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
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=200202151036.g1FAaMU07264@santafe.santafe.edu \
--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 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).