unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Lennart Borgman'" <lennart.borgman@gmail.com>
Cc: handa@m17n.org, joakim@verona.se, emacs-devel@gnu.org,
	bastienguerry@googlemail.com, 'Eli Zaretskii' <eliz@gnu.org>,
	jem@iki.fi, 'Scot Becker' <scot.becker@gmail.com>,
	miles@gnu.org
Subject: RE: line-move-visual
Date: Fri, 10 Jul 2009 10:20:11 -0700	[thread overview]
Message-ID: <EFE5EC8D827140758A72F8E4AA754E4E@us.oracle.com> (raw)
In-Reply-To: <e01d8a50907100922qac485dm28646b52f012a4b5@mail.gmail.com>

> >> I have wondered whether 'customize' is capable of
> >> letting a user collect an arbitrary set of variables for 
> >> the attention of other users. (Seems that the groups a
> >> variable belongs to are hard coded, though).
> >
> > Something like an `add-group' function that would let you 
> > easily add a Customize group to a given option or face?
> > Yes, that could be useful.
> 
>     (custom-add-to-group 'my-group 'my-variable 'custom-variable))

Well, whaddya know?! Forgot about it, I guess.

So all that's missing in this regard is an easy, non-Lisp way for users to do
the same thing - e.g. a button in Customize.

And then perhaps a good way for users to share their groups (a la skins). Maybe
just create an EmacsWiki page (e.g. GroupsAsSkins) where people can upload their
groups to share.

But that would mean also having Customize produce a `custom-add-to-group' entry
when you add a group to an option, so you could then extract that code from your
custom-file to share.





  reply	other threads:[~2009-07-10 17:20 UTC|newest]

Thread overview: 59+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-09 18:12 line-move-visual Johan Myréen
2009-07-10  4:26 ` line-move-visual Bastien
2009-07-10  4:43   ` line-move-visual Miles Bader
2009-07-10  5:48     ` line-move-visual Bastien
2009-07-10  6:14       ` line-move-visual Kenichi Handa
2009-07-10  6:58         ` line-move-visual Bastien
2009-07-10  8:13           ` line-move-visual Alfred M. Szmidt
2009-07-10 10:10             ` line-move-visual Bastien
2009-07-10  8:43           ` line-move-visual Scot Becker
2009-07-10  8:57             ` line-move-visual Eli Zaretskii
2009-07-10  9:04               ` line-move-visual Lennart Borgman
2009-07-10 10:32                 ` line-move-visual Bastien
2009-07-10  9:08               ` line-move-visual Scot Becker
2009-07-10  9:13               ` line-move-visual joakim
2009-07-10  9:22                 ` line-move-visual Scot Becker
2009-07-10 16:11                   ` line-move-visual Drew Adams
2009-07-10 16:22                     ` line-move-visual Lennart Borgman
2009-07-10 17:20                       ` Drew Adams [this message]
2009-07-10 17:40                         ` line-move-visual Drew Adams
2009-07-10  9:52                 ` line-move-visual Miles Bader
2009-07-10 16:11                   ` line-move-visual Drew Adams
2009-07-10 11:35               ` line-move-visual Stephen J. Turnbull
2009-07-10 13:38                 ` line-move-visual Eli Zaretskii
2009-07-10 16:11                   ` line-move-visual Drew Adams
2009-07-10 18:01                     ` line-move-visual Eli Zaretskii
2009-07-10 18:16                       ` line-move-visual Drew Adams
2009-07-11 19:34                   ` line-move-visual Juri Linkov
2009-07-10 13:56                 ` line-move-visual Lennart Borgman
2009-07-10 15:07                   ` line-move-visual Scot Becker
2009-07-10 20:29                     ` line-move-visual Lennart Borgman
2009-07-10 15:43               ` line-move-visual Alfred M. Szmidt
2009-07-10 15:56             ` line-move-visual Sean O'Rourke
2009-07-10  9:14           ` line-move-visual Tassilo Horn
2009-07-10  9:56             ` line-move-visual Miles Bader
2009-07-10 10:22               ` line-move-visual Scot Becker
2009-07-10 16:11                 ` line-move-visual Drew Adams
2009-07-10 10:36               ` line-move-visual Ulrich Mueller
2009-07-10 10:56                 ` line-move-visual Eli Zaretskii
2009-07-10 11:07                   ` line-move-visual Christian Faulhammer
2009-07-10 11:29                   ` line-move-visual Ulrich Mueller
2009-07-10 18:15                     ` line-move-visual Bastien
2009-07-10 20:40     ` line-move-visual Richard Stallman
2009-07-11  1:58       ` line-move-visual Stephen J. Turnbull
2009-07-11  2:29         ` line-move-visual Miles Bader
2009-07-11  2:44           ` line-move-visual Bastien
2009-07-11 18:30             ` line-move-visual Richard Stallman
2009-07-10  6:12   ` line-move-visual Stephen J. Turnbull
2009-07-10 21:19     ` line-move-visual Johan Myréen
2009-07-10 22:14       ` line-move-visual Scot Becker
2009-07-11  1:34       ` line-move-visual Miles Bader
2009-07-11  2:46       ` line-move-visual Bastien
2009-07-11  5:25         ` line-move-visual Miles Bader
2009-07-11  5:49           ` line-move-visual Kenichi Handa
2009-07-11  6:13             ` line-move-visual Miles Bader
2009-07-11  9:22           ` line-move-visual Bastien
2009-07-10  4:35 ` line-move-visual Miles Bader
2009-07-10 13:31 ` line-move-visual Chong Yidong
2009-07-11  6:42 ` line-move-visual Andrey Paramonov
2009-07-11  7:21   ` line-move-visual Teemu Likonen

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=EFE5EC8D827140758A72F8E4AA754E4E@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=bastienguerry@googlemail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=handa@m17n.org \
    --cc=jem@iki.fi \
    --cc=joakim@verona.se \
    --cc=lennart.borgman@gmail.com \
    --cc=miles@gnu.org \
    --cc=scot.becker@gmail.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).