unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Getting help for a widget
Date: Sat, 01 Apr 2006 08:45:41 -0500	[thread overview]
Message-ID: <E1FPgQ9-0004mE-D5@fencepost.gnu.org> (raw)
In-Reply-To: <DNEMKBNJBGPAOPIJOOICMEEIDEAA.drew.adams@oracle.com>

    This is perhaps the main difficulty of working with or even talking about
    widgets (and, so, with Customize too) as either a user or a casual
    developer: understanding what the &^!@% is going on.

I agree.  I find it very hard to understand that code.

But what does it mean to "get help for a widget"?
It is not clear to me, and maybe there is more than one
kind we need.

    If you press

	C-h k

    on a file you get help for `widget-button-press'. But what does the 
    button do?

I don't really follow that, but it seems to be a request
for a better answer to the question, "What happens if i click here"?

That could be useful, and perhaps C-h k ought to make a special
case for the function widget-button-press.  That would not be hard.
But where can it get the useful doc string to display?

Meanwhile, this would not help people who are doing programming with
widgets.  They need a different kind of help.

In other words, it will take some real thought and study to figure out
what "good help for widgets" would mean.  It would be useful for
people to start exploring this now.

  reply	other threads:[~2006-04-01 13:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-31 12:07 Getting help for a widget Lennart Borgman
2006-03-31 14:36 ` Drew Adams
2006-04-01 13:45   ` Richard Stallman [this message]
2006-04-02  9:30     ` Lennart Borgman
2006-04-02 15:19       ` Drew Adams
2006-04-03  1:08       ` Richard Stallman
2006-04-04 20:16         ` Lennart Borgman
2006-04-08  0:05           ` Lennart Borgman

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=E1FPgQ9-0004mE-D5@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).