unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Robert J. Chassell" <bob@rattlesnake.com>
Subject: Re: Customize buttons that change user'scustomfileshouldaskforconfirmation
Date: Thu, 10 Feb 2005 17:25:52 +0000 (UTC)	[thread overview]
Message-ID: <m1CzI4e-0004R0C@rattlesnake.com> (raw)

Customize is a can of worms.  But the worms can improve the garden if
handled rightly!

As others feared years ago, I now fear that some will come to depend
on their .emacs file being written automatically by Customize.  They
will lose or not gain an understanding of the technology.  This
applies especially to people who are not programmers and who do not
wish to become programmers.

Customize should always show what it is automatically writing, just as
menu items always show key strokes, so anyone can become more expert
and more efficient if he or she wants.

This does not force anyone to learn anything, but it makes that
learning easy.  The person faces a low hill rather than a steep
mountain.

For a single value, 

    `Set for Current Session'

should show in the value window the humanly readable version of what
is set, such as

    (custom-set-variables
     ;; ...
     '(baud-rate 38400)
     ;; ... )

which takes a minimum of four lines.  (The current interface requires
one line, but does not show the complete expression.)  This need for
extra lines is a problem that I do not think we can avoid.

The commentary should say, as it does now,

    you have set this option, but not saved it for future sessions.


For future sessions, for a single value, we should replace `Save for
Future Sessions' with the more accurate statement

    `Set and Save', 

write the four line expression in the value window, and say in the
commentary

    you have set this option and saved it in your initialization file

So you would see in your  *Customize Face: bold*  buffer

    (custom-set-faces
     ;; ...
     '(bold ((t (:background "DodgerBlue4" :foreground "PaleGreen"))))
     ;; ... )

and the same expression, with the other custimized faces, too, in your
.emacs file.

As for `All': when using the automatic writing feature for
customization, that only makes sense as both a set and a save.
Otherwise, novices might inadvertently come to think that you need to
start a new instance of Emacs to gain new customizations.

-- 
    Robert J. Chassell                         
    bob@rattlesnake.com                         GnuPG Key ID: 004B4AC8
    http://www.rattlesnake.com                  http://www.teak.cc

             reply	other threads:[~2005-02-10 17:25 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-10 17:25 Robert J. Chassell [this message]
2005-02-10 18:25 ` Customize buttons that change user'scustomfileshouldaskforconfirmation David Kastrup
2005-02-10 19:01 ` Stefan Monnier
2005-02-10 22:49   ` Robert J. Chassell
2005-02-10 21:39 ` Kim F. Storm
2005-02-10 23:45   ` Robert J. Chassell
2005-02-11  0:54     ` David Kastrup
2005-02-12  8:38       ` Richard Stallman
2005-02-12 18:20     ` Drew Adams
  -- strict thread matches above, loose matches on Subject: below --
2005-02-12 18:04 Customize buttons that change user's customfileshouldaskforconfirmation Drew Adams
2005-02-12 18:45 ` Luc Teirlinck
2005-02-12 21:01   ` Customize buttons that change user'scustomfileshouldaskforconfirmation Lennart Borgman
2005-02-12 21:21     ` Luc Teirlinck
2005-02-12 21:28       ` Lennart Borgman
2005-02-12 21:42         ` Luc Teirlinck
2005-02-14  2:07   ` Drew Adams
2005-02-14  2:21     ` Drew Adams
2005-02-14  3:32     ` Luc Teirlinck
2005-02-09 20:31 Customize buttons that change user's customfileshouldaskforconfirmation Robert J. Chassell
2005-02-09 21:27 ` Customize buttons that change user'scustomfileshouldaskforconfirmation Drew Adams
2005-02-10 14:42   ` Robert J. Chassell
2005-02-10 15:20     ` Kim F. Storm
2005-02-07  7:34 Customize buttons that change user's customfileshouldaskforconfirmation Drew Adams
2005-02-07 17:28 ` Customize buttons that change user'scustomfileshouldaskforconfirmation Drew Adams
2005-02-07 20:23   ` Robert J. Chassell
2005-02-07 20:26   ` Lennart Borgman
2005-02-08 11:46     ` Richard Stallman
2005-02-07  5:32 Customize buttons that change user's custom fileshouldaskforconfirmation Drew Adams
2005-02-07  7:25 ` Customize buttons that change user's customfileshouldaskforconfirmation Lennart Borgman
2005-02-07 13:45   ` Robert J. Chassell
2005-02-07 16:46     ` Customize buttons that change user'scustomfileshouldaskforconfirmation Lennart Borgman
2005-02-07 14:15   ` Customize buttons that change user's customfileshouldaskforconfirmation Robert J. Chassell
2005-02-07 16:23     ` Customize buttons that change user'scustomfileshouldaskforconfirmation Lennart Borgman
2005-02-07 20:22       ` Robert J. Chassell

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=m1CzI4e-0004R0C@rattlesnake.com \
    --to=bob@rattlesnake.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).