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.

Full log

View this message in rfc822 format

From: MON KEY <monkey <at> sandpframing.com>
To: 6439 <at> debbugs.gnu.org
Subject: bug#6439: `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\
This bug report was last modified 13 years and 332 days ago.

Previous Next

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