unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: Lars Magne Ingebrigtsen <larsi@gnus.org>
Cc: 135@debbugs.gnu.org, 'Kevin Ryde' <user42@zip.com.au>
Subject: bug#135: generate autoloads versus eval-expression-print-level (patch)
Date: Thu, 07 Jul 2011 13:20:55 -0400	[thread overview]
Message-ID: <c17h7uknwo.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <m31uy2xdpv.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Thu, 07 Jul 2011 18:22:36 +0200")

Lars Magne Ingebrigtsen wrote:

>> 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:
>
> `C-M-x' uses `eval-expression-print-level' and friends (which default to
> 4), so I think this isn't a bug.

I don't understand why answering a message which begins "Haven't read
the bug" means the bug can be closed.

As the bug says, some of the thread is missing, but it is easily found.

http://lists.gnu.org/archive/html/emacs-devel/2008-04/msg01001.html

    It occurred to me to wonder what business eval-defun has binding
    those print variables during the eval, as opposed to just the
    printing of the result, but doing anything about that looks a bit
    difficult.





  reply	other threads:[~2011-07-07 17:20 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <18495.14158.982200.566312@fencepost.gnu.org>
     [not found] ` <87hce58dqy.fsf@blah.blah>
2008-05-29 23:15   ` bug#135: marked as done (eval-defun binds print-level during eval) Emacs bug Tracking System
     [not found]   ` <handler.135.D135.121210258811769.notifdone@emacsbugs.donarmstrong.com>
2008-06-01 23:31     ` bug#135: closed by Glenn Morris <rgm@gnu.org> (Re: eval-defun binds print-level during eval ) Kevin Ryde
2008-06-02  2:03       ` Glenn Morris
2008-06-02 23:04         ` Kevin Ryde
2011-07-06 17:29   ` bug#135: generate autoloads versus eval-expression-print-level (patch) Lars Magne Ingebrigtsen
2011-07-06 19:31     ` Drew Adams
2011-07-07 16:22       ` Lars Magne Ingebrigtsen
2011-07-07 17:20         ` Glenn Morris [this message]
2011-07-07 17:23           ` Lars Magne Ingebrigtsen
2011-07-07 19:58         ` Stefan Monnier
2011-07-10 12:48           ` Lars Magne Ingebrigtsen
2011-07-10 13:14             ` Andreas Schwab
2011-07-10 13:18               ` Lars Magne Ingebrigtsen
2011-07-12  3:35                 ` Stefan Monnier
2011-07-15  0:18             ` Kevin Ryde
2011-07-15 17:03               ` Lars Magne Ingebrigtsen
2011-07-16 21:56                 ` Kevin Ryde
2022-04-24 15:10                   ` bug#135: eval-defun binds print-level during eval Lars Ingebrigtsen
2022-04-27 18:04                     ` Lars Ingebrigtsen
     [not found] <87hce9i8n5.fsf@blah.blah>
     [not found] ` <jwviqypduds.fsf-monnier+emacs@gnu.org>
     [not found]   ` <87ej9au0yy.fsf@blah.blah>

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c17h7uknwo.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=135@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=user42@zip.com.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).