From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: emacs-devel@gnu.org
Subject: Re: mailabbrev.el, mailalias.el and related package.
Date: Fri, 15 Feb 2002 22:47:29 -0600 (CST) [thread overview]
Message-ID: <200202160447.WAA29111@eel.dms.auburn.edu> (raw)
In-Reply-To: <200202151036.g1FAaMU07264@santafe.santafe.edu> (message from Richard Stallman on Fri, 15 Feb 2002 03:36:22 -0700 (MST))
I do not know whether I should actually post this to this thread or
to "expanding mail aliases too aggressive (.mailrc)". Also, maybe
additional people should get a CC?
Concerning the effect of my package on the two problems reported in
"expanding mail aliases too aggressive (.mailrc)":
In .mailrc I used to have this entry:
alias gnu <gnu@gnu.org>
Now, when I type
To: emacs-devel@gnu.-!-
it gets expanded to
To: emacs-devel@<gnu@gnu.org>
I may be misunderstanding the above, but I can not only not reproduce
this in Emacs20.7 built with my package, I can also not reproduce it
in Emacs21.1.90 without any of my package included in it.
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.
The current mailabbrev.el needs to write mailabbrevs in
~/.abbrevs_defs, because that is the only way it can save them. Of
course aliases defined in .mailrc are already stored there, but
mailabbrev needs to worry about aliases defined in other ways. My
package would change that totally, because it would have all aliases
defined in .mailrc. It would still use abbrevs internally, but these
would be essentially invisible to users.
Conflicts between the two types of aliases were a source of bugs.
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel
next prev parent reply other threads:[~2002-02-16 4:47 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 [this message]
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=200202160447.WAA29111@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).