GNU bug report logs - #31654
emacs-lisp-intro.texi - backtrace

Previous Next

Package: emacs;

Reported by: Van L <van <at> scratch.space>

Date: Wed, 30 May 2018 09:25:01 UTC

Severity: minor

Done: Eli Zaretskii <eliz <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Van L <van <at> scratch.space>
Subject: bug#31654: closed (Re: bug#31654: Acknowledgement (emacs-lisp-intro.texi
 - backtrace))
Date: Fri, 01 Jun 2018 14:14:02 +0000
[Message part 1 (text/plain, inline)]
Your bug report

#31654: emacs-lisp-intro.texi - backtrace

which was filed against the emacs package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to 31654 <at> debbugs.gnu.org.

-- 
31654: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=31654
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
From: Eli Zaretskii <eliz <at> gnu.org>
To: Van L <van <at> scratch.space>
Cc: 31654-done <at> debbugs.gnu.org
Subject: Re: bug#31654: Acknowledgement (emacs-lisp-intro.texi - backtrace)
Date: Fri, 01 Jun 2018 17:12:46 +0300
> From: Van L <van <at> scratch.space>
> Date: Fri, 1 Jun 2018 23:42:09 +1000
> 
>   Debugger entered--Lisp error: (wrong-type-argument number-or-marker-p hello)
>     +(2 hello)
>     eval((+ 2 'hello) 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)

Thanks, fixed.

[Message part 3 (message/rfc822, inline)]
From: Van L <van <at> scratch.space>
To: bug-gnu-emacs <at> gnu.org
Subject: emacs-lisp-intro.texi - backtrace
Date: Wed, 30 May 2018 19:23:51 +1000
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




This bug report was last modified 7 years and 47 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.