unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Samuel Wales" <samologist@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: ideas for customize
Date: Sat, 3 Jan 2009 16:49:26 -0700	[thread overview]
Message-ID: <20524da70901031549t392be529v2f5104547427554a@mail.gmail.com> (raw)

Recently two people expressed different opinions on the value of
customize.  I hope that this email helps create more understanding.

A lot of people seem to find customize irksome.  I very much
appreciate the work that went into it and the philosophy
behind it, but I admit that I, too, don't use it (except for
faces because I don't know how to do those otherwise).

Here are some extemporaneous ideas for possible ways to
improve it.

These are just my impressions and some of them might be
incorrect.  I might have missed a few things.

However, I hope that they are useful.  :)

  - the customizable entries should stand out.  but some
    are in a special face while others are not.  help text
    and docstrings look the same as the entries.  a special
    face, perhaps red, used for all customizable entries and
    not used for anything else, would help.
  - help text does not take into account window-width.  it
    should fill according to window-width minus a fixed
    amount.  this should also optionally occur for docstring
    text, ideally trying to notice, filladapt-style, when
    there is a table, a list, or code.
  - it is not easy to navigate with the keyboard.  n and p
    get stuck on values, then you have to manually go to the
    next widget.
  - too many keystrokes to try various settings (e.g. try
    various faces).
  - perhaps something like orgstruct minor mode could be
    used to organize the customize buffer so that users do
    not have to learn a special way of interacting.
  - a more flexible infrastructure for customize-changed,
    which also works for large packages that do not come
    with emacs, might be nice.
  - the difference between "undo edits" and "reset to saved"
    is not clear.  rewording would help.
  - it is not clear how to .emacs -ize custom code.  simple
    for variables, less so for faces.  also not clear when
    to do so, in the case of faces.  for example, will a
    restart of emacs be necessary?
  - having the entries in custom-set-variables and
    custom-set-faces include the (useless for it but useful
    for the user) setq or set-face (or whatever it is) would
    make it easy to cut and paste from the custom section to
    your own .emacs.
  - it is not easy to hide and unhide.  a key would be
    easier than buttons.
    - have help text tell you how.
  - trees should be easier to fold and unfold, perhaps with
    a key.
  - a command for next and previous (perhaps redefining n
    and p) which also optionally hides and unhides
    everything as you navigate, would also help.
  - it seems to say changed outside of customized even when
    it is not.  have not tracked this down.  comment
    perhaps.
  - choosing numbers to choose the state requires a
    translation step.  selecting by letter would be less
    cognitively burdensome.

Again these are just possibilities for improving the (imo)
good start that is customize.

-- 
For personal gain, myalgic encephalomyelitis denialists are knowingly
causing further suffering and death by grossly corrupting science.  Do
you care about the world?
http://www.meactionuk.org.uk/What_Is_ME_What_Is_CFS.htm




             reply	other threads:[~2009-01-03 23:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-03 23:49 Samuel Wales [this message]
2009-01-04  0:01 ` ideas for customize Drew Adams
2009-01-04  0:12   ` Samuel Wales
2009-01-04  0:57     ` Drew Adams

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=20524da70901031549t392be529v2f5104547427554a@mail.gmail.com \
    --to=samologist@gmail.com \
    --cc=help-gnu-emacs@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.
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).