gnus-asynchronous

gnus-asynchronous

[Istvan Marko]

Here is a public NNTP server that hangs with 0.52 and 0.53 when
gnus-asynchronous is set:

nntp+news.3dfx.com:3dfx.glide.linux

-- 
	Istvan

Re: gnus-asynchronous

[Felix Lee]

sorry, I still can't reproduce the problem.  that group
works fine for me.

I suspect it's a side-effect of some weird non-obvious emacs
or gnus setting.  until someone can track this down, I'll
just write some code that will compensate for unknown
problems.

Istvan Marko <imarko@pacificnet.net>:
> Here is a public NNTP server that hangs with 0.52 and 0.53 when
> gnus-asynchronous is set:
> 
> nntp+news.3dfx.com:3dfx.glide.linux
> 
> -- 
> 	Istvan
> 

Re: gnus-asynchronous

[Raja R Harinath]

Felix Lee <flee@teleport.com> writes:
> Istvan Marko <imarko@pacificnet.net>:
> > Here is a public NNTP server that hangs with 0.52 and 0.53 when
> > gnus-asynchronous is set:
> > 
> > nntp+news.3dfx.com:3dfx.glide.linux
>  
> sorry, I still can't reproduce the problem.  that group
> works fine for me.
> 
> I suspect it's a side-effect of some weird non-obvious emacs
> or gnus setting.  until someone can track this down, I'll
> just write some code that will compensate for unknown
> problems.

While I didn't try the above server, I have similar problems on my
server.  

The problem is:

It doesn't hang on the first article.  When I hit SPC for the next
article (#2), it just hangs in "Fetching async article..." or something
similar.  I can hit C-g to get out.  If I reselect article #2, it again
hangs.  However, if I choose article #3, it fetches it without problems.
After that, if I go back and select #2, it is fetched and displayed
without problems, and the rest of the newsgroup is readable without
problems.

- Hari
-- 
Raja R Harinath ------------------------------ harinath@cs.umn.edu
"When all else fails, read the instructions."      -- Cahn's Axiom
"Our policy is, when in doubt, do the right thing."   -- Roy L Ash

Re: gnus-asynchronous

[Felix Lee]

I just thought of a new theory, a possible race condition in
nntp's use of the after-change hook.  I'll try to fix that
too.  patch in about a day.
--

Re: gnus-asynchronous

[Felix Lee]

urggg.  I finally reproduce the problem, and after banging
against the wall for a while, I discover it's a bug in emacs
20.3.  after-change-functions aren't run when a process
spews into a buffer.  (unless emacs does encoding stuff,
which is never going to happen in this case.)

this changes everything.  sort of.  maybe.

gnus-async is going to be useless in emacs 20.3
unless.. something.. nasty.. happens...
--

gnus-asynchronous

[Simon Josefsson]

`gnus-asynchronous' seemed to be defined twice, with different default
values. I've removed the definition in gnus.el, which means Gnus is
now asynchronous by default (it's huge gain against slow IMAP servers).

gnus.el:

(defcustom gnus-asynchronous nil
  "*If non-nil, Gnus will supply backends with data needed for async article fetching."
  :group 'gnus-asynchronous
  :type 'boolean)

gnus-async.el:

(defcustom gnus-asynchronous t
  "*If nil, inhibit all Gnus asynchronicity.
If non-nil, let the other asynch variables be heeded."
  :group 'gnus-asynchronous
  :type 'boolean)