unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Kevin Rodgers <ihs_4664@yahoo.com>
Subject: Re: [drew.adams@oracle.com: links in Help buffer aren't always correct]
Date: Tue, 13 Dec 2005 10:17:36 -0700	[thread overview]
Message-ID: <dnmvnj$afd$1@sea.gmane.org> (raw)
In-Reply-To: <E1Em0dJ-0002Ns-7u@fencepost.gnu.org>

Richard Stallman wrote:
> Would someone please DTRT about this, then ack?
> 
> ------- Start of forwarded message -------
> From: "Drew Adams" <drew.adams@oracle.com>
> To: "Emacs-Pretest-Bug" <emacs-pretest-bug@gnu.org>
> Date: Mon, 28 Nov 2005 08:58:08 -0800
> X-Brightmail-Tracker: AAAAAQAAAAI=
> X-Whitelist: TRUE
> Subject: links in Help buffer aren't always correct
> Sender: emacs-pretest-bug-bounces+rms=gnu.org@gnu.org
> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on monty-python
> X-Spam-Level: 
> X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.63
> 
> For example, C-h f buffer-list shows this text:
> 
>  buffer-list is a built-in function in `C source code'.
>  (buffer-list &optional frame)
> 
>  Return a list of all existing live buffers.
>  If the optional arg frame is a frame, we return the buffer list
>  in the proper order for that frame: the buffers in frame's `buffer-list'
>  frame parameter come first, followed by the rest of the buffers.

I think it would be better to say:
   the buffers in FRAME's `buffer-list' frame parameter come first,
or:
   the buffers in the frame's `buffer-list' frame parameter come first,
or:
   the buffers in its `buffer-list' frame parameter come first,

>  [back]
> 
> The text "buffer-list" in the last sentence is linked to the help for the
> `buffer-list' function, not the `buffer-list' frame parameter. Either there
> should be no link here (if there is no way to show help on the parameter) or
> the link should point to help on the frame parameter.

Since there is no describe-frame-parameter command, and the phrase
"frame paramter" follows the quoted symbol (unlike the phrases listed
in help-xref-symbol-regexp, which precede quoted symbols), we can avoid
hyperlinking such phrases by changing help-make-xrefs in help-mode.el
from:

               ;; Quoted symbols
               (save-excursion
                 (while (re-search-forward help-xref-symbol-regexp nil t)
                   (let* ((data (match-string 8))
                          (sym (intern-soft data)))
                     (if sym

to:

               ;; Quoted symbols
               (save-excursion
                 (while (re-search-forward help-xref-symbol-regexp nil t)
                   (let* ((data (match-string 8))
                          (sym (intern-soft data)))
                     (if (and sym
                              (save-match-data
                                (not (looking-at "[ \t\n]+frame 
parameter"))))

-- 
Kevin Rodgers

  reply	other threads:[~2005-12-13 17:17 UTC|newest]

Thread overview: 19+ 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 [this message]
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
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

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='dnmvnj$afd$1@sea.gmane.org' \
    --to=ihs_4664@yahoo.com \
    /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).