unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "Lennart Borgman \(gmail\)" <lennart.borgman@gmail.com>
Cc: "Stephen J. Turnbull" <stephen@xemacs.org>,
	Emacs-Devel <emacs-devel@gnu.org>
Subject: RE: always put Customizations in `custom-file', never in `user-init-file'
Date: Mon, 10 Dec 2007 15:09:04 -0800	[thread overview]
Message-ID: <BNELLINCGFJLDJIKDGACAELOCFAA.drew.adams@oracle.com> (raw)
In-Reply-To: <475DBF19.4050501@gmail.com>

> > `custom-file' would not be loaded automatically, but only
> > when (where) the user requests via (load-file custom-file).
>
> If you do not mean that custom-file should be loaded automatically then
> I must have misunderstood you.

Yes, I think you did. I said that `custom-file' would be loaded explicitly:
(load-file custom-file). Just as it is now. All I proposed was that any
Customize stuff currently in `user-init-file' should be moved to
`custom-file'.

> I thought it would be a good idea to by
> default have custom-file separate,

You were right. And not just by default.

> but as Jason points out there was
> probably a good reason why this was not done from the beginning.

So what you thought would be a good idea turns out in fact to be a bad idea
simply because someone designed the status quo? Sheesh! You say you don't
know what the arguments behind the design were, but, although unknown, the
fact that they "probably" existed is enough to convince you to change your
mind?

We need never think again: our world is a product of decisions and other
actions, many of which were "probably" made consciously. Let it be.

What kind of an argument is that? Of course there was "probably a good
reason". That doesn't mean that the best decision was made then or, a
fortiori, that that decision is also the best decision now.

If you want to make specific arguments, whether repeated from a previous
discussion or not, please do. But let's not argue only from authority,
saying that whatever is, is right.

> Though I can't remember that reason now. Maybe it had something
> to do with the order of loading? Maybe it was some problem
> with custom-set-variables from the beginning?

Maybe those maybe's don't help. What about the order of loading? With an
explicit (load-file custom-file), you can have any order you like. What
problem with custom-set-variables from the beginning?

It doesn't help here to grasp at straws or appeal to authority. Let's
discuss the pros and cons and forget about imagining what someone might have
thought about this long ago, if it was in fact thought about in this way.

This is nuts. We can't have a discussion if as soon as someone says, in
effect, "that's the way it is because that's the way it was decided" we stop
thinking about it.

  reply	other threads:[~2007-12-10 23:09 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-10 19:02 always put Customizations in `custom-file', never in `user-init-file' Drew Adams
2007-12-10 19:21 ` Eric Hanchrow
2007-12-10 20:30 ` Lennart Borgman (gmail)
2007-12-10 21:19   ` Stephen J. Turnbull
2007-12-10 21:25     ` Lennart Borgman (gmail)
2007-12-10 22:12       ` Drew Adams
2007-12-10 22:35         ` Lennart Borgman (gmail)
2007-12-10 23:09           ` Drew Adams [this message]
2007-12-10 23:19             ` Lennart Borgman (gmail)
2007-12-10 23:44               ` Drew Adams
2007-12-11  0:05                 ` Jason Rumney
2007-12-11  0:16                 ` Lennart Borgman (gmail)
2007-12-10 22:56       ` Stephen J. Turnbull
2007-12-10 23:06         ` David Kastrup
2007-12-11  0:07           ` Stephen J. Turnbull
2007-12-10 23:08         ` Drew Adams
2007-12-11  0:31           ` Stephen J. Turnbull
2007-12-10 22:08     ` Drew Adams
2007-12-10 23:45       ` Stephen J. Turnbull
2007-12-11  0:14         ` Lennart Borgman (gmail)
2007-12-11  1:04           ` Stephen J. Turnbull
2007-12-11  6:05           ` Drew Adams
2007-12-11  0:47         ` Drew Adams
2007-12-11  2:20           ` Stephen J. Turnbull
2007-12-11  6:15             ` Drew Adams
2007-12-11  9:53               ` Stephen J. Turnbull
2007-12-11 16:57                 ` Drew Adams
2007-12-12 10:00                   ` Stephen J. Turnbull
2007-12-12 16:31                     ` Drew Adams
2007-12-11 19:01           ` Richard Stallman
2007-12-11 19:12             ` Drew Adams
2007-12-10 21:58   ` Drew Adams
2007-12-11  4:00     ` Stefan Monnier
2007-12-11  6:04       ` Drew Adams
2007-12-11 14:52         ` Stefan Monnier
2007-12-11 16:58           ` Drew Adams
2007-12-11 22:12             ` David Kastrup
2007-12-10 22:07 ` Jason Rumney
2007-12-10 23:08   ` Drew Adams
2007-12-11  3:02 ` Robert J. Chassell
2007-12-11  6:06   ` Drew Adams
2007-12-11 11:39     ` Robert J. Chassell
2007-12-11 16:58       ` Drew Adams
2007-12-11 19:00 ` Richard Stallman

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=BNELLINCGFJLDJIKDGACAELOCFAA.drew.adams@oracle.com \
    --to=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=lennart.borgman@gmail.com \
    --cc=stephen@xemacs.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).