On Wed, Mar 01, 2006 at 12:32:01PM -0700, Paul wrote:
>I'm also happy I joined the list in time to see the post about
>CYGWIN=error_start! I've been cussing about cygwin's lack of useful core
> file for ages (i.e., I can't do gdb core and then bt to see a stack
>trace with symbols and parameters
I upgraded to 1.5.19-4 yesterday and now notice the following new,
undesirable behavior: empty console windows for child make processes.
I use the FTE editor and run make from it, the make output being
displayed inside an FTE window. Before upgrading to 1.5.19-4, no
console windows popped up, ev
On 01 March 2006 15:41, Christopher Faylor wrote:
> On Wed, Mar 01, 2006 at 12:03:20PM -, Dave Korn wrote:
>> On 28 February 2006 19:54, Paul Hepworth wrote:
>>> I upgraded to 1.5.19-4 yesterday and now notice the following new,
>>> undesirable behavior: empty console windows for child make pr
On Wed, Mar 01, 2006 at 12:03:20PM -, Dave Korn wrote:
>On 28 February 2006 19:54, Paul Hepworth wrote:
>>I upgraded to 1.5.19-4 yesterday and now notice the following new,
>>undesirable behavior: empty console windows for child make processes.
>>
>>I use the FTE editor and run make from it, th
On 28 February 2006 19:54, Paul Hepworth wrote:
> I upgraded to 1.5.19-4 yesterday and now notice the following new,
> undesirable behavior: empty console windows for child make processes.
>
> I use the FTE editor and run make from it, the make output being
> displayed inside an FTE window. Befor
I upgraded to 1.5.19-4 yesterday and now notice the following new,
undesirable behavior: empty console windows for child make processes.
I use the FTE editor and run make from it, the make output being
displayed inside an FTE window. Before upgrading to 1.5.19-4, no console
windows popped up, eve
6 matches
Mail list logo
