From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: emacs-devel@gnu.org
Subject: Re: C-j in Lisp interaction mode.
Date: Fri, 8 Aug 2003 21:41:07 -0500 (CDT) [thread overview]
Message-ID: <200308090241.h792f7M19010@raven.dms.auburn.edu> (raw)
In-Reply-To: <E19lEzZ-0005le-Fx@fencepost.gnu.org> (message from Richard Stallman on Fri, 08 Aug 2003 17:41:45 -0400)
Richard Stallman wrote:
Also,
`eval-expression-print-length' and `eval-expression-print-level' do
not seem to be documented in the Elisp manual, which makes their use
very confusing to beginning Elisp users.
They are documented in the Emacs manual, where the commands are
documented. I'm not against putting them in the Lisp manual, but is
there a place where they would fit? The evaluation commands are not
documented in that manual.
The diff below would document `eval-expression-print-length' and
`eval-expression-print-level' straight after the definitions of
`print-length' and `print-level'. It would prevent readers of the
Elisp manual who try out the latter two variables in the *scratch*
buffer from being completely confused by Emacs' apparent lack of
response in as far as C-j, C-x C-e or similar, is concerned. There is
a reference to the section of the Emacs manual which you mentioned.
If the diff is OK, I could commit it to the CVS, if desired.
===File ~/streamsdiff=======================================
cd ~/
diff -c /home/teirllm/streams.old.texi /home/teirllm/streams.texi
*** /home/teirllm/streams.old.texi Tue Jul 22 12:19:57 2003
--- /home/teirllm/streams.texi Fri Aug 8 20:32:27 2003
***************
*** 771,776 ****
--- 771,784 ----
@code{nil} (which is the default) means no limit.
@end defvar
+ @defopt eval-expression-print-length
+ @defoptx eval-expression-print-level
+ These are the values for @code{print-length} and @code{print-level}
+ used by @code{eval-expression}, and thus, indirectly, by many
+ interactive evaluation commands (@pxref{Lisp Eval,, Evaluating
+ Emacs-Lisp Expressions, emacs, The GNU Emacs Manual}).
+ @end defopt
+
These variables are used for detecting and reporting circular
and shared structure---but they are only defined in Emacs 21.
Diff finished at Fri Aug 8 21:18:10
============================================================
prev parent reply other threads:[~2003-08-09 2:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-07 17:08 C-j in Lisp interaction mode Luc Teirlinck
2003-08-08 6:11 ` Richard Stallman
2003-08-08 21:41 ` Richard Stallman
2003-08-09 2:41 ` Luc Teirlinck [this message]
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=200308090241.h792f7M19010@raven.dms.auburn.edu \
--to=teirllm@dms.auburn.edu \
--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 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).