Gnus development mailing list
 help / color / mirror / Atom feed
From: ShengHuo ZHU <zsh@cs.rochester.edu>
Subject: Re: nnslashdot usage
Date: Mon, 10 Dec 2001 14:41:50 -0500	[thread overview]
Message-ID: <2nbsh6rhfl.fsf@zsh.cs.rochester.edu> (raw)
In-Reply-To: <81667eopv8.fsf@zion.bpnetworks.com> (Ami Fischman's message of "Mon, 10 Dec 2001 11:07:55 -0800")

Ami Fischman <usenet@fischman.org> writes:

> ShengHuo ZHU <zsh@cs.rochester.edu> writes:
>
> [...]
>
>> nnrss:Slashdot lists topics as articles, but it doesn't show the
>> followups.  The all-in-one solution is difficult to implement, because
>> of the difficulties in maintaining the map of article numbers.
>
> Thanks for the reply.  Gave nnrss a shot, but it doesn't seem to
> automatically fetch the stories here (i.e., each article shows up as just a
> URL to the story).  Is that intentional?  Is there a way to force the
> retrieval of the story without explicitly clicking on the widget in the
> article?  I'm using the browse-nnrss-url function from the  info file:

nnrss is a backend for files in RSS (or RDF) format.  Slashdot
provides such a file, but no descriptions, therefore, no stories.

> (require 'nnrss)
> (require 'browse-url)
> (defun browse-nnrss-url( arg )
>   (interactive "p")
>   (let ((url (assq nnrss-url-field
> 		   (mail-header-extra
> 		    (gnus-data-header
> 		     (assq (gnus-summary-article-number)
> 			   gnus-newsgroup-data))))))
>     (message "URL: ")
>     (message url)
>     (if url
> 	(browse-url (cdr url))
>       (gnus-summary-scroll-up arg))))
> (eval-after-load "gnus"
>   #'(define-key gnus-summary-mode-map
>       (kbd "<RET>") 'browse-nnrss-url))
> (add-to-list 'nnmail-extra-headers nnrss-url-field)
>
> but all the article buffer shows after I've hit "RET" in the summary buffer
> is a highlighted URL...

It sends the URL to your (external) browser.  (Actually, I don't use
this code.)

> Is the "all-in-one" solution something that you have any plans/hopes of
> implementing?  Or are you happy with nnslashdot as it is now?

Maybe nnslashdot is a little strange at the first sight. However,
after using it for two years, I am happy with it.  So, I am not going
to implement the all-in-one solution. Does anyone want to implement
it?

ShengHuo



  reply	other threads:[~2001-12-10 19:41 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-09 22:15 Ami Fischman
2001-12-10 17:36 ` ShengHuo ZHU
2001-12-10 19:07   ` Ami Fischman
2001-12-10 19:41     ` ShengHuo ZHU [this message]
2001-12-11 20:43   ` Ami Fischman
2001-12-11  9:39 ` Kai Großjohann
2001-12-11 17:34   ` Ami Fischman
2001-12-29  0:55 ` Lars Magne Ingebrigtsen
2001-12-29  2:21   ` ShengHuo ZHU
2001-12-29  2:34     ` Lars Magne Ingebrigtsen
  -- strict thread matches above, loose matches on Subject: below --
1999-11-11 19:30 Bruce Z. Lysik
1999-11-11 21:47 ` Shenghuo ZHU
1999-11-11 22:00   ` Laura Conrad
1999-11-11 22:06   ` Bruce Z. Lysik

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=2nbsh6rhfl.fsf@zsh.cs.rochester.edu \
    --to=zsh@cs.rochester.edu \
    /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).