Gnus development mailing list
 help / color / mirror / Atom feed
From: Mike Fabian <mike.fabian@gmx.de>
Cc: ding@gnus.org
Subject: Re: Email address handling
Date: 08 Feb 2000 07:55:48 +0100	[thread overview]
Message-ID: <m3emaob2tn.fsf@nozomi.rhein-neckar.de> (raw)
In-Reply-To: Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "06 Feb 2000 16:55:24 +0100"

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:

> Mike Fabian <mike.fabian@gmx.de> writes:
> 
> > But I have always wondered why `Gcc: nnml+archive:archive' isn't
> > inserted automatically when I click on such a header. Most other
> > commands to send mail insert the `Gcc:' header automatically.
> 
> Maybe hitting RET on a mailto URL invokes message-mail rather than
> gnus-mail?  Message can in principle be used without Gnus, and when
> you do that you don't get the normal Gnus features, of course.
> 
> Somebody has written some code such that you can set mail-user-agent
> to some value which uses gnus-mail rather than message-mail in such
> cases.  You may wish to search the Gnus and BBDB mailing list archives
> for define-mail-user-agent.

Thank you, I found a message in the archive explaining how to do this: 

    From: Rob Browning <rlb@cs.utexas.edu>
    Subject: Success?  Potential gnus-user-agent definition.
    Newsgroups: gnu.emacs.gnus
    Date: 17 Jun 1999 00:00:00 GMT

In this message Rob writes that define-mail-user-agent doesn't help
with bbdb:

RB> Note that it doesn't help with bbdb, but after further
RB> investigation, I discovered that that's because the version of
RB> bbdb doesn't use compose-mail, but the docs claim it will.  When
RB> it does, everything will work fine.

For the same reason it doesn't work when starting a mail by clicking
on a email-address in the headers of an *Article* buffer.
`compose-mail' is not used in this case either (I checked by
instrumenting `compose-mail' for Edebug and see whether it stops
there. It doesn't.)

Maybe this is an oversight and `compose-mail' should be used in this
case?

-- 
Mike Fabian   <mike.fabian@gmx.de>   <mike@nozomi.rhein-neckar.de>




  reply	other threads:[~2000-02-08  6:55 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-02-04 15:59 Roman Belenov
2000-02-04 16:10 ` Colin Marquardt
2000-02-04 17:10 ` Kai Großjohann
2000-02-04 17:13   ` Roman Belenov
2000-02-04 17:43     ` Kai Großjohann
2000-02-04 17:48       ` Roman Belenov
2000-02-04 17:58       ` Jason Rumney
2000-02-04 18:18         ` Kai Großjohann
2000-02-05 13:46       ` Randal L. Schwartz
2000-02-07 14:59         ` Colin Rafferty
2000-02-07 15:14           ` Kai Großjohann
2000-02-07 15:26             ` Colin Rafferty
2000-02-07 17:56               ` Steinar Bang
2000-02-07 12:34     ` Toby Speight
2000-02-07 19:00       ` Per Abrahamsen
2000-04-20 23:43         ` Lars Magne Ingebrigtsen
2000-02-05 12:48   ` Mike Fabian
2000-02-06 15:55     ` Kai Großjohann
2000-02-08  6:55       ` Mike Fabian [this message]
2000-02-08 12:15         ` Kai Großjohann

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=m3emaob2tn.fsf@nozomi.rhein-neckar.de \
    --to=mike.fabian@gmx.de \
    --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).