Subject: bug#15655: closed (Re: bug#12985: eval-last-sexp looks broken when executed twice)

From: [email-masked] (GNU bug Tracking System)
Date: Thu, 19 Dec 2013 21:04:03 +0000

Your bug report

#12985: Eval integer, see extraneous nonsense output

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 [email-masked].

-- 
12985: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=12985
GNU Bug Tracking System
Contact [email-masked] with problems

Subject: Re: bug#12985: eval-last-sexp looks broken when executed twice
From: Juri Linkov <[email-masked]>
To: Kelly Dean <[email-masked]>
Cc: [email-masked]
Date: Thu, 19 Dec 2013 23:03:36 +0200
List-Id: <debbugs-submit.debbugs.gnu.org>

> It seems a better design would be to always include the string, even
> the first time, when displaying in the echo area, and never include
> the string when printing into the buffer, regardless of the invoking
> command name. This is simpler, and it's how eval-expression
> already works.

This is implemented now, including other discussed changes.

Subject: Eval integer, see extraneous nonsense output
From: Barry OReilly <[email-masked]>
To: [email-masked]
Date: Sat, 19 Oct 2013 16:20:14 -0400
List-Id: <debbugs-submit.debbugs.gnu.org>

Run emacs -Q. Type the number 23 in the scratch buffer. eval-last-sexp
and see in the minibuffer: "23". eval-last-sexp again and see in the
minibuffer: "23 (#o27, #x17, ?\C-w)". I didn't expect (#o27, #x17,
?\C-w).

Using recent trunk.