Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: nnslashdot
Date: 07 Nov 1999 20:35:30 +0100	[thread overview]
Message-ID: <m34seyumbh.fsf@quimbies.gnus.org> (raw)

Hm.  nnimap has the same problem, I think -- there are some natural
group names that can't be done under the current Gnus group name
regime, most notably group names with spaces in them.

But if we just allow *-request-list to answer with lines that look
like

"This is a really weird group name" 9 1 m

then everything will work, as if by magic.  So I've done that, and
made nnslashdot use then (uniquified) article title as the group name, 
which means that the group buffer looks kinda like:

     81: Amazon.com switches to Apache (99/11/05/0947259)
    141: Caldera vs. Microsoft Goes to Jury Trial (99/11/05/0814243)
    120: Checkpoint Porting Firewall-1 to Linux (99/11/06/1018228)
     79: Cobalt IPO Opens...High (99/11/05/1113248)

It's in CVS.

The more serious problem with nnslashdot is that when requesting the
comments strictly sorted by age (which is nice, since that means not
having to fetch the entire list of comments when entering the group),
all the threading info is gone.  (That is, the "Parent" link is
"cid"-less.)  Looks kinda like a bug in Slashdot to me.  

-- 
(domestic pets only, the antidote for overdose, milk.)
   larsi@gnus.org * Lars Magne Ingebrigtsen


             reply	other threads:[~1999-11-07 19:35 UTC|newest]

Thread overview: 70+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-11-07 19:35 Lars Magne Ingebrigtsen [this message]
1999-11-08  4:19 ` nnslashdot Shenghuo ZHU
  -- strict thread matches above, loose matches on Subject: below --
2000-05-11 11:08 nnslashdot Lars Magne Ingebrigtsen
2000-05-11 15:05 ` nnslashdot BrYan P. Johnson
2000-05-11 15:13   ` nnslashdot BrYan P. Johnson
2000-05-11 15:19   ` nnslashdot dme
2000-05-12 15:49 ` nnslashdot Kai Großjohann
2000-05-12 16:27   ` nnslashdot Alan Shutko
2000-05-12 17:28     ` nnslashdot Kai Großjohann
1999-11-07  6:32 nnslashdot Lars Magne Ingebrigtsen
1999-11-07  6:42 ` nnslashdot Lars Magne Ingebrigtsen
1999-11-08 22:51 ` nnslashdot Dan Christensen
1999-11-08 22:59   ` nnslashdot Shenghuo ZHU
1999-11-08 23:23     ` nnslashdot Dan Christensen
1999-11-08 23:57       ` nnslashdot Lars Magne Ingebrigtsen
1999-11-09  0:35       ` nnslashdot Matt Pharr
1999-11-08 23:53         ` nnslashdot Dan Christensen
1999-11-09  0:09           ` nnslashdot Lars Magne Ingebrigtsen
1999-11-09  1:15             ` nnslashdot Matt Pharr
1999-11-09  0:37         ` nnslashdot Matt Pharr
1999-11-09  0:17           ` nnslashdot Lars Magne Ingebrigtsen
1999-11-09  1:17             ` nnslashdot Matt Pharr
1999-11-09  0:23               ` nnslashdot Lars Magne Ingebrigtsen
1999-11-09  6:32                 ` nnslashdot Matt Pharr
1999-11-09  6:19                   ` nnslashdot Shenghuo ZHU
1999-11-10 20:55                     ` nnslashdot Matt Pharr
1999-11-10 21:56                       ` nnslashdot Kai Großjohann
1999-11-11 16:35                       ` nnslashdot Lars Magne Ingebrigtsen
1999-11-11 23:08                         ` nnslashdot Matt Pharr
1999-11-12  4:30                           ` nnslashdot Lars Magne Ingebrigtsen
1999-11-12  6:16                             ` nnslashdot Norbert Koch
1999-11-12  8:03                             ` nnslashdot Hrvoje Niksic
1999-11-12  8:26                               ` nnslashdot Lars Magne Ingebrigtsen
1999-11-12 10:16                                 ` nnslashdot Steinar Bang
1999-11-12 11:01                                   ` nnslashdot Lars Magne Ingebrigtsen
1999-11-14 15:42                     ` nnslashdot Jack Twilley
1999-11-15 19:51                       ` nnslashdot Lars Magne Ingebrigtsen
1999-11-16 19:25                         ` nnslashdot Jack Twilley
1999-12-01 15:20                           ` nnslashdot Lars Magne Ingebrigtsen
1999-11-09 21:03       ` nnslashdot Kevin Ryde
1999-11-08 23:51   ` nnslashdot Lars Magne Ingebrigtsen
1999-11-09  0:58     ` nnslashdot Matt Pharr
1999-11-09  0:07       ` nnslashdot Lars Magne Ingebrigtsen
1999-11-09  1:09         ` nnslashdot Matt Pharr
1999-11-09  4:29     ` nnslashdot Dan Christensen
1999-11-09 14:23       ` nnslashdot Lars Magne Ingebrigtsen
1999-11-10  4:54         ` nnslashdot Dan Christensen
1999-07-07  7:16 nnslashdot Lars Magne Ingebrigtsen
1999-07-07  7:16 ` nnslashdot David Hedbor
1999-07-07  7:42   ` nnslashdot Lars Magne Ingebrigtsen
1999-07-07 12:08     ` nnslashdot Chris Halverson
1999-07-07 18:30     ` nnslashdot David Hedbor
1999-07-07 10:47 ` nnslashdot Jon K Hellan
1999-07-09 17:17   ` nnslashdot Lars Magne Ingebrigtsen
1999-07-07 20:56 ` nnslashdot Wes Hardaker
1999-07-07 22:55   ` nnslashdot David Hedbor
1999-07-08 11:31     ` nnslashdot Kai.Grossjohann
1999-07-08 22:16       ` nnslashdot David Hedbor
1999-07-09 17:23   ` nnslashdot Lars Magne Ingebrigtsen
1999-07-09 17:24     ` nnslashdot Ted Rathkopf
1999-07-12 13:01     ` nnslashdot Jan Vroonhof
1999-08-27 17:36       ` nnslashdot Lars Magne Ingebrigtsen
1999-07-12 15:44     ` nnslashdot Wes Hardaker
1999-07-12 20:13       ` nnslashdot Simon Josefsson
1999-07-12 21:09         ` nnslashdot Wes Hardaker
1999-07-13  0:48         ` nnslashdot Rob Browning
1999-07-13 11:20         ` nnslashdot Kim-Minh Kaplan
1999-07-13 12:45           ` nnslashdot Simon Josefsson
1999-07-21 22:29           ` nnslashdot Carl R. Witty
1999-07-26 11:59             ` nnslashdot Kim-Minh Kaplan

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=m34seyumbh.fsf@quimbies.gnus.org \
    --to=larsi@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).