[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#135: generate autoloads versus eval-expression-print-level (patch)
|
From: |
Lars Magne Ingebrigtsen |
|
Subject: |
bug#135: generate autoloads versus eval-expression-print-level (patch) |
|
Date: |
Wed, 06 Jul 2011 19:29:02 +0200 |
|
User-agent: |
Gnus/5.110018 (No Gnus v0.18) Emacs/24.0.50 (gnu/linux) |
Kevin Ryde <user42@zip.com.au> writes:
>> Actually, looking at the code of eval-expression, it seems to only bind
>> those variables around the print part, not the eval part.
>
> Yep, eval-expression and eval-last-sexp both seem ok, but eval-defun
> not. Eg. C-M-x on (progn print-level) ==> 4.
What's the status on this bug? Is this still a problem?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog http://lars.ingebrigtsen.no/
- bug#135: generate autoloads versus eval-expression-print-level (patch),
Lars Magne Ingebrigtsen <=
- bug#135: generate autoloads versus eval-expression-print-level (patch), Drew Adams, 2011/07/06
- bug#135: generate autoloads versus eval-expression-print-level (patch), Lars Magne Ingebrigtsen, 2011/07/07
- bug#135: generate autoloads versus eval-expression-print-level (patch), Stefan Monnier, 2011/07/07
- bug#135: generate autoloads versus eval-expression-print-level (patch), Lars Magne Ingebrigtsen, 2011/07/10
- bug#135: generate autoloads versus eval-expression-print-level (patch), Andreas Schwab, 2011/07/10
- bug#135: generate autoloads versus eval-expression-print-level (patch), Lars Magne Ingebrigtsen, 2011/07/10
- bug#135: generate autoloads versus eval-expression-print-level (patch), Stefan Monnier, 2011/07/11
- bug#135: generate autoloads versus eval-expression-print-level (patch), Kevin Ryde, 2011/07/14