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'talwayscorrect]
Date: Fri, 16 Dec 2005 11:53:40 -0700	[thread overview]
Message-ID: <dnv2fp$bim$1@sea.gmane.org> (raw)
In-Reply-To: <E1Emwaf-0007C8-RB@fencepost.gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1689 bytes --]

Richard M. Stallman wrote:
> 	describe-frame-parameter seems to work usefully, but it has one
> 	problem: its completion list is incomplete.
> 
>     Do you mean because it iterates only over the parameters of the selected
>     frame?
> 
> I wasn't sure exactly what it does, but it certainly omits many
> standard frame parameter names.  I don't think whether the selected
> frame has a setting for a particular frame parameter ought to affect
> whether I can complete its name.
> 
>     It might also include user-defined parameters that won't be documented in
>     Info. Perhaps it should instead iterate over an explicit list of all of the
>     Info-documented (built-in) frame parameters.
> 
> I think that is the best thing to do.  Or else get that from the
> manual too.

OK, the attached version addresses all the points that have been raised:

* It defines a global list of documented frame parameters, which is
   initialized from the manual (using info, not Info-goto-node), and
   which can be augmented with user-defined parameters.

* The global list is actually an alist mapping parameters to their doc
   strings, so the doc strings are only extracted once from the manual
   and cached there.

* Completion uses the union of the documented frame parameters and any
   other parameters set in the selected frame.  The symbol at point is
   only provided as a default if it's a member of that union.

* The Info xrefs and indentation have been removed from the doc string,
   and it's been reformatted (filled) to account for that.

* Like variables, undocumented frame parameters are described as "not
   documented" and there's no link to the manual.

Enjoy!
-- 
Kevin

[-- Attachment #2: describe-frame-parameter.el --]
[-- Type: application/emacs-lisp, Size: 4265 bytes --]

[-- Attachment #3: Type: text/plain, Size: 142 bytes --]

_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel

  reply	other threads:[~2005-12-16 18:53 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
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 [this message]
     [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='dnv2fp$bim$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).