[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: always put Customizations in `custom-file', never in `user-init-file
From: |
Drew Adams |
Subject: |
RE: always put Customizations in `custom-file', never in `user-init-file' |
Date: |
Wed, 12 Dec 2007 08:31:44 -0800 |
> > What happens in XEmacs for saving customizations when the
> > `custom-file' value is a symbol (so no custom file was
> > loaded)? Are settings nevertheless saved to the default
> > custom file?
>
> I don't know; I imagine you get an invalid-state or invalid-argument
> error. The XEmacs design assumes you want to load and save
> customizations, and assumes that `custom-file' will be a string;
> AFAICS it does not deal gracefully with anything else. I'm not
> advocating the XEmacs design here; I'm just saying it works for us.
>
> > If so, I think (until I understand better ;-)) that it would be better
> > to prevent saving customizations until the user redefines
> > `custom-file' to a file name (possibly the default file).
>
> Well, an error wil do that. ;-)
Yes, that's what I was suggesting.
> > if the user's custom file is in a different location and s?he decides
> > not to load it, and then forgets that, then settings get saved to a
> > different custom file (the default), so s?he now has two custom files.
>
> Seems like a YAGNI to me.
Worse than a YAGNI. I wasn't promoting it; I was pointing it out as a
potential problem if you can bypass loading your custom file but then saving
saves silently to the default custom file.
If an error is raised when `custom-file' is a non-nil symbol and you try to
save customizations, then there is no problem.
At any rate, the discussion is moot, now that RMS has decided for the status
quo.
- RE: always put Customizations in `custom-file', never in `user-init-file', (continued)
- RE: always put Customizations in `custom-file', never in `user-init-file', Stephen J. Turnbull, 2007/12/10
- Re: always put Customizations in `custom-file', never in `user-init-file', Lennart Borgman (gmail), 2007/12/10
- Re: always put Customizations in `custom-file', never in `user-init-file', Stephen J. Turnbull, 2007/12/10
- RE: always put Customizations in `custom-file', never in `user-init-file', Drew Adams, 2007/12/11
- RE: always put Customizations in `custom-file', never in `user-init-file', Drew Adams, 2007/12/10
- RE: always put Customizations in `custom-file', never in `user-init-file', Stephen J. Turnbull, 2007/12/10
- RE: always put Customizations in `custom-file', never in `user-init-file', Drew Adams, 2007/12/11
- RE: always put Customizations in `custom-file', never in `user-init-file', Stephen J. Turnbull, 2007/12/11
- RE: always put Customizations in `custom-file', never in `user-init-file', Drew Adams, 2007/12/11
- RE: always put Customizations in `custom-file', never in `user-init-file', Stephen J. Turnbull, 2007/12/12
- RE: always put Customizations in `custom-file', never in `user-init-file',
Drew Adams <=
- Re: always put Customizations in `custom-file', never in `user-init-file', Richard Stallman, 2007/12/11
- RE: always put Customizations in `custom-file', never in `user-init-file', Drew Adams, 2007/12/11
RE: always put Customizations in `custom-file', never in `user-init-file', Drew Adams, 2007/12/10
- Re: always put Customizations in `custom-file', never in `user-init-file', Stefan Monnier, 2007/12/10
- RE: always put Customizations in `custom-file', never in `user-init-file', Drew Adams, 2007/12/11
- Re: always put Customizations in `custom-file', never in `user-init-file', Stefan Monnier, 2007/12/11
- RE: always put Customizations in `custom-file', never in `user-init-file', Drew Adams, 2007/12/11
- Re: always put Customizations in `custom-file', never in `user-init-file', David Kastrup, 2007/12/11
Re: always put Customizations in `custom-file', never in `user-init-file', Jason Rumney, 2007/12/10