From: Simon Josefsson <jas@extundo.com>
Cc: emacs-pretest-bug@gnu.org
Subject: Re: Gnus issues
Date: Fri, 15 Oct 2004 00:46:14 +0200 [thread overview]
Message-ID: <ilu4qkwyl3d.fsf@latte.josefsson.org> (raw)
In-Reply-To: <rzq3c0hkmsv.fsf@albion.dl.ac.uk>
Dave Love <fx@gnu.org> writes:
> It seems it still uses nnheader-accept-process-output, which it
> shouldn't. A reasonable solution to that, which I should probably
> have used elsewhere before, is to compile it away. nnheader could
> just be required at compile time if nnheader-accept-process-output is
> made a defsubst (with a comment about why).
n-a-p-o uses a variable, nnheader-read-timeout, so if it is a
defsubst, wouldn't either the user lose the ability to customize the
variable, or that nnheader.el is loaded for the variable?
Btw, I should installed a fix to make pop3.el not depend on nnheader.
I copied the nnheader code, which may be bad, though.
OTOH, I'm not sure why we bother. The entire n-a-p-o stuff seem to be
workaround for a problem on non-unix platforms. Wouldn't it be better
if the people using those platforms fix accept-process-output to do
the right thing, instead of messing up the lisp code?
I would support using accept-process-output directly in pop3.el.
prev parent reply other threads:[~2004-10-14 22:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <rzqmzzbv1y2.fsf@albion.dl.ac.uk>
2004-09-29 21:52 ` Reiner Steib
2004-09-30 3:33 ` Katsumi Yamaoka
2004-10-08 17:03 ` Dave Love
2004-10-08 17:31 ` Jesper Harder
2004-10-08 21:59 ` Reiner Steib
2004-09-30 22:07 ` Dave Love
2004-09-30 22:51 ` Simon Josefsson
2004-10-01 0:38 ` Steve Youngs
2004-10-01 2:02 ` Edward O'Connor
2004-10-01 9:14 ` Simon Josefsson
2004-10-01 13:26 ` Miles Bader
2004-10-03 14:33 ` Richard Stallman
2004-10-01 6:36 ` Katsumi Yamaoka
2004-10-02 19:09 ` Reiner Steib
2004-10-08 17:09 ` Dave Love
2004-10-10 17:50 ` Reiner Steib
2004-10-14 21:33 ` Dave Love
2004-10-14 22:46 ` Simon Josefsson [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=ilu4qkwyl3d.fsf@latte.josefsson.org \
--to=jas@extundo.com \
--cc=emacs-pretest-bug@gnu.org \
/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).