Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm
To: ant-dev@jakarta.apache.org
Subject: Re: -emacs flag ??
References: <NDBBIMHCHMPELMBMMFIMOEJJFDAA.conor@cortexebusiness.com.au>
From: Stefan Bodewig <bodewig@apache.org>
Date: 01 Mar 2001 09:39:34 +0100
In-Reply-To: "Conor MacNeill"'s message of "Thu, 1 Mar 2001 13:43:43 +1100"
Message-ID: <m3pug17uih.fsf@bodewig.bost.de>
Lines: 39
User-Agent: Gnus/5.0807 (Gnus v5.8.7) XEmacs/21.1 (Cuyahoga Valley)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

Conor MacNeill <conor@cortexebusiness.com.au> wrote:

>> From: Peter Donald [mailto:donaldp@apache.org]

>> some editors ? All editors that provide this functionality would be
>> closer to it ;)
> 
> Maybe all editors that you use, but mine has no problems
> whatsoever. I believe you can configure emacs to handle it too.

Sure - I think any editor that can parse error messages of compilers
can be customized to accept additional regexps, otherwise this feature
would be quite limited, wouldn't it.

>> >That information is an advantage to me. It helps me know which
>> >task is failing. How do you find that out?

We agree completely.

>> The question is how useful is that in general? How often can you
>> not tell where the error is coming from?

> When we support multithreading it will be even more important to
> know the source of the error.

Very important point IMHO.

>> I wasn't actually going to bring this issue up to 2.0 though but
>> somehow the issue up and pounced ;) How about we keep it as is in
>> 1.x for backwards compatability but maybe ant2.0 defaults to the
>> standard?
> 
> Nothing is set for 2.0 yet, and everything will be up for
> discussion.

Right, and could we please release Ant 1.3 and then start this
discussion (on Ant2) in a more formal way (I'll post a proposal soon)?

Stefan