From: Brian May <bmay@csse.monash.edu.au>
Cc: ding@gnus.org
Subject: Re: What now?
Date: 09 Dec 1999 09:51:37 +1100 [thread overview]
Message-ID: <t4ik8mpkpvq.fsf@silas-2.cc.monash.edu.au> (raw)
In-Reply-To: wmperry@aventail.com's message of "Tue, 07 Dec 1999 08:09:12 -0800"
>>>>> "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.
William> This is changed with the new version of URL - I am in the
William> midst of rewriting url-news.el right now.
Ok... Thats Good.
>> 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.
William> Well, news and nntp URLs are theoretically just for NNTP
William> access. Gnus is not exactly envisioned by the guys who
William> wrote the URL for news. :) I couldn't find any sort of
William> 'get this messageid regardless of backend'. If there is
William> one, could someone send it to me?
Both M-^ and news URLS from Gnus seem to be able to fetch articles,
regardless of source...
Hang on, no, it depends on the current group selected. If I am in a
NNTP group, I cannot find a mail message (at least for M-^, I haven't
tested news URLS). I would imagine it might be possible to query each
back end in turn??? Perhaps allow the user to select order of
priority?
William> THen they have been embedded in the document wrong. This
William> is what the
William> <URL:news:t4in1ruvyij.fsf_-_@silas-2.cc.monash.edu.au>... syntax
William> is for. :)
Thats what I thought too. Does Gnus provide any macros to automate
creating these?
--
Brian May <bmay@csse.monash.edu.au>
next prev parent reply other threads:[~1999-12-08 22:51 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
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 ` Brian May [this message]
1999-12-06 17:36 ` What now? 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=t4ik8mpkpvq.fsf@silas-2.cc.monash.edu.au \
--to=bmay@csse.monash.edu.au \
--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).