On Wednesday, October 27, 2004 at 22:29:40, Matthieu Moy wrote: [...] > 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?
Yes, this is the way to go, also tla-log-library should be stored there by default. IMHO the current file names do not make it clear that ~/.tla-bookmarks.el and ~/.arch-log-library/ are generated by Xtla, have I missed others?. Better to call them ~/.xtla-bookmarks.el and ~/.xtla-log-library/, much better to put them in ~/.xtla/. > > 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:"). Yes it does, at least for XEmacs. > I'd like to get more arguments (from you and others) before we take > the "decision". One thing I was confused about was a 1-2 sec delay of Xemacs doing garbage-collecting due to loading, processing and saving of the custom file. Which is a big annoying since frequent and fast commits are a nice thing. I wonder if we really need to save the tip-number between sessions. We may also initialize it randomly. Robert
