Gnus development mailing list
 help / color / mirror / Atom feed
From: Andreas Seltenreich <andreas+ding@gate450.dyndns.org>
Subject: Re: nnweb + Gmane search
Date: Sat, 11 Feb 2006 10:23:30 +0100	[thread overview]
Message-ID: <87fymquu3x.fsf@gate450.dyndns.org> (raw)
In-Reply-To: <loom.20060209T132346-579@post.gmane.org> (Olly Betts's message of "Thu, 9 Feb 2006 12:28:56 +0000 (UTC)")

Olly Betts writes:

> Olly Betts <olly@survex.com> writes:
>> How does this first attempt look:
>> 
>> http://search.gmane.org/cgi-bin/omega.cgi?FMT=nov&query=gnus+nnweb
>> 
>> The first line is either an error, or:
>> 
>> OK <total (estimated) matches> <number of matches which follow> <match time>
>
> Forgot to say - if any of the current output format is inconvenient, I
> can probably easily fix it.  In particular, I suspect the current date
> format will probably want adjusting to be a valid date in news format.

If I correctly interpreted <news:nov-faq-1-817902143@agate.Berkeley.EDU>,
one would also have to put numbers in the first column, and the
optional xref header comes one field too early and would need to
actually be prefixed with "Xref: " to yield a proper nov-line.

Don't get me wrong, the current format is /perfectly/ fine with nnweb,
since nnweb generates article numbers using the Xref content anyway,
but if more software is supposed to use this interface, one might want
to get it right the first time.

| Beware the URL and format may not be stable, so don't build it into
| anything just yet.  

I'll hold my breath :-)

Thanks!
Andreas



  reply	other threads:[~2006-02-11  9:23 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-31  9:42 nnweb fix Andreas Seltenreich
2005-12-31 10:48 ` Andreas Seltenreich
2006-01-04  0:18   ` Reiner Steib
2006-01-04 12:25     ` Andreas Seltenreich
2006-01-27  8:35     ` Andreas Seltenreich
2006-01-30 15:08       ` Reiner Steib
2006-01-31  5:48         ` Andreas Seltenreich
2006-01-31 16:03           ` Reiner Steib
2006-01-31 17:06             ` Andreas Seltenreich
2006-02-03 13:20               ` Reiner Steib
2006-02-12  6:34                 ` Andreas Seltenreich
2006-02-13 13:35                   ` Reiner Steib
2006-02-08  5:56             ` nnweb + Gmane search (was: nnweb fix) Andreas Seltenreich
2006-02-08  7:56               ` Olly Betts
2006-02-09  4:47                 ` nnweb + Gmane search Andreas Seltenreich
2006-02-09 10:41                   ` Olly Betts
2006-02-09 12:28                     ` Olly Betts
2006-02-11  9:23                       ` Andreas Seltenreich [this message]
2006-02-13 10:23                         ` Olly Betts
2006-02-14 19:55                           ` Andreas Seltenreich
2006-02-23 17:53                             ` Reiner Steib
2006-02-23 23:04                               ` Olly Betts
2006-02-24  0:49                                 ` Andreas Seltenreich
2006-02-24 12:07                                 ` Olly Betts
2006-02-24 14:31                                   ` Reiner Steib
2006-02-24 15:34                                     ` Olly Betts
2006-02-24 21:58                                     ` Andreas Seltenreich
2006-02-24 23:24                                       ` Reiner Steib

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=87fymquu3x.fsf@gate450.dyndns.org \
    --to=andreas+ding@gate450.dyndns.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).