From: Van L <van@scratch.space>
To: 31654@debbugs.gnu.org
Subject: bug#31654: emacs-lisp-intro.texi - backtrace
Date: Wed, 30 May 2018 19:23:51 +1000 [thread overview]
Message-ID: <8794A4AF-6030-4A0E-9F50-FFDFA8AB981D@scratch.space> (raw)
Hello.
What I’ll do is collect backtrace as documented and shown in GNU Emacs 26.1, here.
I like how the original extended the common prefix ``eval’’ in the naming.
The newer backtrace result looks ``complicated''.
#+BEGIN_EXAMPLE
8cda6f8f (Glenn Morris 2007-09-06 1818) ---------- Buffer: *Backtrace* ----------
8cda6f8f (Glenn Morris 2007-09-06 1819) Debugger entered--Lisp error: (void-function fill-column)
8cda6f8f (Glenn Morris 2007-09-06 1820) (fill-column)
8cda6f8f (Glenn Morris 2007-09-06 1821) eval((fill-column))
8cda6f8f (Glenn Morris 2007-09-06 1822) eval-last-sexp-1(nil)
8cda6f8f (Glenn Morris 2007-09-06 1823) eval-last-sexp(nil)
8cda6f8f (Glenn Morris 2007-09-06 1824) call-interactively(eval-last-sexp)
8cda6f8f (Glenn Morris 2007-09-06 1825) ---------- Buffer: *Backtrace* ----------
Debugger entered--Lisp error: (void-function fill-column)
(fill-column)
eval((fill-column) nil)
elisp--eval-last-sexp(nil)
eval-last-sexp(nil)
funcall-interactively(eval-last-sexp nil)
call-interactively(eval-last-sexp nil nil)
command-execute(eval-last-sexp)
#+END_EXAMPLE
next reply other threads:[~2018-05-30 9:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-30 9:23 Van L [this message]
[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
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=8794A4AF-6030-4A0E-9F50-FFDFA8AB981D@scratch.space \
--to=van@scratch.space \
--cc=31654@debbugs.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).