On 1/8/2012 4:45 PM, Lars Bjørndal wrote:
Hi
[Corinna Vinschen]
On Dec 11 21:32, Samuel Thibault wrote:
Corinna Vinschen, le Thu 08 Dec 2011 09:47:45 +0100, a écrit :
Too bad. In that case, Samuel, can you please have a closer look to
see what broke brltty?
The switch to mintty, simply. B
Hi
[Corinna Vinschen]
> On Dec 11 21:32, Samuel Thibault wrote:
>> Corinna Vinschen, le Thu 08 Dec 2011 09:47:45 +0100, a écrit :
>> > Too bad. In that case, Samuel, can you please have a closer look to
>> > see what broke brltty?
>>
>> The switch to mintty, simply. Brltty uses ReadConsoleOutpu
On Dec 23 11:18, Shaddy Baddah wrote:
> Hi Corinna,
>
>
> On 23/12/11 02:40, Corinna Vinschen wrote:
> > On Dec 23 01:47, Shaddy Baddah wrote:
> >> On 23/12/11 01:33, Corinna Vinschen wrote:
> >>> Other than that I might have a solution. I applied a patch which only
> >>> adds the CREATE_BREAKAW
Hi Corinna,
On 23/12/11 11:18, Shaddy Baddah wrote:
> On 23/12/11 02:40, Corinna Vinschen wrote:
>> On Dec 23 01:47, Shaddy Baddah wrote:
>>> On 23/12/11 01:33, Corinna Vinschen wrote:
Other than that I might have a solution. I applied a patch which only
adds the CREATE_BREAKAWAY_FROM_J
Hi Corinna,
On 23/12/11 02:40, Corinna Vinschen wrote:
> On Dec 23 01:47, Shaddy Baddah wrote:
>> On 23/12/11 01:33, Corinna Vinschen wrote:
>>> Other than that I might have a solution. I applied a patch which only
>>> adds the CREATE_BREAKAWAY_FROM_JOB flag if the calling process is member
>>>
On Thu, Dec 22, 2011 at 01:43:03PM -0500, Buchbinder, Barry (NIH/NIAID) [E]
wrote:
>Shaddy Baddah sent the following at Thursday, December 22, 2011 5:12 AM
>>At this point, I should make a disclosure. To do this as a
>>non-Administrator grouped user, I must rename setup.exe to cygpkg.exe.
>>This d
Shaddy Baddah sent the following at Thursday, December 22, 2011 5:12 AM
>At this point, I should make a disclosure. To do this as a
>non-Administrator grouped user, I must rename setup.exe to cygpkg.exe.
>This defeats the later Windows releases abilities to automatically
>detect installer applicati
On Dec 23 01:47, Shaddy Baddah wrote:
> On 23/12/11 01:33, Corinna Vinschen wrote:
> > Other than that I might have a solution. I applied a patch which only
> > adds the CREATE_BREAKAWAY_FROM_JOB flag if the calling process is member
> > of a job and the job allows a breakaway. It works in my lim
On 23/12/11 01:33, Corinna Vinschen wrote:
> On Dec 23 00:07, Shaddy Baddah wrote:
>> On 22/12/11 22:19, Corinna Vinschen wrote:
>>> On Dec 22 22:11, Shaddy Baddah wrote:
69 126706 [main] sh 3824 build_env: envp 0x61266AB4, envc 47
37 126743 [main] sh 3824 child_info::child_info:
On Dec 23 00:07, Shaddy Baddah wrote:
> On 22/12/11 22:19, Corinna Vinschen wrote:
> > On Dec 22 22:11, Shaddy Baddah wrote:
> >>69 126706 [main] sh 3824 build_env: envp 0x61266AB4, envc 47
> >>37 126743 [main] sh 3824 child_info::child_info: subproc_ready 0x234
> >> 589 127332 [main]
Hi Corinna,
On 22/12/11 22:19, Corinna Vinschen wrote:
> On Dec 22 22:11, Shaddy Baddah wrote:
>> On 22/12/11 21:44, Corinna Vinschen wrote:
>>> Does it really work if you replace the DLL with 1.7.9 again? If so,
>>> you could try to find out which snapshot introduced the problem for you.
>>>
>>>
On Dec 22 22:11, Shaddy Baddah wrote:
> On 22/12/11 21:44, Corinna Vinschen wrote:
> > Does it really work if you replace the DLL with 1.7.9 again? If so,
> > you could try to find out which snapshot introduced the problem for you.
> >
> > Also, you could start the whole thing from strace to see w
Hi Corinna,
On 22/12/11 21:44, Corinna Vinschen wrote:
> On Dec 22 21:12, Shaddy Baddah wrote:
>> On 22/12/11 20:25, Corinna Vinschen wrote:
>>> On Dec 22 18:09, Shaddy Baddah wrote:
On 06/12/11 20:37, Corinna Vinschen wrote:
> A lot of changes and fixes have been made in Cygwin since 1.7
On Dec 22 21:12, Shaddy Baddah wrote:
> On 22/12/11 20:25, Corinna Vinschen wrote:
> > On Dec 22 18:09, Shaddy Baddah wrote:
> >> On 06/12/11 20:37, Corinna Vinschen wrote:
> >>> A lot of changes and fixes have been made in Cygwin since 1.7.9 has
> >>> been released, so we're looking forward to rel
Hi Corinna,
On 22/12/11 20:25, Corinna Vinschen wrote:
> On Dec 22 18:09, Shaddy Baddah wrote:
>> Hi,
>>
>> On 06/12/11 20:37, Corinna Vinschen wrote:
>>> A lot of changes and fixes have been made in Cygwin since 1.7.9 has
>>> been released, so we're looking forward to release Cygwin 1.7.10 soon.
On Dec 22 18:09, Shaddy Baddah wrote:
> Hi,
>
> On 06/12/11 20:37, Corinna Vinschen wrote:
> > A lot of changes and fixes have been made in Cygwin since 1.7.9 has
> > been released, so we're looking forward to release Cygwin 1.7.10 soon.
> >
> > Please test the latest developer snapshots at http:/
Hi,
On 06/12/11 20:37, Corinna Vinschen wrote:
> A lot of changes and fixes have been made in Cygwin since 1.7.9 has
> been released, so we're looking forward to release Cygwin 1.7.10 soon.
>
> Please test the latest developer snapshots at http://cygwin.com/snapshots/
> which should have "Release
Corinna Vinschen wrote:
>On Dec 9 12:58, Bengt Larsson wrote:
>> Christopher Faylor wrote:
>> >On Thu, Dec 08, 2011 at 11:00:11PM +0100, Bengt Larsson wrote:
>> >>Christopher Faylor wrote:
>> >>>On Thu, Dec 08, 2011 at 05:06:21PM +0100, Bengt Larsson wrote:
>> With the DLL from 20111208, a bug
On Dec 9 12:58, Bengt Larsson wrote:
> Christopher Faylor wrote:
> >On Thu, Dec 08, 2011 at 11:00:11PM +0100, Bengt Larsson wrote:
> >>Christopher Faylor wrote:
> >>>On Thu, Dec 08, 2011 at 05:06:21PM +0100, Bengt Larsson wrote:
> With the DLL from 20111208, a bug seems to have returned:
> >>>
On Sat, Dec 10, 2011 at 11:34 PM, Christopher Faylor wrote:
> The hanging problem should be fixed in recent snapshots.
I can confirm this in the 12/12 and 12/13 snapshots - thanks!
Cygwin-X is working fine again without any hangs.
--
Jim Reisert AD1C, , http://www.ad1c.us
--
Problem reports:
On Dec 12 23:07, Enrico Forestieri wrote:
> Corinna Vinschen writes:
> >
> > Would it be ok if it works the old way (WIN_A uses the Cygwin codeset)
> > for applications built under 1.7.9 and earlier, and the new way (WIN_A
> > uses Win32 ANSI/OEM codepage) for applications built under 1.7.10 and
>
Corinna Vinschen writes:
>
> Would it be ok if it works the old way (WIN_A uses the Cygwin codeset)
> for applications built under 1.7.9 and earlier, and the new way (WIN_A
> uses Win32 ANSI/OEM codepage) for applications built under 1.7.10 and
> later? That means the current lyx continues to wor
On Dec 8 14:31, Enrico Forestieri wrote:
> Enrico Forestieri writes:
> >
> > However, I experimented a bit with the last snapshot, and even using Greek
> > or Japanese characters in file names, lyx seems to be working fine.
>
> Sorry, it was a cursory test. Actually, cygwin_conv_path is only cal
On Dec 11 21:32, Samuel Thibault wrote:
> Corinna Vinschen, le Thu 08 Dec 2011 09:47:45 +0100, a écrit :
> > Too bad. In that case, Samuel, can you please have a closer look to
> > see what broke brltty?
>
> The switch to mintty, simply. Brltty uses ReadConsoleOutputCharacter()
> to get the text
On Sun, Dec 11, 2011 at 08:10:15PM -0500, Christopher Faylor wrote:
>On Sun, Dec 11, 2011 at 02:59:49PM -0600, Yaakov (Cygwin/X) wrote:
>>On Sun, 2011-12-11 at 01:34 -0500, Christopher Faylor wrote:
>>> The hanging problem should be fixed in recent snapshots.
>>
>>Unfortunately not for automoc4. :-
On Sun, Dec 11, 2011 at 02:59:49PM -0600, Yaakov (Cygwin/X) wrote:
>On Sun, 2011-12-11 at 01:34 -0500, Christopher Faylor wrote:
>> The hanging problem should be fixed in recent snapshots.
>
>Unfortunately not for automoc4. :-(
How do you duplicate your problem?
bash-4.1$ automoc4
bash: autom
On Sun, Dec 11, 2011 at 09:32:39PM +0100, Samuel Thibault wrote:
>Corinna Vinschen, le Thu 08 Dec 2011 09:47:45 +0100, a ?crit :
>> Too bad. In that case, Samuel, can you please have a closer look to
>> see what broke brltty?
>
>The switch to mintty, simply. Brltty uses ReadConsoleOutputCharacter(
Corinna Vinschen, le Thu 08 Dec 2011 09:47:45 +0100, a écrit :
> Too bad. In that case, Samuel, can you please have a closer look to
> see what broke brltty?
The switch to mintty, simply. Brltty uses ReadConsoleOutputCharacter()
to get the text from consoles, I bet mintty does not implement this.
On Sun, 2011-12-11 at 01:34 -0500, Christopher Faylor wrote:
> The hanging problem should be fixed in recent snapshots.
Unfortunately not for automoc4. :-(
Yaakov
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: htt
On Sun, Dec 11, 2011 at 08:07:12AM +0100, marco atzeri wrote:
>On 12/11/2011 7:34 AM, Christopher Faylor wrote:
>
>>> The issue is still present from 2029 to current CVS (fith select).
>>> Any clue ?
>>
>> The hanging problem should be fixed in recent snapshots.
>
>it was fixed on yesterday CVS
On 12/11/2011 7:34 AM, Christopher Faylor wrote:
The issue is still present from 2029 to current CVS (fith select).
Any clue ?
The hanging problem should be fixed in recent snapshots.
cgf
it was fixed on yesterday CVS
Thanks
Marco
--
Problem reports: http://cygwin.com/problems
On Fri, Dec 09, 2011 at 07:14:13AM +0100, marco atzeri wrote:
>On 12/7/2011 8:56 AM, marco atzeri wrote:
>> For the spinning problem I put the test case here:
>>
>> http://matzeri.altervista.org/works/test_case/prova2.tar.bz2
>>
>> running ./system_test.sh
>> some of the tests should dump and retu
Christopher Faylor wrote:
>On Thu, Dec 08, 2011 at 11:00:11PM +0100, Bengt Larsson wrote:
>>Christopher Faylor wrote:
>>>On Thu, Dec 08, 2011 at 05:06:21PM +0100, Bengt Larsson wrote:
With the DLL from 20111208, a bug seems to have returned:
Wildcard match fail from a windows shell wit
On Wed, 2011-12-07 at 12:18 +0100, Corinna Vinschen wrote:
> On Dec 7 04:33, Yaakov (Cygwin/X) wrote:
> > On Tue, 2011-12-06 at 22:08 -0500, Christopher Faylor wrote:
> > > On Tue, Dec 06, 2011 at 06:45:35PM +0100, Corinna Vinschen wrote:
> > > >On Dec 6 15:39, marco atzeri wrote:
> > > >> On 12/
On 12/7/2011 8:56 AM, marco atzeri wrote:
For the spinning problem I put the test case here:
http://matzeri.altervista.org/works/test_case/prova2.tar.bz2
running ./system_test.sh
some of the tests should dump and return.
++ ./xprobe_3dnow.exe
./system_test.sh: line 14: 3256 Illegal instructi
On Thu, Dec 08, 2011 at 11:00:11PM +0100, Bengt Larsson wrote:
>Christopher Faylor wrote:
>>On Thu, Dec 08, 2011 at 05:06:21PM +0100, Bengt Larsson wrote:
>>>With the DLL from 20111208, a bug seems to have returned:
>>>
>>>Wildcard match fail from a windows shell with non-ASCII characters
>>>
>>>ht
Christopher Faylor wrote:
>On Thu, Dec 08, 2011 at 05:06:21PM +0100, Bengt Larsson wrote:
>>With the DLL from 20111208, a bug seems to have returned:
>>
>>Wildcard match fail from a windows shell with non-ASCII characters
>>
>>http://cygwin.com/ml/cygwin/2009-12/msg01079.html
>
>PLEASE be precise w
On Thu, Dec 08, 2011 at 05:06:21PM +0100, Bengt Larsson wrote:
>With the DLL from 20111208, a bug seems to have returned:
>
>Wildcard match fail from a windows shell with non-ASCII characters
>
>http://cygwin.com/ml/cygwin/2009-12/msg01079.html
PLEASE be precise when reporting problems. Returned
Ken Brown writes:
>
> On 12/8/2011 10:56 AM, Enrico Forestieri wrote:
[...]
> > Until recently, the only Cygwin TeX engine was teTeX, which does not
> > support XeTeX. If you wanted a Cygwin version of lyx, you could not
> > have used XeTeX, unless you used MikTeX, for example.
>
> That changed a
On 12/8/2011 10:56 AM, Enrico Forestieri wrote:
Ken Brown writes:
I don't use lyx (though I use tex extensively), so maybe there's
something I don't understand. But is it really necessary for Cygwin's
lyx to support a native Windows tex?
Necessary? No. Useful? Yes.
Wouldn't it be more reas
With the DLL from 20111208, a bug seems to have returned:
Wildcard match fail from a windows shell with non-ASCII characters
http://cygwin.com/ml/cygwin/2009-12/msg01079.html
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation:
Ken Brown writes:
>
> I don't use lyx (though I use tex extensively), so maybe there's
> something I don't understand. But is it really necessary for Cygwin's
> lyx to support a native Windows tex?
Necessary? No. Useful? Yes.
> Wouldn't it be more reasonable for
> users of a native Windows t
On 12/8/2011 9:48 AM, Enrico Forestieri wrote:
Andy Koppe writes:
On 8 December 2011 00:33, Enrico Forestieri wrote:
Corinna Vinschen writes:
Just so it's clear why I did that, maybe you want to have a look into
the brief discussion on the cygwin-developers list:
http://cygwin.com/ml/cygwin-
Andy Koppe writes:
>
> On 8 December 2011 00:33, Enrico Forestieri wrote:
> > Corinna Vinschen writes:
> >>
> >> Just so it's clear why I did that, maybe you want to have a look into
> >> the brief discussion on the cygwin-developers list:
> >> http://cygwin.com/ml/cygwin-developers/2011-11/msg000
Enrico Forestieri writes:
>
> However, I experimented a bit with the last snapshot, and even using Greek
> or Japanese characters in file names, lyx seems to be working fine.
Sorry, it was a cursory test. Actually, cygwin_conv_path is only called
for absolute paths. Using an absolute Windows path
On 12/8/2011 1:52 AM, Christopher Faylor wrote:
On Wed, Dec 07, 2011 at 10:18:40PM -0500, Ken Brown wrote:
On 12/7/2011 6:13 PM, Christopher Faylor wrote:
On Wed, Dec 07, 2011 at 08:03:22AM -0500, Ken Brown wrote:
On 12/6/2011 10:22 PM, Christopher Faylor wrote:
On Tue, Dec 06, 2011 at 09:51:
Corinna Vinschen writes:
>
> Which raises the question why the Cygwin version of lyx uses
> cygwin_conv_path at all. Does it call Windows functions with the paths?
> If so, why? If not, why are the paths converted to Windows?
Because the user *could* enter Windows paths (e.g., for including ima
Hello,
I upgrade from snapshot 20110829 to current 20111208 qand I update the tools
too.
$ uname -a
CYGWIN_NT-6.1-WOW64 PCFX167 1.7.10s(0.255/5/3) 20111208 06:50:31 i686 Cygwin
I did rebaseall and peflagsall.
I got some "Bad address" errors while compiling with make while running shell
script
On Dec 7 16:47, Lars Bjørndal wrote:
> On on., des. 07, 2011 at 01:40:25 +0100, Lars Bjørndal wrote:
> > [Corinna]
> > > On Dec 7 10:23, Lars Bjørndal wrote:
> > > > [Corinna]
> > > > [...]
> > > >
> > > > > Btw., "brltty doesn't work" is a bit low on detail. It would also be
> > > > > helpful
On Dec 8 00:33, Enrico Forestieri wrote:
> Corinna Vinschen writes:
> >
> > Just so it's clear why I did that, maybe you want to have a look into
> > the brief discussion on the cygwin-developers list:
> > http://cygwin.com/ml/cygwin-developers/2011-11/msg0.html
>
> All good reasons, but you
On 8 December 2011 00:33, Enrico Forestieri wrote:
> Corinna Vinschen writes:
>>
>> Just so it's clear why I did that, maybe you want to have a look into
>> the brief discussion on the cygwin-developers list:
>> http://cygwin.com/ml/cygwin-developers/2011-11/msg0.html
>
> All good reasons, but
On Wed, Dec 07, 2011 at 05:18:28PM -0600, Yaakov (Cygwin/X) wrote:
>On Tue, 2011-12-06 at 10:37 +0100, Corinna Vinschen wrote:
>> A lot of changes and fixes have been made in Cygwin since 1.7.9 has
>> been released, so we're looking forward to release Cygwin 1.7.10 soon.
>>
>> Please test the late
On Wed, Dec 07, 2011 at 10:18:40PM -0500, Ken Brown wrote:
>On 12/7/2011 6:13 PM, Christopher Faylor wrote:
>> On Wed, Dec 07, 2011 at 08:03:22AM -0500, Ken Brown wrote:
>>> On 12/6/2011 10:22 PM, Christopher Faylor wrote:
On Tue, Dec 06, 2011 at 09:51:32PM -0500, Ken Brown wrote:
> On 12/
On 12/7/2011 6:13 PM, Christopher Faylor wrote:
On Wed, Dec 07, 2011 at 08:03:22AM -0500, Ken Brown wrote:
On 12/6/2011 10:22 PM, Christopher Faylor wrote:
On Tue, Dec 06, 2011 at 09:51:32PM -0500, Ken Brown wrote:
On 12/6/2011 3:02 PM, Corinna Vinschen wrote:
On Dec 6 13:28, Ken Brown wrote
Corinna Vinschen writes:
>
> Just so it's clear why I did that, maybe you want to have a look into
> the brief discussion on the cygwin-developers list:
> http://cygwin.com/ml/cygwin-developers/2011-11/msg0.html
All good reasons, but you are going to break backward compatibility.
At least, ly
On Tue, 2011-12-06 at 10:37 +0100, Corinna Vinschen wrote:
> A lot of changes and fixes have been made in Cygwin since 1.7.9 has
> been released, so we're looking forward to release Cygwin 1.7.10 soon.
>
> Please test the latest developer snapshots at http://cygwin.com/snapshots/
> which should ha
On Wed, Dec 07, 2011 at 08:03:22AM -0500, Ken Brown wrote:
>On 12/6/2011 10:22 PM, Christopher Faylor wrote:
>> On Tue, Dec 06, 2011 at 09:51:32PM -0500, Ken Brown wrote:
>>> On 12/6/2011 3:02 PM, Corinna Vinschen wrote:
On Dec 6 13:28, Ken Brown wrote:
> On 12/6/2011 12:57 PM, Corinna Vi
Greetings, Tim McDaniel!
> On Tue, 6 Dec 2011, Lars Bj_rndal wrote:
>> What doew Iirc mean?
> http://www.acronymfinder.com/ is often useful, but in this case, it
> produces a lot of useless crud.
If you search directly in Slang/Chat, it's usually more useful.
http://www.acronymfinder.com/Slang/I
On Dec 7 18:50, Bengt Larsson wrote:
> Corinna Vinschen wrote:
> >On Dec 7 18:00, Bengt Larsson wrote:
> >> Corinna Vinschen wrote:
> >>
> >> >- cygwin_conv_path and cygwin_conv_path_list: In CCP_WIN_A_TO_POSIX and
> >> > CCP_POSIX_TO_WIN_A conversions, use the current Windows ANSI or OEM
> >>
Corinna Vinschen wrote:
>On Dec 7 18:00, Bengt Larsson wrote:
>> Corinna Vinschen wrote:
>>
>> >- cygwin_conv_path and cygwin_conv_path_list: In CCP_WIN_A_TO_POSIX and
>> > CCP_POSIX_TO_WIN_A conversions, use the current Windows ANSI or OEM
>> > charset, depending on the return value of AreFile
On Dec 7 18:00, Bengt Larsson wrote:
> Corinna Vinschen wrote:
>
> >- cygwin_conv_path and cygwin_conv_path_list: In CCP_WIN_A_TO_POSIX and
> > CCP_POSIX_TO_WIN_A conversions, use the current Windows ANSI or OEM
> > charset, depending on the return value of AreFileApisANSI. Up to Cygwin
> > 1
On 7 December 2011 21:03, Ken Brown wrote:
> On 12/6/2011 10:22 PM, Christopher Faylor wrote:
>>
>> On Tue, Dec 06, 2011 at 09:51:32PM -0500, Ken Brown wrote:
>>>
>>> On 12/6/2011 3:02 PM, Corinna Vinschen wrote:
On Dec 6 13:28, Ken Brown wrote:
>
> On 12/6/2011 12:57 PM, Corinn
Corinna Vinschen wrote:
>- cygwin_conv_path and cygwin_conv_path_list: In CCP_WIN_A_TO_POSIX and
> CCP_POSIX_TO_WIN_A conversions, use the current Windows ANSI or OEM
> charset, depending on the return value of AreFileApisANSI. Up to Cygwin
> 1.7.9, both conversions used the current Cygwin cha
Am 07.12.2011 14:03, schrieb Ken Brown:
On 12/6/2011 10:22 PM, Christopher Faylor wrote:
On Tue, Dec 06, 2011 at 09:51:32PM -0500, Ken Brown wrote:
On 12/6/2011 3:02 PM, Corinna Vinschen wrote:
...
...
- When I finally get tired of waiting and kill mintty (and the
associated bash process) fro
On on., des. 07, 2011 at 01:40:25 +0100, Lars Bjørndal wrote:
> [Corinna]
> > On Dec 7 10:23, Lars Bjørndal wrote:
> > > [Corinna]
> > > [...]
> > >
> > > > Btw., "brltty doesn't work" is a bit low on detail. It would also be
> > > > helpful if you could find out with which snapshot brltty start
On 12/6/2011 10:22 PM, Christopher Faylor wrote:
On Tue, Dec 06, 2011 at 09:51:32PM -0500, Ken Brown wrote:
On 12/6/2011 3:02 PM, Corinna Vinschen wrote:
On Dec 6 13:28, Ken Brown wrote:
On 12/6/2011 12:57 PM, Corinna Vinschen wrote:
On Dec 6 12:37, Ken Brown wrote:
On 12/6/2011 4:37 AM, C
[Corinna]
> On Dec 7 10:23, Lars Bjørndal wrote:
> > [Corinna]
> > [...]
> >
> > > Btw., "brltty doesn't work" is a bit low on detail. It would also be
> > > helpful if you could find out with which snapshot brltty starts to
> > > misbehave.
> >
> > At 20111022. Now, I'm using the dll from 2011
On Dec 7 10:23, Lars Bjørndal wrote:
> [Corinna]
> [...]
>
> > Btw., "brltty doesn't work" is a bit low on detail. It would also be
> > helpful if you could find out with which snapshot brltty starts to
> > misbehave.
>
> At 20111022. Now, I'm using the dll from 20111021, and it works.
Thanks!
On Dec 7 04:33, Yaakov (Cygwin/X) wrote:
> On Tue, 2011-12-06 at 22:08 -0500, Christopher Faylor wrote:
> > On Tue, Dec 06, 2011 at 06:45:35PM +0100, Corinna Vinschen wrote:
> > >On Dec 6 15:39, marco atzeri wrote:
> > >> On 12/6/2011 10:37 AM, Corinna Vinschen wrote:
> > >> >A lot of changes and
On Tue, 2011-12-06 at 22:08 -0500, Christopher Faylor wrote:
> On Tue, Dec 06, 2011 at 06:45:35PM +0100, Corinna Vinschen wrote:
> >On Dec 6 15:39, marco atzeri wrote:
> >> On 12/6/2011 10:37 AM, Corinna Vinschen wrote:
> >> >A lot of changes and fixes have been made in Cygwin since 1.7.9 has
> >>
[Corinna]
[...]
> Btw., "brltty doesn't work" is a bit low on detail. It would also be
> helpful if you could find out with which snapshot brltty starts to
> misbehave.
At 20111022. Now, I'm using the dll from 20111021, and it works.
Regards,
Lars
--
Problem reports: http://cygwin.com/pr
On 12/7/2011 4:08 AM, Christopher Faylor wrote:
I have the impression that 2024 is working better than 2029,
and that 20111204 and 05 have some additional problems.
On 2029, building atlas on W7/x64 I see the custom config
spinning and never ending, while on 2024 is goes smooth.
On Tue, Dec 06, 2011 at 09:51:32PM -0500, Ken Brown wrote:
>On 12/6/2011 3:02 PM, Corinna Vinschen wrote:
>> On Dec 6 13:28, Ken Brown wrote:
>>> On 12/6/2011 12:57 PM, Corinna Vinschen wrote:
On Dec 6 12:37, Ken Brown wrote:
> On 12/6/2011 4:37 AM, Corinna Vinschen wrote:
>> A lot o
On Tue, Dec 06, 2011 at 06:45:35PM +0100, Corinna Vinschen wrote:
>On Dec 6 15:39, marco atzeri wrote:
>> On 12/6/2011 10:37 AM, Corinna Vinschen wrote:
>> >A lot of changes and fixes have been made in Cygwin since 1.7.9 has
>> >been released, so we're looking forward to release Cygwin 1.7.10 soon
On 12/6/2011 3:02 PM, Corinna Vinschen wrote:
On Dec 6 13:28, Ken Brown wrote:
On 12/6/2011 12:57 PM, Corinna Vinschen wrote:
On Dec 6 12:37, Ken Brown wrote:
On 12/6/2011 4:37 AM, Corinna Vinschen wrote:
A lot of changes and fixes have been made in Cygwin since 1.7.9 has
been released, so
On Tue, 6 Dec 2011, Lars Bj_rndal wrote:
What doew Iirc mean?
http://www.acronymfinder.com/ is often useful, but in this case, it
produces a lot of useless crud.
http://www.urbandictionary.com/define.php?term=iirc is often of more
use.
If I Recall Correctly.
--
Tim McDaniel, t...@panix.com
[Samuel]
> Lars Bjørndal, le Tue 06 Dec 2011 21:17:37 +0100, a écrit :
> > [Corinna]
> > > On Dec 6 16:27, Corinna Vinschen wrote:
> > > > On Dec 6 16:21, Lars Bjørndal wrote:
> > > > > Hi
> > > > >
> > > > > Sorry, but now, with this new snapshot, BRLTTY doesn't work. I'm not
> > > > > sure how
Lars Bjørndal, le Tue 06 Dec 2011 21:17:37 +0100, a écrit :
> [Corinna]
> > On Dec 6 16:27, Corinna Vinschen wrote:
> > > On Dec 6 16:21, Lars Bjørndal wrote:
> > > > Hi
> > > >
> > > > Sorry, but now, with this new snapshot, BRLTTY doesn't work. I'm not
> > > > sure how to figure out which snap
[Corinna]
> On Dec 6 16:27, Corinna Vinschen wrote:
> > On Dec 6 16:21, Lars Bjørndal wrote:
> > > Hi
> > >
> > > Sorry, but now, with this new snapshot, BRLTTY doesn't work. I'm not
> > > sure how to figure out which snapshot I'm currently using, where the
> > > program does work.
> >
> > Unam
On Dec 6 13:28, Ken Brown wrote:
> On 12/6/2011 12:57 PM, Corinna Vinschen wrote:
> >On Dec 6 12:37, Ken Brown wrote:
> >>On 12/6/2011 4:37 AM, Corinna Vinschen wrote:
> >>>A lot of changes and fixes have been made in Cygwin since 1.7.9 has
> >>>been released, so we're looking forward to release
On 12/6/2011 5:56 AM, Thorsten Kampe wrote:
> * Corinna Vinschen (Tue, 6 Dec 2011 10:37:46 +0100)
>> - Fifos have been rewritten and should now be more reliable.
>
> Trying to run GNU Screen:
> "open fifo /tmp/uscreens/S-thorsten/2756.cons1.hombre: Bad file
> descriptor"
I'm seeing this as well
On Dec 6 12:37, Ken Brown wrote:
> On 12/6/2011 4:37 AM, Corinna Vinschen wrote:
> >A lot of changes and fixes have been made in Cygwin since 1.7.9 has
> >been released, so we're looking forward to release Cygwin 1.7.10 soon.
> >
> >Please test the latest developer snapshots at http://cygwin.com/s
On Dec 6 15:39, marco atzeri wrote:
> On 12/6/2011 10:37 AM, Corinna Vinschen wrote:
> >A lot of changes and fixes have been made in Cygwin since 1.7.9 has
> >been released, so we're looking forward to release Cygwin 1.7.10 soon.
> >[...]
>
> Hi Corinna,
> I have the impression that 2024 is w
On 12/6/2011 4:37 AM, Corinna Vinschen wrote:
A lot of changes and fixes have been made in Cygwin since 1.7.9 has
been released, so we're looking forward to release Cygwin 1.7.10 soon.
Please test the latest developer snapshots at http://cygwin.com/snapshots/
which should have "Release Candidate
On Dec 6 16:27, Corinna Vinschen wrote:
> On Dec 6 16:21, Lars Bjørndal wrote:
> > Hi
> >
> > Sorry, but now, with this new snapshot, BRLTTY doesn't work. I'm not
> > sure how to figure out which snapshot I'm currently using, where the
> > program does work.
>
> Uname -a. The build date will s
On Dec 6 16:21, Lars Bjørndal wrote:
> Hi
>
> Sorry, but now, with this new snapshot, BRLTTY doesn't work. I'm not
> sure how to figure out which snapshot I'm currently using, where the
> program does work.
Uname -a. The build date will show.
Corinna
--
Corinna Vinschen Ple
Hi
Sorry, but now, with this new snapshot, BRLTTY doesn't work. I'm not
sure how to figure out which snapshot I'm currently using, where the
program does work.
Regards,
Lars
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation:
On 12/6/2011 10:37 AM, Corinna Vinschen wrote:
A lot of changes and fixes have been made in Cygwin since 1.7.9 has
been released, so we're looking forward to release Cygwin 1.7.10 soon.
Please test the latest developer snapshots at http://cygwin.com/snapshots/
which should have "Release Candidat
* Corinna Vinschen (Tue, 6 Dec 2011 10:37:46 +0100)
> - Fifos have been rewritten and should now be more reliable.
Trying to run GNU Screen:
"open fifo /tmp/uscreens/S-thorsten/2756.cons1.hombre: Bad file
descriptor"
Thorsten
--
Problem reports: http://cygwin.com/problems.html
FAQ:
On Dec 6 07:07, Ken Brown wrote:
> On 12/6/2011 4:37 AM, Corinna Vinschen wrote:
> >In 1.7.10 a few internals have changed, which influence the way some of
> >the Cygwin tools work. For instance, the Cygwin ps tool from 1.7.9 will
> >show weird tty numbers for processes running in a console windo
On 12/6/2011 4:37 AM, Corinna Vinschen wrote:
In 1.7.10 a few internals have changed, which influence the way some of
the Cygwin tools work. For instance, the Cygwin ps tool from 1.7.9 will
show weird tty numbers for processes running in a console window, while
the new ps knows how to handle the
A lot of changes and fixes have been made in Cygwin since 1.7.9 has
been released, so we're looking forward to release Cygwin 1.7.10 soon.
Please test the latest developer snapshots at http://cygwin.com/snapshots/
which should have "Release Candidate" quality.
A very noticable change is that for
92 matches
Mail list logo