[debbugs-tracker] bug#15655: closed (Eval integer, see extraneous nonsense output)

[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 integer, see extraneous nonsense output
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 integer, see extraneous nonsense output Date: Sat, 19 Oct 2013 16:20:14 -0400

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.

--- 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 ---