From: Kevin Rodgers <ihs_4664@yahoo.com>
Subject: Re: [drew.adams@oracle.com: links in Help buffer aren't alwayscorrect]
Date: Tue, 13 Dec 2005 16:53:56 -0700 [thread overview]
Message-ID: <dnnmun$tl9$1@sea.gmane.org> (raw)
In-Reply-To: <DNEMKBNJBGPAOPIJOOICAECNDAAA.drew.adams@oracle.com>
Drew Adams wrote:
> There may not be a `describe-frame-parameter' function, but the
> `help-make-xrefs' code could use a preceding "frame parameter" to link to
> the Info section describing the `buffer-list' parameter. Or, at the very
> least, it could test for preceding "frame parameter" in order to do
nothing
> (add no link) if it is present.
Here's a start, cobbled together from describe-variable and your idea of
linking to the Info node:
(defun describe-frame-parameter (parameter &optional frame)
"Display the full documentation of frame PARAMETER (a symbol) in FRAME.
If FRAME is nil, describe the selected frame's parameter value."
(interactive
(let* ((enable-recursive-minibuffers t)
(default-param (symbol-at-point))
(param-alist (frame-parameters nil))
(param-name
(completing-read (if (assq default-param param-alist)
(format "Describe parameter (default %s): "
default-param)
"Describe parameter: ")
obarray
(lambda (p) (assq p param-alist))
t nil nil
(if default-param (symbol-name
default-param)))))
(list (if (equal param-name "")
default-param
(intern param-name)))))
(if (null frame)
(setq frame (selected-frame)))
(if (null parameter)
(message "You did not specify a frame parameter")
(with-output-to-temp-buffer "*Help*"
(prin1 parameter)
(princ "'s value is ")
(terpri)
(let ((param-value (frame-parameter frame parameter)))
(with-current-buffer standard-output
(let ((from (point)))
(pp param-value)
;; (help-xref-on-pp from (point))
(if (< (point) (+ from 20))
(save-excursion
(goto-char from)
(delete-char -1))))))
(terpri)
(terpri)
(princ "Documentation (see Info node `(elisp)Window Frame
Parameters'):")
(terpri)
(save-excursion
(save-window-excursion
(Info-goto-node "(elisp)Window Frame Parameters")
(princ (buffer-substring
(re-search-forward (concat "^`" (symbol-name
parameter) "'"))
(1- (or (re-search-forward "^`" nil t)
(point-max))))))))))
--
Kevin Rodgers
next prev parent reply other threads:[~2005-12-13 23:53 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
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 [this message]
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='dnnmun$tl9$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).