From: Kevin Ryde <user42@zip.com.au>
To: emacs-devel@gnu.org
Subject: Re: generate autoloads versus eval-expression-print-level (patch)
Date: Sun, 13 Apr 2008 09:07:01 +1000 [thread overview]
Message-ID: <87ej9au0yy.fsf@blah.blah> (raw)
In-Reply-To: <jwviqypduds.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Thu, 10 Apr 2008 21:59:20 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>
> installed,
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.
next prev parent reply other threads:[~2008-04-12 23:07 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-10 23:37 generate autoloads versus eval-expression-print-level (patch) Kevin Ryde
2008-04-11 1:59 ` Stefan Monnier
2008-04-12 23:07 ` Kevin Ryde [this message]
2008-04-13 19:24 ` Stefan Monnier
2008-04-14 0:46 ` Kevin Ryde
2008-04-14 1:53 ` Stefan Monnier
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
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ej9au0yy.fsf@blah.blah \
--to=user42@zip.com.au \
--cc=emacs-devel@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.