yes, this is exactly the same behavior i'm seeing [except that my custom file is
not write-protected].
Vin Shelton wrote:
I think this may be the annoyance that Ben was referring to. Every
time I start my XEmacs (21.2 latest CVS), I get prompted to save my
custom file because it happens to be write-protected. This happens
even though my custom file already contains the line:
'(load-home-init-file t t)
which is presumably what the startup code is trying to write to my
custom file.
Michael, let me know if I can help you diagnose this.
- vin
--
Ben
In order to save my hands, I am cutting back on my mail. I also write
as succinctly as possible -- please don't be offended. If you send me
mail, you _will_ get a response, but please be patient, especially for
XEmacs-related mail. If you need an immediate response and it is not
apparent in your message, please say so. Thanks for your understanding.
See also
http://www.666.com/ben/chronic-pain/