From: Van L <van@scratch.space>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 31654@debbugs.gnu.org
Subject: bug#31654: emacs-lisp-intro.texi - backtrace
Date: Thu, 31 May 2018 13:00:02 +1000 [thread overview]
Message-ID: <D937AD3F-A82B-4709-A9B2-7CB1FD53B632@scratch.space> (raw)
In-Reply-To: <83y3g1gk41.fsf@gnu.org>
> On 31 May 2018, at 02:54, Eli Zaretskii <eliz@gnu.org> wrote:
>
> But it's what Emacs shows nowadays. I don't see any good reasons to
> describe in the manual something that is different from the reality
>
> If you or someone else have ideas how to make this "nicer" without
> lying to the reader, I'm all ears.
The ``ignore'' passage for pre-version 22 suggests a one line backtrace for the event of function or variable being ``void’’. Neat.
How about something like a universal argument for level of detail of verbosity? for backtrace.
The default is one line where possible for C-x C-e.
The easy to medium setting has lines having a common beautiful prefix where possible.
The extremely difficult setting has all the ugly offal outpourings for the kitchen sink.
next prev parent reply other threads:[~2018-05-31 3:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-30 9:23 bug#31654: emacs-lisp-intro.texi - backtrace Van L
[not found] ` <handler.31654.B.152767225430552.ack@debbugs.gnu.org>
2018-05-30 9:34 ` bug#31654: Acknowledgement (emacs-lisp-intro.texi - backtrace) Van L
2018-06-01 13:42 ` Van L
2018-06-01 14:12 ` Eli Zaretskii
2018-05-30 16:54 ` bug#31654: emacs-lisp-intro.texi - backtrace Eli Zaretskii
2018-05-31 3:00 ` Van L [this message]
2018-05-31 14:44 ` Eli Zaretskii
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=D937AD3F-A82B-4709-A9B2-7CB1FD53B632@scratch.space \
--to=van@scratch.space \
--cc=31654@debbugs.gnu.org \
--cc=eliz@gnu.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).