GNU bug report logs - #6439
`bkqt` <- eval-last-sexp return value => bkqt

Previous Next

Package: emacs;

Reported by: MON KEY <monkey <at> sandpframing.com>

Date: Wed, 16 Jun 2010 18:00:03 UTC

Severity: minor

Tags: notabug

Done: Lars Magne Ingebrigtsen <larsi <at> gnus.org>

Bug is archived. No further changes may be made.

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 6439 in the body.
You can then email your comments to 6439 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox

Report forwarded to owner <at> debbugs.gnu.org, bug-gnu-emacs <at> gnu.org:
bug#6439; Package emacs. (Wed, 16 Jun 2010 18:00:03 GMT) Full text and rfc822 format available.
Acknowledgement sent to MON KEY <monkey <at> sandpframing.com>:
New bug report received and forwarded. Copy sent to bug-gnu-emacs <at> gnu.org. (Wed, 16 Jun 2010 18:00:03 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: MON KEY <monkey <at> sandpframing.com>
To: bug-gnu-emacs <at> gnu.org
Subject: `bkqt` <- eval-last-sexp return value => bkqt
Date: Wed, 16 Jun 2010 13:59:27 -0400

With point after the following:

 `bkqt`

`eval-last-sexp' returns => bkqt

e.g.

(progn
  (insert "`bkqt`")
  (apply 'eval-last-sexp '(nil)))

Likewise, there is this weird behavior:

(progn
  (insert
   "\n\(progn\n"
   "  \(insert \"`bkqt`\"\)\n"
   "  \(apply 'eval-last-sexp '\(nil\)\)\)\n`\n")
  (apply 'eval-last-sexp '(nil)))

Why does evaluating the grave char evaluate the sexp preceding it but also does
something like this:

 (with-temp-buffer (insert "`````") (apply 'eval-last-sexp '(nil)))

Which signals an EOF?

Whereas this something like this doesn't:

 (with-temp-buffer (insert "`,(quote nil)`````") (apply 'eval-last-sexp '(nil)))


--
/s_p\
Added tag(s) notabug. Request was from Lars Magne Ingebrigtsen <larsi <at> gnus.org> to control <at> debbugs.gnu.org. (Sun, 03 Jul 2011 02:02:01 GMT) Full text and rfc822 format available.
bug closed, send any further explanations to 6439 <at> debbugs.gnu.org and MON KEY <monkey <at> sandpframing.com> Request was from Lars Magne Ingebrigtsen <larsi <at> gnus.org> to control <at> debbugs.gnu.org. (Sun, 03 Jul 2011 02:02:02 GMT) Full text and rfc822 format available.
Information forwarded to owner <at> debbugs.gnu.org, bug-gnu-emacs <at> gnu.org:
bug#6439; Package emacs. (Sun, 03 Jul 2011 02:03:01 GMT) Full text and rfc822 format available.

Message #12 received at 6439 <at> debbugs.gnu.org (full text, mbox):

From: Lars Magne Ingebrigtsen <larsi <at> gnus.org>
To: MON KEY <monkey <at> sandpframing.com>
Cc: 6439 <at> debbugs.gnu.org
Subject: Re: `bkqt` <- eval-last-sexp return value => bkqt
Date: Sun, 03 Jul 2011 04:01:35 +0200

MON KEY <monkey <at> sandpframing.com> writes:

> With point after the following:
>
>  `bkqt`
>
> `eval-last-sexp' returns => bkqt
>
> e.g.
>
> (progn
>   (insert "`bkqt`")
>   (apply 'eval-last-sexp '(nil)))

I don't think recursive calls to `eval-last-sexp' are particularly
useful.

The command does some minor Do What I Mean to make it more useful, and
that means that you can make it return odd values if you're doing
something Nobody Could Possibly Mean.

So I don't think this is a bug.

-- 
(domestic pets only, the antidote for overdose, milk.)
  bloggy blog http://lars.ingebrigtsen.no/
bug archived. Request was from Debbugs Internal Request <help-debbugs <at> gnu.org> to internal_control <at> debbugs.gnu.org. (Sun, 31 Jul 2011 11:24:05 GMT) Full text and rfc822 format available.
This bug report was last modified 13 years and 331 days ago.

Previous Next

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