bug-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#135: marked as done (eval-defun binds print-level during eval)


From: Emacs bug Tracking System
Subject: bug#135: marked as done (eval-defun binds print-level during eval)
Date: Thu, 29 May 2008 16:15:06 -0700

Your message dated Thu, 29 May 2008 19:07:58 -0400
with message-id <address@hidden>
and subject line Re: eval-defun binds print-level during eval  
has caused the Emacs bug report #135,
regarding eval-defun binds print-level during eval
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact address@hidden
immediately.)


-- 
135: http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=135
Emacs Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: Re: generate autoloads versus eval-expression-print-level (patch) Date: Mon, 14 Apr 2008 10:46:29 +1000 User-agent: Gnus/5.110007 (No Gnus v0.7) Emacs/22.1 (gnu/linux)
Stefan Monnier <address@hidden> 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.




--- End Message ---
--- Begin Message --- Subject: Re: eval-defun binds print-level during eval Date: Thu, 29 May 2008 19:07:58 -0400
This has been fixed.


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]