Subject: bug#12985: 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:02 +0000

Your bug report

#12985: eval-last-sexp looks broken when executed twice

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-last-sexp looks broken when executed twice
From: Kelly Dean <[email-masked]>
To: [email-masked]
Date: Sat, 24 Nov 2012 17:52:06 -0800 (PST)
List-Id: <debbugs-submit.debbugs.gnu.org>

Using 24.2, type:
5
Then do C-x C-e, and as expected it echoes:
5
But then do C-x C-e again, and unexpectedly it echoes:
5 (#o5, #x5, ?\C-e)
The same thing happens if you type 5 then do C-u C-x C-e C-u C-x C-e; first as expected you get:
55
Then unexpectedly you get:
5555 (#o67, #x37, ?7)