From: "William M. Perry" <wmperry@aventail.com>
Cc: The Ding List <ding@ifi.uio.no>
Subject: Re: slow splitting
Date: Fri, 10 Jan 1997 08:38:26 -0800 [thread overview]
Message-ID: <199701101638.IAA13590@newman> (raw)
In-Reply-To: <yviazpyi2nhl.fsf@atreides.mindspring.com>
Sudish Joseph writes:
>Chris Jones writes:
>> Should I turn these hook expressions into full-fledged patches, and
>> send them in? The reason I'm asking is this: If you're running on a
>> really fast box (and you have simple splitting rules, which I don't),
>> those messages could just whiz by you, potentially causing some worry
>> because the thing's printing messages that you don't get an
>> opportunity to read.
>
>The jwz-enhanced GNUS that was standard with XEmacs until 19.13(12?)
>had a messaging function that tried not to call 'message if messages
>occured too close to each other. I do not recollect if it was based
>on time or print-nth-message, but you might look it up if you have
>access to that version of GNUS.
There is a similar function in the url package that will only do it every
'n' seconds.
-bill
prev parent reply other threads:[~1997-01-10 16:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-01-09 23:08 Chris Jones
1997-01-10 0:39 ` Karl Anderson
1997-01-10 3:55 ` Sudish Joseph
1997-01-10 16:38 ` William M. Perry [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=199701101638.IAA13590@newman \
--to=wmperry@aventail.com \
--cc=ding@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).