all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Daniel Hackney <dan@haxney.org>
To: Glenn Morris <rgm@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Interest in "Elisp lint"-like tool?
Date: Wed, 1 Feb 2012 09:46:46 -0500	[thread overview]
Message-ID: <CAMqXDZsROs_we5Gwsk3MPZR6OTn4LqR81tJjE4Letizqg4W=oA@mail.gmail.com> (raw)
In-Reply-To: <j3bopk8r45.fsf@fencepost.gnu.org>

Glenn Morris <rgm@gnu.org> wrote:
> (trivial comments only)
>
> Daniel Hackney wrote:
>
>>   - elLint
>
> A bad name, since elint.el already exists. (See also lisp-mnt.el.)

Ah, I wasn't aware. Again, these are merely random ideas off the top of
my head; I'm sure others could come up with better (read: less cheesy
and less already-taken-y) names.

>> Some of these style choices seem fairly uncontroversial (like making
>> sure `provide' is at the end of the file)
>
> It is not always possible though (to avoid recursive requires is the
> usual reason).

Haha, bad choice of "uncontroversial" example, then! ;)

Looking at the list again, I guess none of them are truly
uncontroversial, but many should be reasonably easy to agree on, like
having ";;; filename.el --- What this file does" as the first line or
"no trailing whitespace."

The broader point is that I think it would be useful to have some
guidelines on these sorts of things beyond what currently exists, and
some way to enforce or "gently suggest" adherence to them.

--
Daniel M. Hackney



  reply	other threads:[~2012-02-01 14:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-30 22:45 Interest in "Elisp lint"-like tool? Daniel Hackney
2012-01-31  3:53 ` Glenn Morris
2012-02-01 14:46   ` Daniel Hackney [this message]
2012-02-02 18:38     ` Stefan Monnier
2012-01-31 10:50 ` Ted Zlatanov

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='CAMqXDZsROs_we5Gwsk3MPZR6OTn4LqR81tJjE4Letizqg4W=oA@mail.gmail.com' \
    --to=dan@haxney.org \
    --cc=emacs-devel@gnu.org \
    --cc=rgm@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.