[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#135: generate autoloads versus eval-expression-print-level (patch)
From: |
Drew Adams |
Subject: |
bug#135: generate autoloads versus eval-expression-print-level (patch) |
Date: |
Wed, 6 Jul 2011 12:31:13 -0700 |
> > 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?
Haven't read the bug thread, but putting (progn print-level) in *scratch* and
doing C-M-x on it shows 4 in the echo area. IOW, that description still
applies, in the latest Windows build:
In GNU Emacs 24.0.50.1 (i386-mingw-nt5.1.2600)
of 2011-06-27 on 3249CTO
Windowing system distributor `Microsoft Corp.', version 5.1.2600
configured using `configure --with-gcc (4.5) --no-opt --cflags
-Ic:/build/include'
- bug#135: generate autoloads versus eval-expression-print-level (patch), Lars Magne Ingebrigtsen, 2011/07/06
- bug#135: generate autoloads versus eval-expression-print-level (patch),
Drew Adams <=
- 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
- bug#135: generate autoloads versus eval-expression-print-level (patch), Lars Magne Ingebrigtsen, 2011/07/15