[debbugs-tracker] bug#12985: closed (eval-last-sexp looks broken when executed twice)

[GNU bug Tracking System]

Your message dated Thu, 19 Dec 2013 23:03:36 +0200
with message-id <address@hidden>
and subject line Re: bug#12985: eval-last-sexp looks broken when executed twice
has caused the debbugs.gnu.org bug report #12985,
regarding eval-last-sexp looks broken when executed twice
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
12985: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=12985
GNU Bug Tracking System
Contact address@hidden with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> eval-last-sexp looks broken when executed twice
>
>
>
>
> Date: 
>
> Sat, 24 Nov 2012 17:52:06 -0800 (PST)
>
>
>
>
> 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)
>
>
>
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#12985: eval-last-sexp looks broken when executed twice
>
>
>
>
> Date: 
>
> Thu, 19 Dec 2013 23:03:36 +0200
>
>
>
>
> User-agent: 
>
> Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (x86_64-pc-linux-gnu)
>
>
>
>
> > 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.
>
>
> --- End Message ---