Re: files.el: Patch to make project-settings optional/customizable

[Chong Yidong]

Tom Tromey <address@hidden> writes:

> Dan> If no, what is the advantage of having this name customizable?  
> Dan> What happens if different projects using different names?
> Dan> It seems that it would just bring in complications...
>
> Yes, this makes the feature less useful, by making it not work
> automatically across projects.

I think it's generally good policy to avoid hardcoding file names.  The
default is unchanged, so the feature still works automatically across
projects unless you change it.  People who care enough about changing
the default presumably know what they are doing (presumably, they want
to have a different file name for some reasons of their own, and this
change lets them do that without redefining the functions).