unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Chong Yidong <cyd@stupidchicken.com>
To: rms@gnu.org
Cc: lennart.borgman@gmail.com, monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: print-circle and describe-variable
Date: Wed, 11 Apr 2007 01:16:09 -0400	[thread overview]
Message-ID: <878xczjxt2.fsf@stupidchicken.com> (raw)
In-Reply-To: <E1HbUDe-0004vN-1g@fencepost.gnu.org> (Richard Matthew Stallman's message of "Wed\, 11 Apr 2007 00\:14\:06 -0400")

Richard Matthew Stallman <rms@gnu.org> writes:

>     I think only Lisp hackers will encounter/care about such complicated
>     structures, and they are surely able to customize print-length and
>     print-level if necessary.
>
> Lots of users will see these variables in values shown by
> describe-variable.  And even if they know how to customize,
> it is pure inconvenience to require them to do so.
>
> It would be useful for the help buffer to let RET expand the partly
> hidden value, just as evaluation in the buffer does.  And the code
> is already written.

My point is whether this is even necessary for realistic Emacs usage.
In practice, are there any significant Emacs variables containing
circular structures, that users will want to look up using
describe-variable?  I can't think of any off the top of my head.

  reply	other threads:[~2007-04-11  5:16 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-07  0:54 print-circle and describe-variable Lennart Borgman (gmail)
2007-04-07 17:31 ` Richard Stallman
2007-04-09  0:15   ` Stefan Monnier
2007-04-09  1:00     ` Lennart Borgman (gmail)
2007-04-09  7:02       ` Eli Zaretskii
2007-04-09  9:06         ` Lennart Borgman (gmail)
2007-04-09 19:25       ` Stefan Monnier
2007-04-09 19:59         ` Lennart Borgman (gmail)
2007-04-09 23:08           ` Chong Yidong
2007-04-09 23:28             ` Lennart Borgman (gmail)
2007-04-09 23:43               ` Drew Adams
2007-04-10  0:01                 ` Lennart Borgman (gmail)
2007-04-10 15:02                   ` Drew Adams
2007-04-10 15:33                     ` Lennart Borgman (gmail)
2007-04-10 15:50                       ` Drew Adams
2007-04-10 16:32                         ` Lennart Borgman (gmail)
2007-04-10 16:13                       ` Chong Yidong
2007-04-10  1:00           ` Miles Bader
2007-04-10  2:21         ` Richard Stallman
2007-04-10  2:35           ` Chong Yidong
2007-04-11  4:14             ` Richard Matthew Stallman
2007-04-11  5:16               ` Chong Yidong [this message]
2007-04-11 23:04                 ` Richard Matthew Stallman
2007-04-12  9:29                   ` Kim F. Storm
2007-04-13  1:41                     ` Richard Stallman
2007-05-11 16:33                 ` Herbert Euler
2007-04-09 22:52     ` Richard Stallman

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=878xczjxt2.fsf@stupidchicken.com \
    --to=cyd@stupidchicken.com \
    --cc=emacs-devel@gnu.org \
    --cc=lennart.borgman@gmail.com \
    --cc=monnier@iro.umontreal.ca \
    --cc=rms@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).