Gnus development mailing list
 help / color / mirror / Atom feed
From: Wesley.Hardaker@sphys.unil.ch
Subject: nnweb observations
Date: 10 Oct 1996 15:16:45 +0100	[thread overview]
Message-ID: <qk2919ec3aq.fsf@iptsun2.unil.ch> (raw)


Well, I really like playing with nnweb...  I've been doing so for an
hour or so.  Lots of fun.  Sure wish it worked as advertised though...

- altavista searches didn't work at all ("couldn't load group" or
  something like that)

- dejanews searches worked but had lots of problems when actually
  reading the articles.  Mostly, it displayed the article full of html
  code, which should be run through w3 or retrieve the text version
  instead.  Imediately after loading the article it bombs out with:

     Signalling: (error "Keyboard macro terminated by a command ringing the bell")
       ding()
       gnus-error(1 "No such article (may have expired or been canceled)")
       gnus-article-prepare(1 nil)
       gnus-summary-display-article(1 nil)
       gnus-summary-select-article(nil nil pseudo)
       gnus-summary-scroll-up(1)
       call-interactively(gnus-summary-scroll-up)

- Lots of errors creating groups:
    format specifier %d doesn't match argument type
  This then produces
    Undefined definition map
  when you try 'M-g' on most of the other groups.

- Sometimes you get an error like:
    Connection failed, retry?
  which happens at the same time as another buffer is displayed with
  the warning:
    A connection is alread in progress with search.dejanews.com

- When you actually try to read an article, it highlights the line as
  'canceled' (ie, black background yellow foreground) but displays the
  article (along with the above stack trace).  At this point
  gnus-summary-scroll-article-up or down fails and trys to read the
  article above or below the current one even though the html'icied
  article is much longer than a page and needs scrolling.

- Re-reading an article that you've already read once in the summary
  buffer (without exit/re-entering) displays an empty buffer (and some
  error I'm forgetting).

Wheee
Cool though!
Wes


             reply	other threads:[~1996-10-10 14:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-10-10 14:16 Wesley.Hardaker [this message]
1996-10-11  6:48 ` Wesley.Hardaker

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=qk2919ec3aq.fsf@iptsun2.unil.ch \
    --to=wesley.hardaker@sphys.unil.ch \
    /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).