Drew Adams wrote:
The question was about "getting" values from a custom file without loading
that file. You are confirming, I guess, that there is no way to change
custom-file for purposes of get-but-do-not-load.
Setting custom-file _during an Emacs session_ is usually with the
intent to
> If it implies reading from the file, this could
> be used to load values from a diffent custom-file
> (to see what they are) before actually using them.
>
> No way to do that has yet been proposed. S=>F me
> If it implies reading from the file, this could
> be used to load values from a diffent custom-file
> (to see what they are) before actually using them.
>
> No way to do that has yet been proposed. S=>F means
> to
Lennart Borgman wrote:
The suggested (load custom-file) looks like it means "this is where we read
from".
(load "file") _does_ means to load "file", that is to read from the file.
(setq custom-file "file") means that Custom should write its saved
values into "file". Maybe you do not even
- Original Message -
From: "Luc Teirlinck" <[EMAIL PROTECTED]>
>> Absolutely not. `(setq custom-file "Y")' means that you want Custom
to
>> _write_ to Y. If you want Y to be read you have to load Y.
>..
>> (setq custom-file "Y")
>> (load custom-file)
..
> Where is the
Lennart Borgman wrote:
> Absolutely not. `(setq custom-file "Y")' means that you want Custom to
> _write_ to Y. If you want Y to be read you have to load Y.
..
> (setq custom-file "Y")
> (load custom-file)
Is not this a bit of a contradiction? I would not say that the semantic
- Original Message -
From: "Luc Teirlinck" <[EMAIL PROTECTED]>
>M-: (setq custom-file "X")
>M-x customize
>do some editing
>save (into X)
>M-: (setq custom-file "Y")
>get (from ?)
>
>Question is "from X" or "from Y"?
>
>Good poin
The key is to satisfy both novices and experts
Provide a good default interface for novices and also a way for
that novice to become an expert without too much trouble
That is why Customize should not only do its job, but make
it easy for a person to learn.
I don't agre
> The information should be readily available.
You can look into .emacs. The information is not encrypted, it is not
binary.
It is a good idea for every program to help users find the internal
data that implements any particular customization. But since all the
Customize data is tog
"Robert J. Chassell" <[EMAIL PROTECTED]> writes:
> That is why I dislike a car with a dashboard that never let's me see
> anything; why I dislike car which requires my mechanic to purchase a
> special device to find out what is going on.
>
> The information should be readily available.
You can lo
IMO, the beauty of Customize is that it hides all the nitty gritty
details that no users (novices or experts) need to worry about.
Emacs describes itself as
extensible,
customizable,
self-documenting,
real-time,
display.
Nowadays, few environments work just on a lin
> (custom-set-variables
> ;; ...
> '(baud-rate 38400)
... the above is a bad idea: it is not good elisp code ...
I am not going to say it is good code. (Your `setq' example is
better.) Unfortunately, that is what is currently written
automatically in one's .emacs f
"Robert J. Chassell" <[EMAIL PROTECTED]> writes:
> Customize is a can of worms. But the worms can improve the garden if
> handled rightly!
I don't see how the changes you suggest can be seen as an improvement.
Quite the opposite.
IMO, the beauty of Customize is that it hides all the nitty gritt
> should show in the value window the humanly readable version of what
> is set, such as
> (custom-set-variables
> ;; ...
> '(baud-rate 38400)
> ;; ... )
Whether we want to teach users or not, the above is a bad idea: it is not
good elisp code and noone should write such a thin
"Robert J. Chassell" <[EMAIL PROTECTED]> writes:
> 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.
So what?
> They wi
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 e
"Robert J. Chassell" <[EMAIL PROTECTED]> writes:
> How can you save Customize settings without also setting their
> current values (today)? And, again, changing a value in your init
> file is not what is meant currently by "set"; "set" refers to
> setting the current values.
>
> Ju
... the current value is updated to the same value that is written
to your custom file. That is not the same thing as evaluating your
entire .emacs file, however.
I am refering to `All'. Clearly, individual settings should not
involve evaluating your entire .emacs file.
How can y
I don't understand this. Set All (F=>C) means set all current
values (C) to the values shown in the edit fields (F). What does
this have to do with the init file?
Everything is written to the init file (or files loaded from it); that
is where customization forms are ev
19 matches
Mail list logo
