What does this error message mean ?

What does this error message mean ?

[Pieter Wenk]

Hello to all:

It happens, that I am getting:

variable binding depth exceeds max-specpdl-size.

Result it becomes impossible to hit F or N in order
to send follow-up messages.

Why does this happen and how to correct ?

I this a "special feature" in order keeping people
happy ?

Many thanks for your help
--
        
                           / /  (_)____ __ ____  __
      Pieter Wenk         / /__/ / _ \/ // /\ \/ /  Vevey/Switzerland
                         /____/_/_//_/\_,_/ /_/\_\

Re: What does this error message mean ?

[Pieter Wenk]

On mer, 29 déc 1999, Didier Verna wrote:

>Pieter Wenk <pwenk@urbanet.ch> wrote:
>
>> It happens, that I am getting:
>> 
>> variable binding depth exceeds max-specpdl-size.
>
>        This variable indicates the max number of lisp variables that can be
>bound at the same time. Try to increase it.

Thanks a lot. 

I started in fact to use Xemacs/gnus recently. How do you
increase this number ???

Were ?

Secondly, it happens often that I am getting also
the message:

nnspool: References header too long (Article not posted).

I have of course no influence on such headers and would
like to able answering.

What do I have to do in order to correct this. ?

I wish to all of this group a happy and prosper
New Year.

Regards
--
        
                           / /  (_)____ __ ____  __
      Pieter Wenk         / /__/ / _ \/ // /\ \/ /  Vevey/Switzerland
                         /____/_/_//_/\_,_/ /_/\_\

Re: What does this error message mean ?

[Kai Großjohann]

Pieter Wenk <pwenk@urbanet.ch> writes:

> variable binding depth exceeds max-specpdl-size.

This is a measure against infinite loops, I think.  It seems that
demanding Lisp packages sometimes need more than the normal limit.
You could try increasing the number: (setq max-specpdl-size 9999)

kai
-- 
A preposition is not a good thing to end a sentence with.

Re: What does this error message mean ?

[Pieter Wenk]

On mer, 29 déc 1999, Kai Großjohann wrote:

>Pieter Wenk <pwenk@urbanet.ch> writes:
>
>> variable binding depth exceeds max-specpdl-size.
>
>This is a measure against infinite loops, I think.  It seems that
>demanding Lisp packages sometimes need more than the normal limit.
>You could try increasing the number: (setq max-specpdl-size 9999)

Thanks a lot. Will add this to my ~/.gnus

Now I am also getting another message:

nnspool: Reference header too long (article not posted).

Stefanie Teufel, advised me, that this might be a bug.

Any idea how to correct this ?

Many thanks for your help


--
        
                           / /  (_)____ __ ____  __
      Pieter Wenk         / /__/ / _ \/ // /\ \/ /  Vevey/Switzerland
                         /____/_/_//_/\_,_/ /_/\_\

Re: What does this error message mean ?

[Stefanie Teufel]

On Thu, Dec 30, 1999 at 07:30:11 +0100, Pieter Wenk wrote:

> nnspool: Reference header too long (article not posted). Stefanie
> Teufel, advised me, that this might be a bug. Any idea how to correct
> this ?

Hmmm, I'm not sure, but I mean I read something about broken
references, a possible bug etc. only a few weeks ago on the list. Am I
wrong?

happy new year

Stefanie
-- 
alt.sex.alt.syntax.tactical       No description.

nnspool: Reference header too long (article not posted)

[Pieter Wenk]

Hello to all,

What kind of new great feature is 

Reference header too long (article not posted)

How can I correct this error message as it makes it
absolutly impossible posting follow-up messages.

Like this, gnus 5.8.2 can not be used.....

Many thanks for your help....

Regards
--
        
                           / /  (_)____ __ ____  __
      Pieter Wenk         / /__/ / _ \/ // /\ \/ /  Vevey/Switzerland
                         /____/_/_//_/\_,_/ /_/\_\

Re: nnspool: Reference header too long (article not posted)

[Kai Großjohann]

Pieter Wenk <pwenk@urbanet.ch> writes:

> Reference header too long (article not posted)

I think this is a message that comes from your inews program and not
from Gnus.  I looked in the Gnus *.el files and couldn't find
`reference header' nor `too long' (case insensitively).

Can you use nntp rather than nnspool as a select method?

kai
-- 
A preposition is not a good thing to end a sentence with.

Re: nnspool: Reference header too long (article not posted)

[Pieter Wenk]

On jeu, 30 déc 1999, Kai Großjohann wrote:

Hello Kai,

>> Reference header too long (article not posted)
>
>I think this is a message that comes from your inews program and not
>from Gnus.  I looked in the Gnus *.el files and couldn't find
>`reference header' nor `too long' (case insensitively).
>
>Can you use nntp rather than nnspool as a select method?

I have:

(setq gnus-select-method '(nntp "localhost"))

in ~/.gnus

And with "this" setting am getting the above error !

Do you have any idea why ?

Like this it's really akward using gnus....

Many thanks for your help

Regards
--
        
                           / /  (_)____ __ ____  __
      Pieter Wenk         / /__/ / _ \/ // /\ \/ /  Vevey/Switzerland
                         /____/_/_//_/\_,_/ /_/\_\

Re: nnspool: Reference header too long (article not posted)

[Kai Großjohann]

Pieter Wenk <pwenk@urbanet.ch> writes:

> (setq gnus-select-method '(nntp "localhost"))
> 
> And with "this" setting am getting the above error !

Maybe it would be best to tell message to fold long references lines.
See the variable message-cater-to-broken-inn.

kai
-- 
A preposition is not a good thing to end a sentence with.

Re: nnspool: Reference header too long (article not posted)

[Pieter Wenk]

On jeu, 30 déc 1999, Kai Großjohann wrote:

Hello to all

This nifty "great" feature:  Reference header too long (article not posted),
is really able motivating to some frank, harsh well known words.

Every third message (follow ups), I get the above
absolute unpleasant message. Really, that thing can
really go on your ner

How is this to correct....
--
        
                           / /  (_)____ __ ____  __
      Pieter Wenk         / /__/ / _ \/ // /\ \/ /  Vevey/Switzerland
                         /____/_/_//_/\_,_/ /_/\_\

Re: nnspool: Reference header too long (article not posted)

[David S. Goldberg]

As others have already pointed out, that message appears to be coming
from your news software, not gnus itself.  It seems the easiest thing
would be to pare down the references header when you edit your
message.  You could probably write a hook to do so, or maybe
modify/advise message-shorten-references with a smaller limit.  Or get
better news software.
-- 
Dave Goldberg
Post: The Mitre Corporation\MS B325\202 Burlington Rd.\Bedford, MA 01730
Phone: 781-271-3887
Email: dsg@mitre.org

Re: nnspool: Reference header too long (article not posted)

[Russ Allbery]

David S Goldberg <dsg@mitre.org> writes:

> As others have already pointed out, that message appears to be coming
> from your news software, not gnus itself.  It seems the easiest thing
> would be to pare down the references header when you edit your message.
> You could probably write a hook to do so, or maybe modify/advise
> message-shorten-references with a smaller limit.  Or get better news
> software.

If the problem is that the References header is over 1024 characters on a
single line, you definitely don't want "better" news software where better
is defined as news software that will post that, since your article would
end up getting dropped at other sites.

A better solution would be to set message-cater-to-broken-inn to nil so
that Gnus will fold the References header.  Anyone running that old of a
version of INN should upgrade anyway.

-- 
Russ Allbery (rra@stanford.edu)         <URL:http://www.eyrie.org/~eagle/>

Re: nnspool: Reference header too long (article not posted)

[Pieter Wenk]

On jeu, 30 déc 1999, David S. Goldberg wrote:

>As others have already pointed out, that message appears to be coming
>from your news software, not gnus itself.  It seems the easiest thing
>would be to pare down the references header when you edit your
>message.  You could probably write a hook to do so, or maybe
>modify/advise message-shorten-references with a smaller limit.  Or get
>better news software.

I am using leafnode..."latest" version. What should be wrong
with that ?

I have no idea (yet) how to write such a hook....

Happy New Year


--
        
                           / /  (_)____ __ ____  __
      Pieter Wenk         / /__/ / _ \/ // /\ \/ /  Vevey/Switzerland
                         /____/_/_//_/\_,_/ /_/\_\

Re: nnspool: Reference header too long (article not posted)

[Alan Shutko]

Pieter Wenk <pwenk@urbanet.ch> writes:

> This nifty "great" feature:  Reference header too long (article not posted),
> is really able motivating to some frank, harsh well known words.

Well, it seems the consensus is it's not Gnus's fault, it's your
newsserver's fault.  You could always try complaining there.  It
probably wouldn't help.  8^)

It seems Gnus already tries to keep Reference headers below some
limits.  Those aren't currently configurable, but you could change
message-shorten-references in message.el to have a lower maxcount.
Someone with more time might change that to be configurable... 

-- 
Alan Shutko <ats@acm.org> - In a variety of flavors!
All work and no pay makes a housewife.

Re: nnspool: Reference header too long (article not posted)

[Pieter Wenk]

On jeu, 30 déc 1999, Alan Shutko wrote:

>Pieter Wenk <pwenk@urbanet.ch> writes:
>
>> This nifty "great" feature:  Reference header too long (article not posted),
>> is really able motivating to some frank, harsh well known words.
>
>Well, it seems the consensus is it's not Gnus's fault, it's your
>newsserver's fault.  You could always try complaining there.  It
>probably wouldn't help.  8^)
>
>It seems Gnus already tries to keep Reference headers below some
>limits.  Those aren't currently configurable, but you could change
>message-shorten-references in message.el to have a lower maxcount.
>Someone with more time might change that to be configurable... 

I am using leafnode, latest version which is 1.9.7...

Strange..with my older gnus version, I had "NOT" these 
problems...perhaps somebody is able to tell me why, 
this upgraded 5.8.2 Version is behaving like this ?

Regards
--
        
                           / /  (_)____ __ ____  __
      Pieter Wenk         / /__/ / _ \/ // /\ \/ /  Vevey/Switzerland
                         /____/_/_//_/\_,_/ /_/\_\