From: ShengHuo ZHU <zsh@cs.rochester.edu>
Subject: Re: Suddenly can't subscribe to nnslashdot groups with 'F' ?
Date: 12 Jan 2001 17:42:08 -0500 [thread overview]
Message-ID: <2nwvc0crzz.fsf@tiger.jia.vnet> (raw)
In-Reply-To: <20010110143753.A10959@sci.fi>
Anssi Saari <as@sci.fi> writes:
> Hi,
>
> I've been happily reading slashdot with Gnus all year, but since yesterday
> I can't subscribe the nnslashdot groups any more with 'F'. I just get
> Wrong type argument: stringp, ("nnslashdot") or with debug-on-error
> set to t the dump below. Manual subscribing through the server buffer
> works though. I upgraded to last night's snapshot, but no change.
>
> Signaling: (wrong-type-argument stringp ("nnslashdot"))
Type `G p' on the topic line. You should see something like
((subscribe . "nnslashdot")). The problem is that you might miss the
dot between subscribe and "nnslashdot".
ShengHuo
next prev parent reply other threads:[~2001-01-12 22:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-10 12:37 Anssi Saari
2001-01-12 22:42 ` ShengHuo ZHU [this message]
2001-01-15 11:37 ` Anssi Saari
2001-01-16 19:46 ` Old bug reappearing in 5.8.8 Colin Marquardt
2001-01-16 20:17 ` ShengHuo ZHU
2001-01-16 21:12 ` Colin Marquardt
2001-01-17 2:09 ` ShengHuo ZHU
2001-01-17 3:07 ` Old bug reapqpearing " Colin Marquardt
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=2nwvc0crzz.fsf@tiger.jia.vnet \
--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).