Dan Lipsitt <[EMAIL PROTECTED]> writes:
> In my opinion, tla-tips-number shouldn't be stored using customize.
> There are several reasons:
>
> 1) I keep my .emacs file in RCS, and therefore it is often locked.
I recommend you to store customize configuration outside ~/.emacs.el:
;; Customize file
(setq custom-file (expand-file-name "~/.emacs-customize"))
(load custom-file)
[ This doesn't solve your problem with RCS if you want to manage
.emacs-customize with RCS too, but you should do it anyway ;-) ]
Note that recent versions of XTLA protect the call to
`customize-save-variable' with a `condition-case', so, if the file in
which you store your customization is locked, the tip number won't be
stored, but you also won't get any error.
> 2) If I have compiled my .emacs. the tip number will be overridden by
> the one in .emacs.elc
This is not an argument because this would be valid also for
hand-edited or customize-generated config as well. It's your
responsibility to make sure your .emacs.el is loaded properly.
> 3) It seems to me that customize is meant for user-initiated
> configuration. It probably shouldn't be used to store program state.
XTLA is not the only Emacs program to do that. I have several
variables in my .emacs-customize that I never set manually (Gnus'
`canlock-password', `ecb-options-version', `global-semantic-*', ...)
Well, I don't know what to do here:
I understand the problem with RCS, and I admit I don't like programs
to touch my configuration without asking me.
On the other hand, I hate programs creating a bunch of hidden files in
the root of my home dir.
$ ls -1d .?* | wc -l
231
$ _
With your proposal, I would get 232 :-(
Currently, the tip number is the only "state" information about xtla I
can think about. If we get other similar cases, yes, that would be
worth a ~/.xtla-state.el.
Or perhaps a ~/.xtla/state.el, that would allow to store bookmarks in
~/.xtla/bookmarks.el, leaving room for a ~/.xtla/whatever.el?
> Under Unix, it could be stored somewhere like ~/.xtla-tip-num. I'm not
> sure about windows.
`expand-file-name' also manages ~ under windows, AFAIK. (Will be
something like (or (getenv "HOME") "C:").
I'd like to get more arguments (from you and others) before we take
the "decision".
Thanks for the remark anyway.
--
Matthieu
BTW, may I ask you why you use RCS instead of Arch to manage your
.emacs ? ;-)
