I like it. I think it makes good sense. And while you're at it, why not
go ahead and extend that params idea to targets too?
Gary McCullough
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Ian MacLean
Sent: Friday,
This actually breaks things also. We run Nant from within Visual Studio
to do our builds. With the old way, VS.NET new how understand the
errors from CSC and you could double click on them and VS would jump to
the right spot for the error. This no longer works with the prefix in
place. Can we
Erv,
You can use the -emacs command line option to accomplish this.
Gert
- Original Message -
From: Erv Walter [EMAIL PROTECTED]
To: Ian MacLean [EMAIL PROTECTED]; Nant-Developers (E-Mail)
[EMAIL PROTECTED]
Sent: Wednesday, August 25, 2004 10:24 PM
Subject: RE: [nant-dev] Console logging
Cool, thanks!
-Original Message-
From: Gert Driesen [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 25, 2004 3:56 PM
To: Erv Walter; Nant-Developers (E-Mail)
Subject: Re: [nant-dev] Console logging output
Erv,
You can use the -emacs command line option to accomplish this.
Gert
Ive tried .84, .85 nightly, and cvs head, none of
them build on MacOS X mono 1.1.1. Anybody have ideas? For one thing it
appears to be targeting mono-2.0 which I dont get. I also dont
get why its looking in 1.0.1 and not 1.1.1, which is current.
The errors on the nightly are:
mono
