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

[Dan Nicolaescu]

Juri Linkov <address@hidden> writes:

  > >   >   > >   > I think it's generally good policy to avoid hardcoding file 
names.
  > >   >   > >
  > >   >   > > But general policy should not be applied without thinking about 
the
  > >   >   > > particulars of each case.  As Tom said, there were some long
  > >   >   > > discussions about this, and I think that the opposite 
conclusion was
  > >   >   > > reached _for this particular case_.  Just undoing that decision
  > >   >   > > without reviewing the previous discussions on this does not 
seem like
  > >   >   > > a good idea.
  > >   >   >
  > >   >   > I can't seem to find the discussion.  Could you point me to it?
  > >   >
  > >   > I don't have anything handy, I'd guess that searching for
  > >   > .dir-settings.el and Tom's name should be good enough.
  > >   >
  > >   >   > (Even if we decide to hardcode the name, which I'm not convinced 
about,
  > >   >   > there needs to be a comment in the code explaining why.)
  > >
  > > Any news about this?
  > 
  > I agree with Juanma that the name .dir-settings.el is "ugly as hell".
  > Perhaps this is the reason why users want to customize it.

You did read the part that showed that as things stand now, if the file
name is changed, the feature completely breaks?