Plugged or not?

Plugged or not?

[Robert Epprecht]

CVS Gnus from a few minutes ago:

I start Gnus with 
emacs -f gnus

I have the following line in my .gnus.el
(setq gnus-plugged nil)
and the Agent did this like I wanted since a long time, but now something
has changed:  While the Agent still seems to be unplugged (i.e. can't fetch
articles) the Mode line of the Summary buffer pretends the contrary:

Just after starting:
-:---F1  Gnus: *Group* {nntp:news.cis.dfn.de}      (Group Topic Plugged)--L2-
C-h v gnus-plugged says: gnus-plugged's value is nil

I do 'J j' and see:
-:---F1  Gnus: *Group* {nntp:news.cis.dfn.de}      (Group Topic Plugged)--L1-
C-h v gnus-plugged:  gnus-plugged's value is t

I do another 'J j':
-:---F1  Gnus: *Group* {nntp:news.cis.dfn.de}      (Group Topic Unplugged)--L1
C-h v gnus-plugged:  gnus-plugged's value is nil

Strange...
BTW What's the L2/L1 thing at the end of the line?

Robert Epprecht

Re: Plugged or not?

[Kevin Greiner]

Robert Epprecht <epprecht@solnet.ch> writes:

> CVS Gnus from a few minutes ago:
>
> I start Gnus with 
> emacs -f gnus
>
> I have the following line in my .gnus.el
> (setq gnus-plugged nil)
> and the Agent did this like I wanted since a long time, but now something
> has changed:  While the Agent still seems to be unplugged (i.e. can't fetch
> articles) the Mode line of the Summary buffer pretends the contrary:

Robert,
Just as a test, try replacing (setq gnus-plugged nil) with (gnus-agent-toggle-plugged nil).

>
> Just after starting:
> -:---F1  Gnus: *Group* {nntp:news.cis.dfn.de}      (Group Topic Plugged)--L2-
> C-h v gnus-plugged says: gnus-plugged's value is nil
>
> I do 'J j' and see:
> -:---F1  Gnus: *Group* {nntp:news.cis.dfn.de}      (Group Topic Plugged)--L1-
> C-h v gnus-plugged:  gnus-plugged's value is t
>
> I do another 'J j':
> -:---F1  Gnus: *Group* {nntp:news.cis.dfn.de}      (Group Topic Unplugged)--L1
> C-h v gnus-plugged:  gnus-plugged's value is nil
>
> Strange...
> BTW What's the L2/L1 thing at the end of the line?

Line number?

Kevin

Re: Plugged or not?

[Robert Epprecht]

Kevin Greiner <kgreiner@xpediantsolutions.com> writes:

> Robert Epprecht <epprecht@solnet.ch> writes:

> Just as a test, try replacing (setq gnus-plugged nil) with (gnus-agent-toggle-plugged nil).

.gnus.el:
(gnus-agent-toggle-plugged nil)

Error in ~/.gnus: gnus-agent-toggle-plugged

(Another CVS update did not change this...)

After changing back .gnus.el I tried:
M-x apropos <RET> gnus-agent-toggle-plugged <RET>

gnus-agent-toggle-plugged
  Command: Toggle whether Gnus is unplugged or not.

So I try:
.gnus.el:
(gnus-agent-toggle-plugged) ;; without parameter nil

Error in ~/.gnus: gnus-agent-toggle-plugged


Next try:
.gnus.el:
(setq debug-on-error t)
(gnus-agent-toggle-plugged nil)

Debugger entered--Lisp error: (error "Error in ~/.gnus: gnus-agent-toggle-plugg$  signal(error ("Error in ~/.gnus: gnus-agent-toggle-plugged"))
  error("Error in %s: %s" "~/.gnus" gnus-agent-toggle-plugged)
  byte-code("AÄ^H       \211^ZA@)#\207" [file var x error "Error in %s: %s"] 5)
  gnus-read-init-file()
  gnus-1(nil nil nil)
  gnus()
  command-line-1(("-f" "gnus"))
  command-line()
  normal-top-level()



>> BTW What's the L2/L1 thing at the end of the line?
> Line number?
Oups, sorry, seems I'm blind...

Robert

Re: Plugged or not?

[Kevin Greiner]

Robert Epprecht <epprecht@solnet.ch> writes:

> Kevin Greiner <kgreiner@xpediantsolutions.com> writes:
>
>> Robert Epprecht <epprecht@solnet.ch> writes:
>
>> Just as a test, try replacing (setq gnus-plugged nil) with (gnus-agent-toggle-plugged nil).
>
> .gnus.el:
> (gnus-agent-toggle-plugged nil)
>
> Error in ~/.gnus: gnus-agent-toggle-plugged
>
> (Another CVS update did not change this...)
>
> After changing back .gnus.el I tried:
> M-x apropos <RET> gnus-agent-toggle-plugged <RET>
>
> gnus-agent-toggle-plugged
>   Command: Toggle whether Gnus is unplugged or not.
>
> So I try:
> .gnus.el:
> (gnus-agent-toggle-plugged) ;; without parameter nil
>
> Error in ~/.gnus: gnus-agent-toggle-plugged
>
>
> Next try:
> .gnus.el:
> (setq debug-on-error t)
> (gnus-agent-toggle-plugged nil)

I think that you need to load gnus-agent.  Try this in your .gnus

(require 'gnus-agent)
(gnus-agent-toggle-plugged nil)

Thanks,
Kevin

Re: Plugged or not?

[Robert Epprecht]

Kevin Greiner <kgreiner@xpediantsolutions.com> writes:

> I think that you need to load gnus-agent.  Try this in your .gnus
>
> (require 'gnus-agent)
> (gnus-agent-toggle-plugged nil)

Yes, this works now, thank you.

What about (setq gnus-plugged nil) ?
Robert

Re: Plugged or not?

[Kevin Greiner]

Robert Epprecht <epprecht@solnet.ch> writes:

> Kevin Greiner <kgreiner@xpediantsolutions.com> writes:
>
>> I think that you need to load gnus-agent.  Try this in your .gnus
>>
>> (require 'gnus-agent)
>> (gnus-agent-toggle-plugged nil)
>
> Yes, this works now, thank you.
>
> What about (setq gnus-plugged nil) ?

I'll have to fix the code to support initializing it to nil.

FYI, the problem that was fixed as that the code
  (gnus-agent-toggle-plugged nil)
  (gnus-agent-toggle-plugged nil)
would run the unplug logic twice.  Now, the second call is ignored.

The problem now is that initializing gnus-plugged to nil results in
the unplug logic never being executed.  So, two steps forward, one
step back.

Kevin

Re: Plugged or not?

[Robert Epprecht]

Kevin Greiner <kgreiner@xpediantsolutions.com> writes:

> Robert Epprecht <epprecht@solnet.ch> writes:

>> What about (setq gnus-plugged nil) ?
>
> I'll have to fix the code to support initializing it to nil.
>
> FYI, the problem that was fixed as that the code
>   (gnus-agent-toggle-plugged nil)
>   (gnus-agent-toggle-plugged nil)
> would run the unplug logic twice.  Now, the second call is ignored.
>
> The problem now is that initializing gnus-plugged to nil results in
> the unplug logic never being executed.  So, two steps forward, one
> step back.

I for myself would not mind changing my method of having the Agent start
unplugged, but I might not be the only one trying it the way I did.
I probably read it somewhere in the manual, or was told to do so on this
list or in usenet, ages ago...

Robert

Re: Plugged or not?

[Kevin Greiner]

Robert Epprecht <epprecht@solnet.ch> writes:

> Kevin Greiner <kgreiner@xpediantsolutions.com> writes:
>
>> Robert Epprecht <epprecht@solnet.ch> writes:
>
>>> What about (setq gnus-plugged nil) ?
>>
>> I'll have to fix the code to support initializing it to nil.
>>
>> FYI, the problem that was fixed as that the code
>>   (gnus-agent-toggle-plugged nil)
>>   (gnus-agent-toggle-plugged nil)
>> would run the unplug logic twice.  Now, the second call is ignored.
>>
>> The problem now is that initializing gnus-plugged to nil results in
>> the unplug logic never being executed.  So, two steps forward, one
>> step back.
>
> I for myself would not mind changing my method of having the Agent start
> unplugged, but I might not be the only one trying it the way I did.
> I probably read it somewhere in the manual, or was told to do so on this
> list or in usenet, ages ago...

This problem should now be fixed in revision 6.151 of gnus-agent.el.

Kevin

Re: Plugged or not?

[Robert Epprecht]

Kevin Greiner <kgreiner@xpediantsolutions.com> writes:

> This problem should now be fixed in revision 6.151 of gnus-agent.el.

Yes, thank you,
Robert.

Re: Plugged or not?

[Kai Großjohann]

Robert Epprecht <epprecht@solnet.ch> writes:

> I start Gnus with 
> emacs -f gnus

I also get the "Plugged" indicator in the modeline when doing "emacs
-f gnus-unplugged".  But it's only the display in the modeline that's
wrong, otherwise Gnus behaves as if unplugged.
-- 
A preposition is not a good thing to end a sentence with.

Re: Plugged or not?

[Robert Epprecht]

kai.grossjohann@uni-duisburg.de (Kai Großjohann) writes:

> Robert Epprecht <epprecht@solnet.ch> writes:

> I also get the "Plugged" indicator in the modeline when doing "emacs
> -f gnus-unplugged".  But it's only the display in the modeline that's
> wrong, otherwise Gnus behaves as if unplugged.

AOL, Robert