From: "Drew Adams" <drew.adams@oracle.com>
To: <rms@gnu.org>
Cc: juri@jurta.org, emacs-devel@gnu.org
Subject: RE: customizing key definitions with Customize
Date: Fri, 16 May 2008 01:01:40 -0700 [thread overview]
Message-ID: <004a01c8b72b$1361c370$0200a8c0@us.oracle.com> (raw)
In-Reply-To: <E1JwhQs-0005K9-3d@fencepost.gnu.org>
> handle it as I suggested: customize an option. A keymap-valued
> symbol is just a variable. Either such a variable could itself
> be made a user option or, as I showed, a separate but
> corresponding user option can be created. Both approaches can
> be treated the same way (e.g. as I indicated); it depends on
> what we want.
>
> If we want a given keymap variable itself to be completely
> customizable (i.e., for all of its keys), then we can just
> make it a defcustom of the sort I indicated. If we want some
> keymap variables not to be options, then we need not
> use defcustom for them.
>
> Now it seems you are saying that the _code_ should choose whether the
> user should see the entire keymap or just his changes.
Don't know what you mean by that. What I meant was that it could be useful for
code (e.g. a library, built-in or 3rd-party) to decide whether and how much of a
given keymap should be customizable, by default. I'm talking possibilities, not
"should".
I can see some use value in not always presenting a user, by default, with a
complete keymap to customize. That's all. That doesn't mean we couldn't also
provide a way for a user to go ahead and customize the whole keymap. I'm
thinking of user convenience and possible confusion.
> We were already aware of that possibility, but it has an obvious
> drawback. That is why I suggested that we instead let the _user_
> choose one or the other, for each keymap.
I'm not sure we're saying something different. Nothing would prevent a user from
customizing a complete keymap. But a library might want to (also) give users a
lite keymap option that only shows some of the keys in a map.
Anyway, in the approach I outlined, the flexibility is there to do both.
next prev parent reply other threads:[~2008-05-16 8:01 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-11 19:40 customizing key definitions with Customize Drew Adams
2008-05-11 22:02 ` Lennart Borgman (gmail)
2008-05-11 22:28 ` Drew Adams
2008-05-11 22:40 ` Lennart Borgman (gmail)
2008-05-11 23:02 ` Drew Adams
2008-05-11 23:09 ` Lennart Borgman (gmail)
2008-05-11 23:19 ` Drew Adams
2008-05-11 23:23 ` Lennart Borgman (gmail)
2008-05-11 23:34 ` Drew Adams
2008-05-12 20:42 ` Lennart Borgman (gmail)
2008-05-14 5:24 ` Drew Adams
2008-05-12 8:59 ` Reiner Steib
2008-05-12 20:58 ` Drew Adams
2008-05-12 11:20 ` Richard M Stallman
2008-05-12 14:01 ` Drew Adams
2008-05-13 0:03 ` Juri Linkov
2008-05-13 0:40 ` Lennart Borgman (gmail)
2008-05-13 14:59 ` Richard M Stallman
2008-05-13 23:59 ` Juri Linkov
2008-05-14 1:10 ` Stefan Monnier
2008-05-14 16:40 ` Richard M Stallman
2008-05-15 4:46 ` Drew Adams
2008-05-15 17:39 ` Richard M Stallman
2008-05-16 8:01 ` Drew Adams [this message]
2008-05-16 17:46 ` Richard M Stallman
2008-05-16 18:00 ` David Kastrup
2008-05-16 23:58 ` Drew Adams
2008-05-17 5:00 ` Richard M Stallman
2008-05-16 7:51 ` Drew Adams
2008-05-18 1:22 ` Drew Adams
2008-05-18 9:07 ` Key/menu bug? (was: customizing key definitions with Customize) David Kastrup
2008-05-13 15:07 ` customizing key definitions with Customize David Reitter
2008-05-13 19:05 ` David Kastrup
2008-05-14 5:23 ` Drew Adams
2008-05-13 5:16 ` Richard M Stallman
2008-05-14 5:23 ` Drew Adams
2008-05-14 16:39 ` Richard M Stallman
2008-05-15 4:36 ` Drew Adams
2008-05-15 17:39 ` Richard M Stallman
2008-05-16 8:02 ` Drew Adams
2008-05-16 17:46 ` Richard M Stallman
2008-05-16 23:58 ` Drew Adams
2008-05-12 20:42 ` Lennart Borgman (gmail)
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='004a01c8b72b$1361c370$0200a8c0@us.oracle.com' \
--to=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=juri@jurta.org \
--cc=rms@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.