From: "Drew Adams" <drew.adams@oracle.com>
Subject: RE: [drew.adams@oracle.com: links in Help bufferaren'talwayscorrect]
Date: Wed, 14 Dec 2005 18:01:56 -0800 [thread overview]
Message-ID: <DNEMKBNJBGPAOPIJOOICCEEGDAAA.drew.adams@oracle.com> (raw)
In-Reply-To: <dnqfrj$ljp$1@sea.gmane.org>
And if there were a define-frame-parameter function and/or defframeparam
macro that would maintain a global list (or obarray) of frame
parameters, it would allow `M-x describe-frame-parameter' and `M-x
set-frame-parameter' to reliably complete over both documented and
user-defined frame parameters.
Yes, that would be useful: letting users document user-defined params with a
doc string. (After the release... waiting for godot... after the release...)
next prev parent reply other threads:[~2005-12-15 2:01 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
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 [this message]
2005-12-15 3:16 ` 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=DNEMKBNJBGPAOPIJOOICCEEGDAAA.drew.adams@oracle.com \
--to=drew.adams@oracle.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).