From: Lawrence Mitchell <wence@gmx.li>
To: 10868@debbugs.gnu.org
Subject: bug#10868: 24.0.93; `comment-style' needs to be explained
Date: Thu, 23 Feb 2012 17:24:00 +0000 [thread overview]
Message-ID: <877gzdxy33.fsf@gmx.li> (raw)
In-Reply-To: <DB139E6F33CC441B9C3798B66C9D52FE@us.oracle.com>
Glenn Morris wrote:
> Lawrence Mitchell wrote:
>> The docstring of comment-style refers the user to comment-styles for
>> details on what the values mean. However, this is not available until
>> after newcomment.el is loaded. So autoload comment-styles to avoid
>> this problem.
> Then this is an instance of a general problem. See eg
> http://debbugs.gnu.org/cgi/bugreport.cgi?bug=1768
> for the same thing.
> IMO there should be a general solution rather than papering over every
> instance that occurs with more pre/autoloading.
Sure, but you can't do this, right? You don't know where the
variable is defined until /after/ the file it's defined in is
loaded. Sure, you can guess that links in a docstring for a
variable that is autoloaded from package foo may also lead to
other variables in package foo, but that's not foolproof.
I guess the help system could load the file of autoloaded
variables when showing their docstring, but people are bound to
complain about that too.
Lawrence
next prev parent reply other threads:[~2012-02-23 17:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-22 17:17 bug#10868: 24.0.93; `comment-style' needs to be explained Drew Adams
2012-02-22 17:38 ` Glenn Morris
2012-02-22 18:06 ` Drew Adams
2012-02-22 18:11 ` Glenn Morris
2012-02-22 19:01 ` Drew Adams
2012-02-23 9:22 ` Lawrence Mitchell
2012-02-23 14:31 ` Stefan Monnier
2012-02-23 15:35 ` Drew Adams
2012-02-23 16:04 ` Stefan Monnier
2012-02-23 16:13 ` Drew Adams
2012-02-25 3:08 ` Chong Yidong
2012-02-23 17:16 ` Glenn Morris
2012-02-23 17:22 ` Glenn Morris
2012-02-23 17:24 ` Lawrence Mitchell [this message]
2012-02-23 17:34 ` Drew Adams
2012-02-23 21:48 ` Finding a variable before it's loaded Stefan Monnier
2012-02-23 22:29 ` Lennart Borgman
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=877gzdxy33.fsf@gmx.li \
--to=wence@gmx.li \
--cc=10868@debbugs.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.