From: "Richard M. Stallman" <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: [drew.adams@oracle.com: links in Help buffer aren'talwayscorrect]
Date: Thu, 15 Dec 2005 12:08:39 -0500 [thread overview]
Message-ID: <E1Emwat-0007KK-Vt@fencepost.gnu.org> (raw)
In-Reply-To: <dnqfrj$ljp$1@sea.gmane.org> (message from Kevin Rodgers on Wed, 14 Dec 2005 18:11:12 -0700)
> Perhaps too, the doc string should mention that it only works on documented
> built-in frame parameters, not user-defined parameters.
That goes without saying, since the point of the command is to show
the documentation, and only frame parameters with standard meanings
have standard documentation.
Good point. I think that since Info-goto-node displays the *Info*
buffer, it should be declared as an (interactive) command, and
therefore that it should be autoloaded.
It is already interactive. However, programs normally do this
job by calling `info' or `info-other-window'. They are autoloaded.
next prev parent reply other threads:[~2005-12-15 17:08 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-13 3:15 [drew.adams@oracle.com: links in Help buffer aren't always correct] Richard Stallman
2005-12-13 17:17 ` Kevin Rodgers
2005-12-13 19:52 ` [drew.adams@oracle.com: links in Help buffer aren't alwayscorrect] Drew Adams
2005-12-13 23:53 ` Kevin Rodgers
2005-12-14 18:10 ` Kevin Rodgers
2005-12-14 20:02 ` Richard M. Stallman
2005-12-14 22:48 ` [drew.adams@oracle.com: links in Help buffer aren'talwayscorrect] Drew Adams
2005-12-15 1:11 ` Kevin Rodgers
2005-12-15 2:01 ` [drew.adams@oracle.com: links in Help bufferaren'talwayscorrect] Drew Adams
2005-12-15 3:16 ` [drew.adams@oracle.com: links in Help buffer aren'talwayscorrect] Stefan Monnier
2005-12-15 17:08 ` Richard M. Stallman [this message]
2005-12-15 4:39 ` Eli Zaretskii
2005-12-15 15:39 ` bad mailer Subject meddling (was: links in Help buffer aren't always correct) Drew Adams
2005-12-15 18:47 ` Alfred M. Szmidt
2005-12-16 5:08 ` Richard M. Stallman
2005-12-16 7:55 ` Eli Zaretskii
2005-12-15 19:43 ` Eli Zaretskii
2005-12-15 17:08 ` [drew.adams@oracle.com: links in Help buffer aren'talwayscorrect] Richard M. Stallman
2005-12-16 18:53 ` Kevin Rodgers
[not found] <E1EnQVb-00056d-Vz@fencepost.gnu.org>
2005-12-19 19:22 ` Kevin Rodgers
2005-12-20 19:10 ` Kevin Rodgers
2005-12-20 19:59 ` Stefan Monnier
2005-12-23 17:07 ` Kevin Rodgers
2005-12-23 17:47 ` Eli Zaretskii
[not found] <E1Eoa6a-0004hk-QI@fencepost.gnu.org>
2005-12-20 16:09 ` Kevin Rodgers
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=E1Emwat-0007KK-Vt@fencepost.gnu.org \
--to=rms@gnu.org \
--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).