Re: backtrace sets print-level to 3

[Eli Zaretskii]

> X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,T_RP_MATCHES_RCVD
>       autolearn=unavailable version=3.3.1
> From: Lars Magne Ingebrigtsen <address@hidden>
> Date: Thu, 30 Sep 2010 11:42:44 +0200
> 
> Eli Zaretskii <address@hidden> writes:
> 
> > Can you show an example of this limitation in action?  I don't recall
> > having any problems with Lisp backtraces, they are certainly longer
> > than 3 levels.  Maybe I'm missing something.
> 
> The following backtrace was posted on the Gnus mailing list, and all
> those dots seem to indicate....  something...  I assumed print-level,
> since print-length was nil:
> 
>   nnimap-insert-partial-structure((("text" "plain" ("charset" "iso-8859-1") 
> NIL NIL "quoted-printable" 57 2 NIL "1" NIL NIL) ("message" "rfc822" NIL NIL 
> NIL "7bit" 16383 ("Tue, 28 Sep 2010 07:40:57 -0700 (PDT)" "LinkedIn Network 
> Updates, 9/28/2010" ... ... ... ... NIL NIL NIL "<address@hidden>") (... ... 
> "alternative" ... NIL NIL NIL) "2" NIL ("inline" NIL) NIL NIL) "mixed" 
> ("boundary" "=-=-=") NIL NIL NIL) (("1" "Her er problemartikkelen jeg nevnte 
> p=E5 gnus-gruppa:\n\n")))

What about eval-expression-print-length?  Could it be that it's the
one that causes the ellipsis?

Anyway, I just did a little experiment in today's bzr:

  emacs -Q
  Type (frame-parameter 'foo)
  Go to the right paren and type C-j

and got this backtrace:

Debugger entered--Lisp error: (wrong-number-of-arguments frame-parameter 1)
  (frame-parameter (quote foo))
  eval((frame-parameter (quote foo)))
  eval-last-sexp-1(t)
  eval-last-sexp(t)
  eval-print-last-sexp()
  call-interactively(eval-print-last-sexp nil nil)

This is more than 3 levels, and actually is a full backtrace, right
upto call-interactively.  So it looks like there's no stack depth
limitation at work here.