From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: [ELPA] Package proposal: relint (ex-trawl)
Date: Fri, 22 Mar 2019 17:20:08 +0200 [thread overview]
Message-ID: <83r2azq6l3.fsf@gnu.org> (raw)
In-Reply-To: <jwvtvfvdkij.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Fri, 22 Mar 2019 11:01:43 -0400)
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Date: Fri, 22 Mar 2019 11:01:43 -0400
>
> > My point was that I don't think we should have in our Makefiles
> > targets that require tools which are neither expected to be installed
> > on many systems nor come with the Emacs repository.
>
> What's the harm?
The harm is that it's IME annoying to invoke a target only to be
presented with some error message which at best says some file or
program is missing.
What's the use of having a target that you cannot run?
> And it'll be a lot more convenient than "a small Makefile in the
> package with a lint-emacs-regexps target" since that Makefile would
> be hidden inside ~/.emacs.d/elpa and would have to be told which
> Emacs you want to run and/or which source files you want to check.
Nothing that cannot be solved by an Emacs command, right?
next prev parent reply other threads:[~2019-03-22 15:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-19 13:24 [ELPA] Package proposal: relint (ex-trawl) Mattias Engdegård
2019-03-19 18:05 ` Eli Zaretskii
2019-03-19 20:30 ` Mattias Engdegård
2019-03-19 21:43 ` Stefan Monnier
2019-03-20 5:52 ` Eli Zaretskii
2019-03-20 13:08 ` Stefan Monnier
2019-03-20 13:25 ` Eli Zaretskii
2019-03-21 11:19 ` Mattias Engdegård
2019-03-21 14:26 ` Eli Zaretskii
2019-03-22 14:17 ` Mattias Engdegård
2019-03-22 14:31 ` Stefan Monnier
2019-03-22 14:49 ` Eli Zaretskii
2019-03-22 15:01 ` Stefan Monnier
2019-03-22 15:20 ` Eli Zaretskii [this message]
2019-03-22 15:49 ` Stefan Monnier
2019-03-22 16:12 ` Stefan Monnier
2019-03-22 18:18 ` Stefan Monnier
2019-03-22 18:36 ` T.V Raman
2019-03-23 2:33 ` Richard Stallman
2019-03-26 14:14 ` Mattias Engdegård
2019-03-26 16:00 ` Eli Zaretskii
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=83r2azq6l3.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).