From: sandipchitale@yahoo.com (Sandip Chitale)
Subject: Is there a mode that helps enforce coding guidelines?
Date: 28 May 2003 10:50:52 -0700 [thread overview]
Message-ID: <b607d812.0305280950.199892c5@posting.google.com> (raw)
In-Reply-To: f0077d93.0305280605.3f2e9e83@posting.google.com
Well, there are some modes like JDEE (for Java) which integrate some external
utilities which check the style e.g. checkstyle. When run the utility emits
compiler error style output in a buffer. The error messages are hyperlinked to
the source. Integration is not exactly the way you asked for but it is useful.
sandip
petter_wintzell@yahoo.com (Petter Wintzell) wrote in message news:<f0077d93.0305280605.3f2e9e83@posting.google.com>...
> Hi,
>
> Is there an Emacs mode that can help a programmer follow a set of
> coding guidelines and style rules? I am thinking of the simple rules
> that exist in many companies and projects regarding line length,
> comment style, indent style, hanging braces, variable names and what
> not.
>
> I would like a mode that highlighted the text when I broke a
> guideline. It would also be nice if the mode could help me correct the
> error.
>
> One thing that would also be nice is if one could switch between
> different rule sets, so that I can easily have one set of rules when
> coding at work, one when coding at home, one when participating in a
> particular open source project, etc.
>
> Is there any such mode or functionality?
>
> Regards,
> /Petter
next prev parent reply other threads:[~2003-05-28 17:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-28 14:05 Is there a mode that helps enforce coding guidelines? Petter Wintzell
2003-05-28 16:27 ` Dan Anderson
2003-05-29 12:44 ` Kevin Dziulko
2003-05-28 16:43 ` Kai Großjohann
2003-05-28 17:03 ` Phillip Lord
2003-05-28 18:29 ` Kai Großjohann
2003-05-29 14:09 ` Phillip Lord
2003-05-28 17:50 ` Sandip Chitale [this message]
2003-05-29 3:38 ` Peter Milliken
2003-06-01 21:45 ` Alan Mackenzie
2003-06-02 10:37 ` Petter Wintzell
2003-06-03 15:58 ` Colin Marquardt
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=b607d812.0305280950.199892c5@posting.google.com \
--to=sandipchitale@yahoo.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 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.