From: Jambunathan K <kjambunathan@gmail.com>
To: Bruce Korb <bkorb@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Project initialization files?
Date: Tue, 17 Jul 2012 23:47:58 +0530 [thread overview]
Message-ID: <81a9yyp7zd.fsf@gmail.com> (raw)
In-Reply-To: <CAKRnqNJgYQ2nqaQzh4hoj+XEj8TNPvmrPgu8Q=VXNYw4d3sW3w@mail.gmail.com> (Bruce Korb's message of "Tue, 17 Jul 2012 10:25:33 -0700")
C-h r
g Directory Variables
or
(info "(emacs) Directory Variables")
> Hi,
>
> I am probably not guessing the correct search term to find prior discussions
> of what I'm interested in, sorry. Anyway, I work on a number of different
> projects and each of them have their own favored way of indenting the code.
> To cope with this, emacs and Vim have mechanisms for automatically
> formatting the code to the preferred formatting style. All you need is a little
> comment like "c-file-style: gnu", for example. Well, the Linux kernel has
> decided to remove these warts, they've never been acceptable at my various
> employers and often they are not incorporated into projects I play around with.
>
> 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...
>
> Suggestions? Thanks! - Bruce
>
>
--
prev parent reply other threads:[~2012-07-17 18:17 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
2012-07-17 18:17 ` Jambunathan K [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=81a9yyp7zd.fsf@gmail.com \
--to=kjambunathan@gmail.com \
--cc=bkorb@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 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).