emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@gnu.org>
To: Achim Gratz <Stromeko@nexgo.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: Org Build System (aka Makefile)
Date: Wed, 15 Aug 2012 00:45:13 +0200	[thread overview]
Message-ID: <87r4r9xfd2.fsf@gnu.org> (raw)
In-Reply-To: <877gt2oami.fsf@Rainer.invalid> (Achim Gratz's message of "Mon, 13 Aug 2012 21:27:49 +0200")

Hi Achim,

I reverted the commits introducing the _COMPILE_ variable and the elint
targets in the makefile.

I'm with Eric on thinking that even the casual developer should not have
to tweak his local.mk to run the equivalent of `make compile-single', as
it is directly useful to get some warnings.  Even further: if a user
reports a bug and we want to give him directions to get more information
on his environment, asking him to run `make compile-single' is simple.

As for elint, your last email shows this is still largely experimental 
and I doubt many developers use it to get useful warnings.  Maybe `make
elint' would be useful at some point, but for now developers can simply
do M-x elint-current-buffer RET if they want.

I also reduced the number of targets displayed by `make targets': only
the ones that may be directly useful to the user or the developers are
shown.  You were right on this -- I first needed all doc to be able to 
follow your development myself...

I hope you'll understand the choices above.

Best,

-- 
 Bastien

  parent reply	other threads:[~2012-08-14 22:44 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-15 20:37 Org Build System (aka Makefile) Achim Gratz
2012-07-15 21:38 ` Bastien
2012-08-09 17:03 ` Achim Gratz
2012-08-10  7:17   ` Bastien
2012-08-12 13:56     ` Achim Gratz
2012-08-12 18:56       ` Eric Schulte
2012-08-12 20:41         ` Achim Gratz
2012-08-13 13:16           ` Eric Schulte
2012-08-13 13:45             ` Bastien
2012-08-13 19:27               ` Achim Gratz
2012-08-13 22:43                 ` Eric Schulte
2012-08-14  6:13                   ` Achim Gratz
2012-08-14 12:46                     ` Eric Schulte
2012-08-14 22:06                     ` Bastien
2012-08-15 16:35                       ` Achim Gratz
2012-08-14 22:45                 ` Bastien [this message]
2012-08-15 17:55                   ` Achim Gratz
2012-08-15 18:56                     ` Bastien
2012-08-13 19:47             ` Achim Gratz
2012-08-14 22:07               ` Bastien
2012-08-12 22:27       ` Bastien
2012-08-13  6:11         ` Achim Gratz
2012-08-13  7:40           ` Bastien
2012-08-13 11:42             ` Achim Gratz
2012-08-13 13:13               ` Bastien
2012-08-13 14:17                 ` Achim Gratz
2012-08-13 14:48                   ` Bastien
2012-08-13 18:56                     ` Achim Gratz
2012-08-13  5:34       ` Bastien
2012-08-12 16:58     ` Samuel Wales

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.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87r4r9xfd2.fsf@gnu.org \
    --to=bzg@gnu.org \
    --cc=Stromeko@nexgo.de \
    --cc=emacs-orgmode@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/org-mode.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).