diff options
| author | Miles Bader <miles@gnu.org> | 2004-10-12 02:25:56 +0000 |
|---|---|---|
| committer | Miles Bader <miles@gnu.org> | 2004-10-12 02:25:56 +0000 |
| commit | e62e7654ac785834b72bfb8784ff34d203d3190f (patch) | |
| tree | a070f2fe34b219c630343526193543c43ae5f607 /lisp/gnus/nnheader.el | |
| parent | 332e51c15c33e5033344932424f4f7af99607ffd (diff) | |
| download | emacs-e62e7654ac785834b72bfb8784ff34d203d3190f.tar.gz | |
Revision: miles@gnu.org--gnu-2004/emacs--cvs-trunk--0--patch-610
Merge from gnus--rel--5.10
Patches applied:
* miles@gnu.org--gnu-2004/gnus--rel--5.10--patch-45
Update from CVS
Diffstat (limited to 'lisp/gnus/nnheader.el')
| -rw-r--r-- | lisp/gnus/nnheader.el | 10 |
1 files changed, 9 insertions, 1 deletions
diff --git a/lisp/gnus/nnheader.el b/lisp/gnus/nnheader.el index 1b6ec636734..7df5ecae205 100644 --- a/lisp/gnus/nnheader.el +++ b/lisp/gnus/nnheader.el @@ -74,7 +74,15 @@ Integer values will in effect be rounded up to the nearest multiple of (defvar nnheader-read-timeout (if (string-match "windows-nt\\|os/2\\|emx\\|cygwin" (symbol-name system-type)) - 1.0 ; why? + ;; http://thread.gmane.org/v9655t3pjo.fsf@marauder.physik.uni-ulm.de + ;; + ;; IIRC, values lower than 1.0 didn't/don't work on Windows/DOS. + ;; + ;; There should probably be a runtime test to determine the timing + ;; resolution, or a primitive to report it. I don't know off-hand + ;; what's possible. Perhaps better, maybe the Windows/DOS primitive + ;; could round up non-zero timeouts to a minimum of 1.0? + 1.0 0.1) "How long nntp should wait between checking for the end of output. Shorter values mean quicker response, but are more CPU intensive.") |