Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <reinersteib+gmane@imap.cc>
To: Stephen Eglen <S.J.Eglen@damtp.cam.ac.uk>
Cc: ding@gnus.org
Subject: Re: Small change to message-tab to allow completion of mail aliases
Date: Fri, 30 May 2008 19:14:50 +0200	[thread overview]
Message-ID: <v98wxr7lyt.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <t5x63svsvc4.fsf@notch.damtp.cam.ac.uk> (Stephen Eglen's message of "Fri, 30 May 2008 15:46:51 +0100")

On Fri, May 30 2008, Stephen Eglen wrote:

> Thanks for fixing the typo in message.el;  as I'm new to using GNUS
> (for reading/writing email, I've used it for news for ages), I just also
> found the following; is gnu.emacs.gnus a sensible place, or is the ding
> maillist more suitable?

The ding list (cc-ed) is more suitable.

(BTW, your message didn't appear on
<http://news.gmane.org/gmane.emacs.gnus.user> yet, which is feed from
the news2mail gateway gnu.emacs.gnus <-> info-gnus-english@gnu).

> From: Stephen Eglen <S.J.Eglen@damtp.cam.ac.uk>   
> Subject: Small change to message-tab to allow completion of mail aliases
> Newsgroups: gnu.emacs.gnus
> Date: Thu, 29 May 2008 19:28:05 +0200
> Organization: University of Cambridge, England
> Message-ID: <t5x1w3lt3yy.fsf@notch.damtp.cam.ac.uk>
> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (gnu/linux)
>
> Would it be worth making the following small change to
> message-expand-name, so that TAB on a To: field will allow for
> completion of mail aliases, rather than just expansion of complete mail
> aliases.  All that has changed is expand-abbrev has been changed to
> mail-abbrev-complete-alias
>
> (e.g. if you have the alias "moderator", and no other alias starting
> "mo", then "mo TAB" would complete to moderator)

Does this change have any drawbacks?  I always use the bbdb code path,
so I'm not familiar with the current and proposed behavior.

> (defun message-expand-name ()
>   (cond ((and (memq 'eudc message-expand-name-databases)
> 		    (boundp 'eudc-protocol)
> 		    eudc-protocol)
> 	 (eudc-expand-inline))
> 	((and (memq 'bbdb message-expand-name-databases)
> 	      (fboundp 'bbdb-complete-name))
> 	 (bbdb-complete-name))
> 	(t
> 	 (mail-abbrev-complete-alias))))
>          ;;(expand-abbrev))))

BTW (for future suggestions): sending a unified diff is
encouraged.  Like this:

--- message.el	29 May 2008 20:10:06 +0200	7.263
+++ message.el	30 May 2008 19:02:56 +0200	
@@ -7651,7 +7651,7 @@
 	      (fboundp 'bbdb-complete-name))
 	 (bbdb-complete-name))
 	(t
-	 (expand-abbrev))))
+	 (mail-abbrev-complete-alias))))
 
 ;;; Help stuff.

Could you also provide a ChangeLog entry describing the change?

Bye, Reiner
-- 
PGP key available                               http://rsteib.home.pages.de/



       reply	other threads:[~2008-05-30 17:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <t5x63svsvc4.fsf@notch.damtp.cam.ac.uk>
2008-05-30 17:14 ` Reiner Steib [this message]
2008-05-30 22:47   ` Dave Goldberg
2008-05-31  9:17     ` Reiner Steib
2008-05-31 16:19       ` Dave Goldberg
2008-06-02 18:29       ` Stephen Eglen

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=v98wxr7lyt.fsf@marauder.physik.uni-ulm.de \
    --to=reinersteib+gmane@imap.cc \
    --cc=Reiner.Steib@gmx.de \
    --cc=S.J.Eglen@damtp.cam.ac.uk \
    --cc=ding@gnus.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.
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 NNTP newsgroup(s).