From: Kevin Rodgers <kevinr@ihs.com>
Subject: Re: a little .emacs, like .htaccess, for subdirectories
Date: Wed, 10 Apr 2002 10:28:32 -0600 [thread overview]
Message-ID: <3CB46830.27916B8D@ihs.com> (raw)
In-Reply-To: m2y9fv508n.fsf@jidanni.org
Dan Jacobson wrote:
>
> Well, Apache has .htaccess files for each directory tree, etc. Any
> way to get a already running emacs to know that I want certain options
> in effect when I am in this directory, and other options in effect
> when I am in that directory? Sure there are local file variables, but
> that is only for one file.
Does http://www.lickey.com/env/elisp/dirvars.el do what you want?
> And what about a *compilation* buffer? I don't think you are going to
> get any local variables in there.
>
> Currently my .emacs does
> (add-hook 'compilation-mode-hook
> (function (lambda ()
> (toggle-read-only 1);else I often edit it because it
> ;looks like my makefile
> (toggle-truncate-lines); few docs for this
> (define-key compilation-mode-map "q" 'quit-window))))
>
> I was hoping to have toggle-truncate-lines be in effect in some
> directories only. Must I make some big conditional deal right there
> in the hook, having to list which directories I want this on in... or
> can I one day maybe have a "little .emacs", say read by emacs the
> first time it visits a file in a directory, with items only
> applicable to files in that directory... and if I change the little
> emacs, I would tell emacs to re digest it, unless I have autochecking on...
I think the tricky thing is that the *compilation* buffer is a process
buffer that's not visiting a file. Perhaps the
dirvars-hack-local-variables-hook function could be added to
compilation-mode-hook...
--
Kevin Rodgers <kevinr@ihs.com>
prev parent reply other threads:[~2002-04-10 16:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-10 10:14 a little .emacs, like .htaccess, for subdirectories Dan Jacobson
2002-04-10 16:28 ` Kevin Rodgers [this message]
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=3CB46830.27916B8D@ihs.com \
--to=kevinr@ihs.com \
/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).