Hi Marco,
On Mar 11 21:55, Marco Atzeri wrote:
On 10/03/2014 11:11, Corinna Vinschen wrote:
built from CVS. No crash either.
Corinna
Hi Corinna,
I think it is due to the unusual history of my cygwin installation,
that is triggering a corner case.
The system is installed on a USB
On 12/03/2014 10:23, Corinna Vinschen wrote:
thanks for tracking this down. Still, it shouldn't result in a
Bad address error, only in a GID value -1. Pity that you fixed
it, otherwise your machine would be a wonderful guinea pig :}
Thanks,
Corinna
That Bad address file is still
On Mar 12 10:35, Marco Atzeri wrote:
On 12/03/2014 10:23, Corinna Vinschen wrote:
thanks for tracking this down. Still, it shouldn't result in a
Bad address error, only in a GID value -1. Pity that you fixed
it, otherwise your machine would be a wonderful guinea pig :}
Thanks,
On 12/03/2014 10:43, Corinna Vinschen wrote:
On Mar 12 10:35, Marco Atzeri wrote:
On 12/03/2014 10:23, Corinna Vinschen wrote:
And the USB disk is full of similar files
I just noticed that the 64bit is also available
$ cd /cygdrive/e/cygwin64/var/log
$ ls -l
ls: cannot access xwin: Bad
On Mar 12 11:09, Marco Atzeri wrote:
On 12/03/2014 10:43, Corinna Vinschen wrote:
On Mar 12 10:35, Marco Atzeri wrote:
On 12/03/2014 10:23, Corinna Vinschen wrote:
And the USB disk is full of similar files
I just noticed that the 64bit is also available
$ cd
On 10/03/2014 11:11, Corinna Vinschen wrote:
On Mar 10 07:46, Marco Atzeri wrote:
On 10/03/2014 04:21, Christopher Faylor wrote:
On Sun, Mar 09, 2014 at 09:25:02PM -0500, Steven Penny wrote:
On Sun, Mar 9, 2014 at 2:14 PM, Christopher Faylor wrote:
Interesting problem. Windows always
On 10/03/2014 04:21, Christopher Faylor wrote:
On Sun, Mar 09, 2014 at 09:25:02PM -0500, Steven Penny wrote:
On Sun, Mar 9, 2014 at 2:14 PM, Christopher Faylor wrote:
Interesting problem. Windows always surprises.
This should be fixed in the upcoming snapshot.
cgf
$ uname -svr
On Mar 10 07:46, Marco Atzeri wrote:
On 10/03/2014 04:21, Christopher Faylor wrote:
On Sun, Mar 09, 2014 at 09:25:02PM -0500, Steven Penny wrote:
On Sun, Mar 9, 2014 at 2:14 PM, Christopher Faylor wrote:
Interesting problem. Windows always surprises.
This should be fixed in the
Christopher Faylor wrote:
There is a new snapshot available which should fix the problem with
screen status bar.
There are still issues with the console buffer and full screen apps
like vim/emacs/less. If you scroll the buffer while in that mode
then things will get weird. The solution so far
On Thu, Feb 27, 2014 at 03:26:33PM -0500, Christopher Faylor wrote:
On Thu, Feb 27, 2014 at 07:14:49PM +0100, Thorsten Kampe wrote:
* Christopher Faylor (Thu, 20 Feb 2014 13:11:39 -0500)
I forgot to mention that I managed to duplicate this problem and am
working on a fix for this and the other
On Sun, Mar 09, 2014 at 03:14:32PM -0400, Christopher Faylor wrote:
On Thu, Feb 27, 2014 at 03:26:33PM -0500, Christopher Faylor wrote:
On Thu, Feb 27, 2014 at 07:14:49PM +0100, Thorsten Kampe wrote:
* Christopher Faylor (Thu, 20 Feb 2014 13:11:39 -0500)
I forgot to mention that I managed to
On Sun, Mar 9, 2014 at 2:14 PM, Christopher Faylor wrote:
There are still issues with the console buffer and full screen apps
like vim/emacs/less. If you scroll the buffer while in that mode
then things will get weird. The solution so far is: Don't do that.
1. man bash
2. down arrow once
3.
On Sun, Mar 09, 2014 at 09:25:02PM -0500, Steven Penny wrote:
On Sun, Mar 9, 2014 at 2:14 PM, Christopher Faylor wrote:
There are still issues with the console buffer and full screen apps
like vim/emacs/less. If you scroll the buffer while in that mode
then things will get weird. The solution
* Christopher Faylor (Thu, 27 Feb 2014 15:26:33 -0500)
On Thu, Feb 27, 2014 at 07:14:49PM +0100, Thorsten Kampe wrote:
* Christopher Faylor (Thu, 20 Feb 2014 13:11:39 -0500)
I forgot to mention that I managed to duplicate this problem and am
working on a fix for this and the other screen
* Christopher Faylor (Thu, 20 Feb 2014 13:11:39 -0500)
I forgot to mention that I managed to duplicate this problem and am
working on a fix for this and the other screen garbling seen in
recent snapshots.
Reporting a possibly related bug in connection with the latest
snapshots: connecting to
On Thu, Feb 27, 2014 at 07:14:49PM +0100, Thorsten Kampe wrote:
* Christopher Faylor (Thu, 20 Feb 2014 13:11:39 -0500)
I forgot to mention that I managed to duplicate this problem and am
working on a fix for this and the other screen garbling seen in
recent snapshots.
Reporting a possibly
On Feb 21 11:49, Andrey Repin wrote:
Greetings, Thomas Wolff!
Not specific to this snapshot but it happens when trying to test it:
If a cygwin console is started from a cygwin terminal (e.g. in mintty:
cygstart /Cygwin.bat), the TERM variable is set incorrectly.
Suggested fix: ... unset
Greetings, Corinna Vinschen!
Not specific to this snapshot but it happens when trying to test it:
If a cygwin console is started from a cygwin terminal (e.g. in mintty:
cygstart /Cygwin.bat), the TERM variable is set incorrectly.
Suggested fix: ... unset TERM to Cygwin.bat.
unset would
On Fri, Feb 21, 2014 at 04:17:11PM +0400, Andrey Repin wrote:
Not specific to this snapshot but it happens when trying to test it:
If a cygwin console is started from a cygwin terminal (e.g. in mintty:
cygstart /Cygwin.bat), the TERM variable is set incorrectly.
Suggested fix: ... unset
On Wed, Feb 19, 2014 at 03:52:37PM +0100, Bengt Larsson wrote:
Christopher Faylor wrote:
On Wed, Feb 19, 2014 at 12:52:58PM +0100, Bengt Larsson wrote:
I start a console window, set the buffer to 1100 lines, display a lot in
it. Start bash, type ^L: the console window resizes to be only one line.
I forgot to mention that I managed to duplicate this problem and am working
on a fix for this and the other screen garbling seen in recent snapshots.
Hm, with luck maybe that will also fix the recent garbled screen problem in
screen(1):
http://cygwin.com/ml/cygwin/2014-01/msg00223.html
On Thu, Feb 20, 2014 at 02:30:50PM -0500, Andrew Schulman wrote:
I forgot to mention that I managed to duplicate this problem and am working
on a fix for this and the other screen garbling seen in recent snapshots.
Hm, with luck maybe that will also fix the recent garbled screen problem in
Am 20.02.2014 02:26, schrieb Andrey Repin:
Greetings, Thomas Wolff!
Not specific to this snapshot but it happens when trying to test it:
If a cygwin console is started from a cygwin terminal (e.g. in mintty:
cygstart /Cygwin.bat), the TERM variable is set incorrectly.
Suggested fix: ... unset
Greetings, Thomas Wolff!
Not specific to this snapshot but it happens when trying to test it:
If a cygwin console is started from a cygwin terminal (e.g. in mintty:
cygstart /Cygwin.bat), the TERM variable is set incorrectly.
Suggested fix: ... unset TERM to Cygwin.bat.
unset would be better
Christopher Faylor wrote:
We are contemplating releasing an interim 1.7.29 which does
not incorporate Corinna's revamping of Cygwin's uid/gid handling.
So, please check out snapshots, paying particular attention to the
non-passwd/group parts of this file:
On Wed, Feb 19, 2014 at 12:52:58PM +0100, Bengt Larsson wrote:
Christopher Faylor wrote:
We are contemplating releasing an interim 1.7.29 which does
not incorporate Corinna's revamping of Cygwin's uid/gid handling.
So, please check out snapshots, paying particular attention to the
Christopher Faylor wrote:
On Wed, Feb 19, 2014 at 12:52:58PM +0100, Bengt Larsson wrote:
I start a console window, set the buffer to 1100 lines, display a lot in
it. Start bash, type ^L: the console window resizes to be only one line.
Same result if bash was started first, then display data, then
Am 18.02.2014 20:08, schrieb Christopher Faylor:
We are contemplating releasing an interim 1.7.29 which does
not incorporate Corinna's revamping of Cygwin's uid/gid handling.
So, please check out snapshots, paying particular attention to the
non-passwd/group parts of this file:
Greetings, Thomas Wolff!
Not specific to this snapshot but it happens when trying to test it:
If a cygwin console is started from a cygwin terminal (e.g. in mintty:
cygstart /Cygwin.bat), the TERM variable is set incorrectly.
Suggested fix: ... unset TERM to Cygwin.bat.
unset would be
Am 19.02.2014 23:24, schrieb Andrey Repin:
Greetings, Thomas Wolff!
Not specific to this snapshot but it happens when trying to test it:
If a cygwin console is started from a cygwin terminal (e.g. in mintty:
cygstart /Cygwin.bat), the TERM variable is set incorrectly.
Suggested fix: ... unset
Greetings, Thomas Wolff!
Not specific to this snapshot but it happens when trying to test it:
If a cygwin console is started from a cygwin terminal (e.g. in mintty:
cygstart /Cygwin.bat), the TERM variable is set incorrectly.
Suggested fix: ... unset TERM to Cygwin.bat.
unset would be better
We are contemplating releasing an interim 1.7.29 which does
not incorporate Corinna's revamping of Cygwin's uid/gid handling.
So, please check out snapshots, paying particular attention to the
non-passwd/group parts of this file:
32 matches
Mail list logo
