On Tue, Jun 01, 2010 at 07:55:09PM +0100, Andy Koppe wrote:
>Lowell Anderson wrote:
>> May I express my sincere appreciation and a big THANK YOU to Andy and
>> everyone else involved for your hard work and dedication in providing
>> mintty.
>
>Thanks, my pleasure. Bit embarrassed, because I'm getti
Lowell Anderson wrote:
> May I express my sincere appreciation and a big THANK YOU to Andy and
> everyone else involved for your hard work and dedication in providing
> mintty.
Thanks, my pleasure. Bit embarrassed, because I'm getting more than my
fair share of positive feedback here due to mintty
Andy Koppe wrote:
On 31 May 2010 22:40, L Anderson wrote:
I really like mintty. However, even though it has the option to 'copy on
select' it requires a right click and paste to insert selected text into the
window.
Middle-click pastes by default, and you can change the right-click
action to
On Mon, May 31, 2010 at 6:47 PM, Christopher Faylor wrote:
(in response to Andy Koppe)
>
> Thanks, as always, for your amazing support of mintty. I wonder if it's
> time to just make it the default for the cygwin terminal, knowing that
> some windows apps won't work quite right. We seem to get en
On 31 May 2010 22:40, L Anderson wrote:
> I really like mintty. However, even though it has the option to 'copy on
> select' it requires a right click and paste to insert selected text into the
> window.
Middle-click pastes by default, and you can change the right-click
action to paste on the Mou
Andy Koppe wrote:
On 31 May 2010 17:47, Christopher Faylor wrote:
I don't remember responding to the original message so, if I didn't, I
apologize.
No worries.
Thanks, as always, for your amazing support of mintty. I wonder if it's
time to just make it the default for the cygwin terminal, k
On 31 May 2010 17:47, Christopher Faylor wrote:
> I don't remember responding to the original message so, if I didn't, I
> apologize.
No worries.
> Thanks, as always, for your amazing support of mintty. I wonder if it's
> time to just make it the default for the cygwin terminal, knowing that
> s
On Mon, May 31, 2010 at 12:39:30PM +0100, Andy Koppe wrote:
>On 9 March 2010 21:50, Andy Koppe wrote:
>> Cesar Crusius:
>>> I am using Cygwin and SSH to do automated remote builds using Visual
>>> C++. It works for a few days, but invariably things start failing with
>>> messages like these (this o
On 9 March 2010 21:50, Andy Koppe wrote:
> Cesar Crusius:
>> I am using Cygwin and SSH to do automated remote builds using Visual
>> C++. It works for a few days, but invariably things start failing with
>> messages like these (this one from a build log):
>>
>> Makefile:9: MakePID: 5964
>> 1 [
On Tue, Mar 09, 2010 at 08:50:38PM +, Andy Koppe wrote:
> Cesar Crusius:
> > I am using Cygwin and SSH to do automated remote builds using Visual
> > C++. It works for a few days, but invariably things start failing with
> > messages like these (this one from a build log):
> >
> > Makefile:9: M
On Tue, Mar 09, 2010 at 08:50:38PM +, Andy Koppe wrote:
> Cesar Crusius:
> > I am using Cygwin and SSH to do automated remote builds using Visual
> > C++. It works for a few days, but invariably things start failing with
> > messages like these (this one from a build log):
> >
> > Makefile:9: M
Cesar Crusius:
> I am using Cygwin and SSH to do automated remote builds using Visual
> C++. It works for a few days, but invariably things start failing with
> messages like these (this one from a build log):
>
> Makefile:9: MakePID: 5964
> 1 [main] env 2748 C:\cygwin\bin\env.exe: *** fatal e
Hi all,
I am using Cygwin and SSH to do automated remote builds using Visual
C++. It works for a few days, but invariably things start failing with
messages like these (this one from a build log):
Makefile:9: MakePID: 5964
1 [main] env 2748 C:\cygwin\bin\env.exe: *** fatal error - can't cre
13 matches
Mail list logo
