From: "Štěpán Němec" <stepnem@gmail.com>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: 'Lars Magne Ingebrigtsen' <larsi@gnus.org>, emacs-devel@gnu.org
Subject: Re: backtrace sets print-level to 3
Date: Fri, 01 Oct 2010 15:12:14 +0200 [thread overview]
Message-ID: <87vd5moy4x.fsf@gmail.com> (raw)
In-Reply-To: <388E58028D404C7E97363291360D11AD@us.oracle.com> (Drew Adams's message of "Thu, 30 Sep 2010 06:12:21 -0700")
"Drew Adams" <drew.adams@oracle.com> writes:
>> I think I'll just fix Fbacktrace to 1) restore the previous value upon
>> exit instead of setting it to Qnil, and 2) use 8 instead of 3.
>
> The print-(level|length) of backtraces should be under user control, i.e., at
> the Lisp level or, better, interactively (e.g. option). It should not be
> hard-coded.
>
> If we are not using the global values of `print-level' and `print-length' or,
> better, similar-acting variables (options?) that are specific to backtraces,
> why
> not? How can a user control this aspect of the bactrace output appearance?
+1
I've been missing something like that, too. The current restriction
seems arbitrary and makes the `debug' backtraces much less useful than
they could be.
Štěpán
prev parent reply other threads:[~2010-10-01 13:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-29 22:52 backtrace sets print-level to 3 Lars Magne Ingebrigtsen
2010-09-29 22:54 ` Lars Magne Ingebrigtsen
2010-09-30 9:19 ` Eli Zaretskii
2010-09-30 9:42 ` Lars Magne Ingebrigtsen
2010-09-30 11:15 ` Eli Zaretskii
2010-09-30 11:20 ` Lars Magne Ingebrigtsen
2010-09-30 12:12 ` Eli Zaretskii
2010-09-30 12:35 ` Lars Magne Ingebrigtsen
2010-09-30 13:12 ` Drew Adams
2010-10-01 13:12 ` Štěpán Němec [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87vd5moy4x.fsf@gmail.com \
--to=stepnem@gmail.com \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).