Richard Stallman wrote:
UNCUSTOMIZABLE, you should not see this.
How about
NO CUSTOMIZATION DATA; you should not see this.
I installed the latter. It really does not matter that much, since
those variables really should not find their way into Custom buffers.
Sincerely,
Luc.
EDITED, shown value does not take effect until you set or save it.
That is good.
SET for current session only.
That is good.
UNCUSTOMIZABLE, you should not see this.
How about
NO CUSTOMIZATION DATA; you should not see this.
___
Emac
The idea of using capitalized keywords is good, but you've shortened
some of the messages too much. I don't like these:
! EDITED, but not set." "\
What about:
EDITED, shown value does not take effect until you set or save it.
! SET, but not saved." "\
What about:
SET for curr
The idea of using capitalized keywords is good, but you've shortened
some of the messages too much. I don't like these:
! EDITED, but not set." "\
you have edited something in this group, but not set anything yet.")
(set "+" custom-set-face "\
! SET, but not saved." "\
An
>From my previous reply:
If deemed _really_ necessary, there would be place for things like:
SAVED, but not set. Code written into `custom-file'.
Or, less accurately, if custom-file is set:
SAVED, but not set. Code written in your init file.
That could be somewhat confusing again
Lennart Borgman wrote:
Put a link to an Info page with information about where the saving is done
in the customize buffer.
I agree. Moreover, other people have asked for a link explaining
`custom-file'.
I enclose a patch which implements this and also makes the states of
options more reco
Richard Stallman wrote:
You've set this %c and Customize saved it in your init file.
That gets rid of the confusion that the user might have set it by hand
in his init file, which was by far the worst of the two possible
confusions. So it is a big improvement over your previous suggestion.
I
You have set this %c and saved it in your init file.
_The_ most important thing one needs to know when trying to save a
previously saved option to a new value or reset it to standard, is
whether it was saved _by Custom_, because that affects whether trying
to save a new value
- Original Message -
From: "Richard Stallman" <[EMAIL PROTECTED]>
> We are talking about:
>
> You have set this %c and saved it through Customize in your init file.
>
> How about
>
> You've set this %c and Customize saved it in your init file.
I would prefer something like
Y
We are talking about:
You have set this %c and saved it through Customize in your init file.
How about
You've set this %c and Customize saved it in your init file.
___
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailma
>From my previous message:
+ Choose the Save operation to save it. Saving an option writes a
+ `custom-set-variables' and a `custom-set-faces' form in your
+ `custom-file' (usually .emacs) if they are not yet present and
+ edits these forms otherwise.
This also would take care of obj
Robert Chassell wrote:
You have set this %c and saved it in your init file.
This wording is correct. In this case, you did not write the code
yourself, but had a library do it.
But nothing in the sentence tells the latter. Therefore, the sentence
is very misleading.
_The_ most imp
That would be very misleading. There are two ways a user can set an
option permanently: through Custom and by writing code in his init
file.
Your statement is confusing. Custom automatically writes code that is
saved in an init file. It is a code generating tool that saves in a
part
We are talking about:
You have set this %c and saved it through Customize in your init file.
Richard Stallman wrote:
So I think the best way to shorten this is to delete "through Customize".
That would be very misleading. There are two ways a user can set an
option permanently: through Cus
You have set this %c and saved it through Customize in your init file.
This is too long. It produces lots of ugly continuation lines.
It also is inaccurate if custom-file is non-nil.
Telling the user the value has been saved in the init file may help
users understand what is going on
15 matches
Mail list logo
