bug#31589: lispintro - Backtrace read out update

bug#31589: lispintro - Backtrace read out update

[Van L]

Hello.

The documentation and behavior are different.

diff --git a/doc/lispintro/emacs-lisp-intro.texi b/doc/lispintro/emacs-lisp-intro.texi
index b79432e..a3a2155 100644
--- a/doc/lispintro/emacs-lisp-intro.texi
+++ b/doc/lispintro/emacs-lisp-intro.texi
@@ -1339,10 +1339,12 @@ Making Errors
 ---------- Buffer: *Backtrace* ----------
 Debugger entered--Lisp error: (void-function this)
   (this is an unquoted list)
-  eval((this is an unquoted list))
-  eval-last-sexp-1(nil)
+  eval((this is an unquoted list) nil)
+  elisp--eval-last-sexp(nil)
   eval-last-sexp(nil)
-  call-interactively(eval-last-sexp)
+  funcall-interactively(eval-last-sexp nil)
+  call-interactively(eval-last-sexp nil nil)
+  command-execute(eval-last-sexp)
 ---------- Buffer: *Backtrace* ----------
 @end group
 @end smallexample

bug#31589: Acknowledgement (lispintro - Backtrace read out update)

[Van L]

In the example given, I think if the first atom of the list is `this-here’, as in:

  (this-here is an unquoted list)

explained in the context of `(void-function this-here)’ stands out distinctly from other uses of `this’ in the surrounding text.

: 8cda6f8f (Glenn Morris             2007-09-06  1318) (this is an unquoted list)

bug#31589: lispintro - Backtrace read out update

[Eli Zaretskii]

> From: Van L <van@scratch.space>
> Date: Fri, 25 May 2018 13:32:02 +1000
> 
> The documentation and behavior are different.

Thanks, fixed.

bug#31589: Acknowledgement (lispintro - Backtrace read out update)

[Eli Zaretskii]

> From: Van L <van@scratch.space>
> Date: Fri, 25 May 2018 14:21:24 +1000
> 
> In the example given, I think if the first atom of the list is `this-here’, as in:
> 
>   (this-here is an unquoted list)
> 
> explained in the context of `(void-function this-here)’ stands out distinctly from other uses of `this’ in the surrounding text.
> 
> : 8cda6f8f (Glenn Morris             2007-09-06  1318) (this is an unquoted list)

Sorry, I don't understand what you are trying to say.  The string
"this-here" doesn't appear anywhere in this manual.  And 'this' is a
commonly-used symbol in these days of OOP.

bug#31589: Acknowledgement (lispintro - Backtrace read out update)

[Van L]

> On 25 May 2018, at 18:39, Eli Zaretskii <eliz@gnu.org> wrote:
> 
> And 'this' is a
> commonly-used symbol in these days of OOP.

Yes. That’s one of the two sources of confusion, the other is the plain old English `this’ used in the unquoted list and surrounding discussion.

Having `this-here’ emphasizes the first atom of the list being discussed as distinct from `this' in an oop sense or ordinary `this' in a sentence. It bends over backwards more for a non-programmer.

Anyway, your call.

bug#31589: Acknowledgement (lispintro - Backtrace read out update)

[Phil Sainty]

On 2018-05-25 20:59, Van L wrote:
> Having `this-here’ emphasizes the first atom of the list being
> discussed as distinct from `this' in an oop sense or ordinary `this'
> in a sentence. It bends over backwards more for a non-programmer.

A bit awkward, though?

I think "(here is an unquoted list)" would be nicer than that, if
such a change was to be made.

bug#31589: Acknowledgement (lispintro - Backtrace read out update)

[Van L]

> Phil Sainty writes:
> 
> Van L writes:
>> Having `this-here’ emphasizes the first atom of the list being
>> discussed as distinct from `this' in an oop sense or ordinary `this'
>> in a sentence. It bends over backwards more for a non-programmer.
> 
> A bit awkward, though?
> 
> I think "(here is an unquoted list)" would be nicer than that, if
> such a change was to be made.

Not awkward in the following context, which has the hyphenated `void-function’.

(void-function this-here)

Looks nicer to me.
It hints of being lispy.

hmmm, yeah, this works, too, and won’t add more.

(void-function here)