GNU bug report logs - #12985
eval-last-sexp looks broken when executed twice

Previous Next

Package: emacs;

Reported by: Kelly Dean <kellydeanch <at> yahoo.com>

Date: Sun, 25 Nov 2012 01:54:02 UTC

Severity: minor

Tags: notabug

Merged with 15655

Done: Juri Linkov <juri <at> jurta.org>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Juri Linkov <juri <at> jurta.org>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#15655: closed (Eval integer, see extraneous nonsense output)
Date: Thu, 19 Dec 2013 21:04:02 +0000
[Message part 1 (text/plain, inline)]
Your message dated Thu, 19 Dec 2013 23:03:36 +0200
with message-id <87sitp7dxb.fsf <at> mail.jurta.org>
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
help-debbugs <at> gnu.org.)


-- 
12985: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=12985
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
From: Barry OReilly <gundaetiapo <at> gmail.com>
To: bug-gnu-emacs <at> gnu.org
Subject: Eval integer, see extraneous nonsense output
Date: Sat, 19 Oct 2013 16:20:14 -0400
[Message part 3 (text/plain, inline)]
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.
[Message part 4 (text/html, inline)]
[Message part 5 (message/rfc822, inline)]
From: Juri Linkov <juri <at> jurta.org>
To: Kelly Dean <kellydeanch <at> yahoo.com>
Cc: 12985-done <at> debbugs.gnu.org
Subject: Re: bug#12985: eval-last-sexp looks broken when executed twice
Date: Thu, 19 Dec 2013 23:03:36 +0200
> 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.


This bug report was last modified 11 years and 153 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.