Re: local variable for updating the time stamp on save

[Dan Nicolaescu]

"Bruce Korb" <bkorb@gnu.org> writes:

  > On Jan 19, 2008 10:32 AM, Dan Nicolaescu <dann@ics.uci.edu> wrote:
  > 
  > > It's interesting that you get so many duplicates in the list. That might
  > > point to a possible problem in the code that deals with
  > > safe-local-variable-values.
  > 
  > Hi Dan,
  > 
  > s/might/surely/  :)  Likely the reason I found it sub-optimal.  It was 
asking
  > questions redundantly..
  > 
  > Anyway, for my project:
  > 
  > c-file-style
  > indent-tabs-mode

These should work.

  > minor-mode
  > mode

Not sure why you got those

  > ispell-local-pdict
  > sh-basic-offset
  > sh-indentation

I already said these are fixed.

  > c-font-lock-extra-types "JNIEnv" "JNINativeMethod" "JavaVM"

This still needs fixing. Alan can you please mark
c-font-lock-extra-types type to be safe? (not sure what the right
predicate is)

  > compile-command

Should work.

  > folded-file

Does not exist in emacs. 

  > indent-tabs-mode
  > mode
  > sh-indentation
  > tcl-indent-level
  > time-stamp-end
  > time-stamp-format
  > time-stamp-start

Should work. 


  > and for autotools:
  > 
  > coding

Don't know about this one.

  > cperl-brace-offset
  > cperl-continued-brace-offset
  > cperl-continued-statement-offset
  > cperl-extra-newline-before-brace
  > cperl-indent-level
  > cperl-label-offset
  > cperl-merge-trailing-else
  > fill-column
  > indent-tabs-mode
  > ispell-local-dictionary
  > ispell-local-pdict
  > mode
  > perl-brace-imaginary-offset
  > perl-brace-offset
  > perl-continued-brace-offset
  > perl-continued-statement-offset
  > perl-indent-level
  > perl-label-offset
  > sh-indentation
  > time-stamp-end
  > time-stamp-format
  > time-stamp-start
  > whitespace-check-buffer-indent

Should work.


  > And remember that is _will_ be a few years before I see your Emacs fixes.
  > Distros don't pick up and propagate new versions straight away and I don't
  > upgrade my workstation distributions very often.  Takes a _lot_ of work!!

Well, there's not much we can do about that. We can't offer to fix
issues in the past. The GNU Time Machine project it a bit behind
schedule (or ahead?).