unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Chong Yidong <cyd@stupidchicken.com>
To: emacs-devel@gnu.org
Cc: 2833@emacsbugs.donarmstrong.com
Subject: bug#2833: Re: 23.0.92; Bug in Directory Variables
Date: Tue, 07 Apr 2009 00:32:29 -0400	[thread overview]
Message-ID: <87r605f5ia.fsf__17353.9261603311$1239079564$gmane$org@cyd.mit.edu> (raw)

Could someone please take a stab at bug#2833?  This should not be
difficult, but I have no time for it at the moment.  Basically, one
needs to change dir-locals-read-from-file so that it records the modtime
of each directory variables file, and dir-locals-find-file so that it
checked if the cache is stale and refreshes it if necessary.  (Tom
Tromey, the author of the code, is not responding to email.)






                 reply	other threads:[~2009-04-07  4:32 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='87r605f5ia.fsf__17353.9261603311$1239079564$gmane$org@cyd.mit.edu' \
    --to=cyd@stupidchicken.com \
    --cc=2833@emacsbugs.donarmstrong.com \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).