Gnus development mailing list
 help / color / mirror / Atom feed
From: Brian May <bmay@csse.monash.edu.au>
Subject: Re: What now?
Date: 07 Dec 1999 16:59:01 +1100	[thread overview]
Message-ID: <t4iogc3fg0q.fsf@silas-2.cc.monash.edu.au> (raw)
In-Reply-To: wmperry@aventail.com's message of "Tue, 07 Dec 1999 00:36:32 -0500"

>>>>> "William" == William M Perry <wmperry@aventail.com> writes:

    William> Well, Emacs/W3 already uses gnus for that, so that should
    William> be pretty simple to do. :)

When I tried it, W3 seemed to use its on interface for the job, and
didn't use Gnus. For instance, w3 requires the NNTP server to be
configured separately from Gnus.

I seem to remember another difference: when clicking on a news link
from Gnus, Gnus will look up all back ends for the message, but
when clicking on it from w3, w3 will only check with the nntp
server.

I think solving these issues would help significantly with my
initial "wish list", article
news:t4in1ruvyij.fsf_-_@silas-2.cc.monash.edu.au

If you don't understand how this could help, please tell me, and
I will give some examples.

(side note: I have seen a number of embedded URLs in news documents of
the form "news:messageid...". Note the trailing periods. This breaks
Gnus, as it doesn't remove them before trying to fetch the article :-(
eg that previous article would be written as:
news:t4in1ruvyij.fsf_-_@silas-2.cc.monash.edu.au...
)

    William> Easily accomplished. :) The problem with using gnus
    William> posting styles for Emacs/W3 mailto: URLs is that not
    William> everybody clicks those links from within Gnus.  Emacs/W3

Thats what I meant. I want to be able to click on the link from
w3. Same goes for the issue above. I think it should work for links
you click on outside of Gnus, using Gnus, so that I don't have to
duplicate my configuration for w3.

Come to think if it though, I have never yet seen a message
with a mailto url...

    William> uses _message_, not Gnus for sending the mail.  There
    William> might be a case for having w3 allow customization of
    William> posting styles based on email address or the URL the link
    William> is on, something like that.

No - I would much prefer a Gnus function that w3 can call "send mail
with these headers". That way, there is no need to re-invent the rule
and redo what has already been implemented.

Of course, it gets a bit messier when you deal with multiple groups,
and possibly this needs to be discussed a bit more. I would be happy
if everything just matched a preset group, eg "w3". Another
alternative, is that w3 could somehow track which group you originally
loaded the web page from (if any). I suspect this might be difficult
to implement and use though.

As I have already said earlier, I don't think it matters if there
is the requirement "Gnus must be running beforehand".
-- 
Brian May <bmay@csse.monash.edu.au>


  reply	other threads:[~1999-12-07  5:59 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-11-24  0:06 Forwarding Mail Messages Brian May
1999-12-01 19:47 ` Lars Magne Ingebrigtsen
1999-12-02  0:42   ` Nevin Kapur
1999-12-02  1:19     ` What now? (was: Forwarding Mail Messages) Lars Magne Ingebrigtsen
1999-12-02  2:59       ` What now? Brian May
1999-12-02 16:23         ` Colin Marquardt
1999-12-02 16:56         ` Jody M. Klymak
1999-12-06  4:26           ` Lars Magne Ingebrigtsen
1999-12-06  5:31             ` Brian May
1999-12-07  5:36               ` William M. Perry
1999-12-07  5:59                 ` Brian May [this message]
1999-12-07 16:09                   ` William M. Perry
1999-12-08  8:02                     ` nnimap URLs? (Was: What now?) Steinar Bang
1999-12-08 16:08                       ` William M. Perry
1999-12-08 18:02                         ` Simon Josefsson
1999-12-08 18:23                           ` William M. Perry
1999-12-08 17:26                       ` Simon Josefsson
1999-12-10 16:07                         ` William M. Perry
1999-12-08 22:51                     ` What now? Brian May
1999-12-06 17:36             ` Jody M. Klymak
1999-12-06 20:34               ` Bruce Stephens
1999-12-06 22:38               ` Kai Großjohann
1999-12-03 19:12       ` What now? (was: Forwarding Mail Messages) Jody M. Klymak
1999-12-04 17:05         ` Hrvoje Niksic
1999-12-04 22:53           ` Jody M. Klymak
2000-04-21 21:13         ` Lars Magne Ingebrigtsen
2000-04-21 21:05           ` William M. Perry
2000-04-21 21:16             ` Arcady Genkin
2000-04-21 23:32               ` William M. Perry
2000-04-22  9:36             ` Hans de Graaff
1999-12-05 21:46       ` Kai Großjohann
1999-12-05 21:51       ` Kai Großjohann
1999-12-06  1:27       ` Richard Hoskins
1999-12-02  1:48   ` Forwarding Mail Messages Brian May
1999-12-06  4:12     ` Lars Magne Ingebrigtsen

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=t4iogc3fg0q.fsf@silas-2.cc.monash.edu.au \
    --to=bmay@csse.monash.edu.au \
    /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).