From: * Tong * <sun_tong@users.sourceforge.net>
Subject: Re: Gnus reset and start fresh
Date: Thu, 16 Oct 2003 22:49:23 GMT [thread overview]
Message-ID: <dece189fd5c9f22d5f3655ce21860851@news.teranews.com> (raw)
In-Reply-To: <7055934a733b5d4fa86f267b89d976e1@news.teranews.com>
On Thu, 16 Oct 2003 22:23:06 +0000, * Tong * wrote:
> * Tong * <sun_tong@users.sourceforge.net> writes:
>
>> [...] I guess it is my own setting's problem now. :-)
>
> Hi, my gnus gets into a bewildering stage:
>
> [...]
> - I can't see my posting: In comp.test, I can read/post, but I was
> having a hard time seeing my posting coming up in gnus. The new
> posting shows up instantly in pan, but in gnus, I 'g' in group
> window many many time, still can't see my new posting. I am able
> to see them though, after many twisting, might be the exit and
> come back again did the trick.
Correction #1, exit and come back again won't do the trick. Have to wait
excessively long. This time 5 minutes later, gnus still unable to pick up
my new posting (while pan picks up instantly).
Correction #2, this happens to all news groups that I posted. Beside
comp.test, I also just posted to here and comp.unix.shell. I haven't seen
them in gnus yet. I'm now posting with my pan.
--
Tong (remove underscore(s) to reply)
*niX Power Tools Project: http://xpt.sourceforge.net/
- All free contribution & collection
prev parent reply other threads:[~2003-10-16 22:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5ac94456dd95a05606393951dbca04bb@news.teranews.com>
[not found] ` <87b951075a86f0d9d430407d465e9ace@news.teranews.com>
2003-10-16 19:26 ` Gnus and free.teranews.com * Tong *
[not found] ` <7055934a733b5d4fa86f267b89d976e1@news.teranews.com>
2003-10-16 22:49 ` * Tong * [this message]
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=dece189fd5c9f22d5f3655ce21860851@news.teranews.com \
--to=sun_tong@users.sourceforge.net \
/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).