I was having trouble getting something to compile a while ago and it turned out that the problem was there was a sc.ini sitting in the dir I was working in. I was playing with settings so I expected something like this but the -v flag didn't give me anything useful. It would be nice to have the -v flag (or a -vv flag) given the full effective command line as gathered from all over the place and where the args come from.

On Thu, 30 Aug 2007 21:33:47 +0000 (UTC), BCS wrote:

> I was having trouble getting something to compile a while ago and it turned out that the problem was there was a sc.ini sitting in the dir I was working in. I was playing with settings so I expected something like this but the -v flag didn't give me anything useful. It would be nice to have the -v flag (or a -vv flag) given the full effective command line as gathered from all over the place and where the args come from.

BTW, 'Bud' does this with the -V switch.

-- 
Derek Parnell
Melbourne, Australia
skype: derek.j.parnell

Reply to Derek,

> On Thu, 30 Aug 2007 21:33:47 +0000 (UTC), BCS wrote:
> 
>> I was having trouble getting something to compile a while ago and it
>> turned out that the problem was there was a sc.ini sitting in the dir
>> I was working in. I was playing with settings so I expected something
>> like this but the -v flag didn't give me anything useful. It would be
>> nice to have the -v flag (or a -vv flag) given the full effective
>> command line as gathered from all over the place and where the args
>> come from.
>> 
> BTW, 'Bud' does this with the -V switch.
> 

Just for BUD's args or does it figure out what DMD will be fed?

On Thu, 30 Aug 2007 22:14:18 +0000 (UTC), BCS wrote:

> Reply to Derek,
> 
>> On Thu, 30 Aug 2007 21:33:47 +0000 (UTC), BCS wrote:
>> 
>>> I was having trouble getting something to compile a while ago and it turned out that the problem was there was a sc.ini sitting in the dir I was working in. I was playing with settings so I expected something like this but the -v flag didn't give me anything useful. It would be nice to have the -v flag (or a -vv flag) given the full effective command line as gathered from all over the place and where the args come from.
>>> 
>> BTW, 'Bud' does this with the -V switch.
>> 
> 
> Just for BUD's args or does it figure out what DMD will be fed?

Everything. In fact, it might be a little too verbose for some people.

-- 
Derek Parnell
Melbourne, Australia
skype: derek.j.parnell

Reply to Derek,

> On Thu, 30 Aug 2007 22:14:18 +0000 (UTC), BCS wrote:
> 
>> Reply to Derek,
>> 
>>> On Thu, 30 Aug 2007 21:33:47 +0000 (UTC), BCS wrote:
>>> 
>>>> I was having trouble getting something to compile a while ago and
>>>> it turned out that the problem was there was a sc.ini sitting in
>>>> the dir I was working in. I was playing with settings so I expected
>>>> something like this but the -v flag didn't give me anything useful.
>>>> It would be nice to have the -v flag (or a -vv flag) given the full
>>>> effective command line as gathered from all over the place and
>>>> where the args come from.
>>>> 
>>> BTW, 'Bud' does this with the -V switch.
>>> 
>> Just for BUD's args or does it figure out what DMD will be fed?
>> 
> Everything. In fact, it might be a little too verbose for some people.
> 

I work with 400K trace logs for fun, their is no sutch thing as "a little too verbose". <G>