[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#6439: `bkqt` <- eval-last-sexp return value => bkqt
From: |
MON KEY |
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\
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- bug#6439: `bkqt` <- eval-last-sexp return value => bkqt,
MON KEY <=