From: Dan Nicolaescu <dann@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Bruce Korb <bkorb@gnu.org>, emacs-devel@gnu.org
Subject: Re: Project initialization files?
Date: Tue, 17 Jul 2012 17:12:23 -0400 [thread overview]
Message-ID: <yxqhat6hz2g.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <83fw8q9t9c.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 17 Jul 2012 20:45:03 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Bruce Korb <bkorb@gnu.org>
>> Date: Tue, 17 Jul 2012 10:25:33 -0700
>>
>> What to do? It seems to me there ought to be some way of saying, "C files
>> in this tree are gnu-style, that tree is Stroustrup and over there use
>> the linux-kernel's favored style. I think it boils down to this question:
>>
>> How hard would it be to set up a personal registry of projects
>> (~/emacs.d/projects)
>> that specified the c-file-style for all .c/.h files in a tree? So if
>> I edit files in
>> ~/my-day-job, I use the "work" style, etc.
>>
>> Does such a thing already exist? EDE isn't quite it and it requires a special
>> file added to the source code to boot. But what I'd like to find ought to be
>> able to pilfer some of that code...
>
> Is the .dir-locals.el feature (described in the "Specifying File
> Variables" node of the Emacs manual) fit the bill? If not, why not?
What this points out is that we haven't made much effort to spread the
knowledge about .dir-locals.el.
GNU projects like GCC/gdb/binutils/etc could incorporate customized
versions of .dir-locals.el (the one in emacs can be used as a starting
point)...
next prev parent reply other threads:[~2012-07-17 21:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-17 17:25 Project initialization files? Bruce Korb
2012-07-17 17:45 ` Eli Zaretskii
2012-07-17 20:25 ` Bruce Korb
2012-07-21 22:06 ` Nix
2012-07-17 21:12 ` Dan Nicolaescu [this message]
2012-07-17 18:17 ` Jambunathan K
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=yxqhat6hz2g.fsf@fencepost.gnu.org \
--to=dann@gnu.org \
--cc=bkorb@gnu.org \
--cc=eliz@gnu.org \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.