From: Lars Magne Ingebrigtsen <larsi@ifi.uio.no>
Subject: Re: missing feedback
Date: 16 Apr 1996 23:58:29 +0200 [thread overview]
Message-ID: <w8s68azg7ay.fsf@hler.ifi.uio.no> (raw)
In-Reply-To: <2645.9604151616@grogan.cogsci.ed.ac.uk>
"Henry S. Thompson" <ht@cogsci.ed.ac.uk> writes:
> 1) The reassuring parade of article numbers in the message buffer
> during long content searches (M-s, search-article-forward);
(setq gnus-verbose 10)
> 2) Some idea of what's happening during news reading: After
> NNTP: Reading ........
> I get a palpable (>10 seconds) pause before my few NNSPOOL method
> groups (local fake mail-to-news stuff) start flickering by at the
> limits of invisibility. What's happening during that dead time?
After the "Reading ..." thing, there's usually not much of a pause for
me. Do you have massive amounts of (un)subscribed groups? That could
explain it.
To find out where Gnus is spending so much time:
(setq debug-on-quit t)
and `C-g' when it's working.
> Also, is there any way to be saved from myself in a way which gnus
> manages because .newsrc is actually in a buffer, namely that if I am
> running Gnus on one machine, run it AGAIN (e.g. from home) and read
> a bunch of news and exit, then quitting Gnus on the first machine
> the next day DOESN'T notice that .newsrc[.eld] has changed and
> simply overwrites?
Nope, sorry.
--
"Yes. The journey through the human heart
would have to wait until some other time."
prev parent reply other threads:[~1996-04-16 21:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-04-15 16:16 Henry S. Thompson
1996-04-15 18:45 ` Colin Rafferty
1996-04-15 20:13 ` Steven L Baur
1996-04-15 18:47 ` Colin Rafferty
1996-04-15 19:00 ` Paul D. Smith
1996-04-15 19:45 ` William Perry
1996-04-15 19:51 ` Paul D. Smith
1996-04-16 21:58 ` Lars Magne Ingebrigtsen [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=w8s68azg7ay.fsf@hler.ifi.uio.no \
--to=larsi@ifi.uio.no \
/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).