From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Kevin Rodgers Newsgroups: gmane.emacs.devel Subject: Re: .dir-locals.el Date: Wed, 07 Jan 2009 20:04:23 -0700 Message-ID: References: <200812271713.mBRHDnU3019200@mothra.ics.uci.edu> <87hc4ak6b9.fsf@gmail.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1231383904 4590 80.91.229.12 (8 Jan 2009 03:05:04 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 8 Jan 2009 03:05:04 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Jan 08 04:06:14 2009 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1LKlDA-0007FM-8d for ged-emacs-devel@m.gmane.org; Thu, 08 Jan 2009 04:05:46 +0100 Original-Received: from localhost ([127.0.0.1]:57530 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LKlBu-0004b6-HV for ged-emacs-devel@m.gmane.org; Wed, 07 Jan 2009 22:04:14 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LKlBq-0004az-Gb for emacs-devel@gnu.org; Wed, 07 Jan 2009 22:04:10 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LKlBp-0004am-Nf for emacs-devel@gnu.org; Wed, 07 Jan 2009 22:04:10 -0500 Original-Received: from [199.232.76.173] (port=56761 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LKlBp-0004aj-Kt for emacs-devel@gnu.org; Wed, 07 Jan 2009 22:04:09 -0500 Original-Received: from main.gmane.org ([80.91.229.2]:51899 helo=ciao.gmane.org) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1LKlBp-0006vB-3G for emacs-devel@gnu.org; Wed, 07 Jan 2009 22:04:09 -0500 Original-Received: from list by ciao.gmane.org with local (Exim 4.43) id 1LKlBk-0000tf-Al for emacs-devel@gnu.org; Thu, 08 Jan 2009 03:04:04 +0000 Original-Received: from c-67-161-145-183.hsd1.co.comcast.net ([67.161.145.183]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 08 Jan 2009 03:04:04 +0000 Original-Received: from kevin.d.rodgers by c-67-161-145-183.hsd1.co.comcast.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 08 Jan 2009 03:04:04 +0000 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 36 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: c-67-161-145-183.hsd1.co.comcast.net User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209) In-Reply-To: <87hc4ak6b9.fsf@gmail.com> X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6, seldom 2.4 (older, 4) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:107703 Archived-At: Eric Schulte wrote: > Is there a good way to apply the variables set in .dir-locals.el when > changing into and out of a directory in eshell (or I suppose in other > Emacs shells as well)? > > I've tried setting eshell as a mode in the .dir-locals.el file but with > no success. I've also tried to define after-advice on the `cd' function > in eshell, but there doesn't appear to be any means for applying local > variables to a buffer which doesn't have a file-name. > > (defadvice cd (after dir-locals-on-cd activate) > "Apply the variables defined in .dir-locals.el when changing > into and outof a directory in eshell." > (hack-dir-local-variables)) > > Fails because `hack-dir-local-variables' checks that the buffer is > visiting a file before applying the variables. > > Is there a supported way to do this? > > If not should I write a new function for this? > > If so should it be included in the dir-locals.el functionality? > > If not is there a reason to only allow setting local variables for > buffers visiting files? I don't know. But you should be able to get your advice to work by let-binding buffer-file-name to default-directory around the call to hack-dir-local-variables. Or perhaps to (expand-file-name "foo"). -- Kevin Rodgers Denver, Colorado, USA