Yaakov (Cygwin/X) wrote:
On 03/08/2009 10:49, Rob Gillen wrote:
After updating my 1.7 installation to the latest cygwin DLL, my xterms
were finally able to exec bash (with some issues from bash as well),
but I immediately ran into segfault when copying to the clipboard from
nedit. I.e. as soon
On Fri, Nov 20, 2009 at 4:25 PM, Jon TURNEY jon.tur...@dronecode.org.uk wrote:
On 13/11/2009 03:14, Ken Brown wrote:
On 11/12/2009 3:17 PM, Jon TURNEY wrote:
On 10/11/2009 23:44, Mike Ayers wrote:]
Apparently, run.exe is not providing stdout/stderr to dump to. The
workaround:
[SNIP]
Ken Brown wrote:
On 11/26/2009 2:30 AM, Lothar Brendel wrote:
Errh, yes. Hence, to make Cygwin/X+xterm run out of the box (using
the
start menu shortcut), you have to install the CJK fonts. One more
There are three packages: font-isas-misc, font-jis-misc, and
font-daewoo-misc.
I installed
Timares, Brian (Patriot) wrote:
[...]
Nothing works. 1.7 doesn't work for me out-of-the-box (yes, I ripped
it all out and tried it fresh :-)
I open a DOS box and check processes and see bash running with an l or
a 1 in the left columnn, but nothing appears. If I launch an Xterm
it opens up.
Thomas Dickey wrote:
On Thu, 26 Nov 2009, Lothar Brendel wrote:
[...]
Hence, to make Cygwin/X+xterm run out of the box (using
the start menu shortcut), you have to install the CJK fonts. One
more noob-question,
otoh, (discarding run-out-of-the-box, since that doesn't give a good
solution),
On Fri, 27 Nov 2009, Lothar Brendel wrote:
Thomas Dickey wrote:
On Thu, 26 Nov 2009, Lothar Brendel wrote:
[...]
Hence, to make Cygwin/X+xterm run out of the box (using
the start menu shortcut), you have to install the CJK fonts. One
more noob-question,
otoh, (discarding
Timares, Brian (Patriot) wrote:
Lothar Brendel wrote:
[...]
My guess: It's the old checkX-problem again because you're using
version
0.3.0-1 of the run2-package. Do to some reason unknown to me, that's
the default version. But we need 0.3.1-1, which you only get when
explicitely
Lothar Brendel wrote:
Timares, Brian (Patriot) wrote:
Lothar Brendel wrote:
My guess: It's the old checkX-problem again because you're using
version
0.3.0-1 of the run2-package. Do to some reason unknown to me, that's
the default version. But we need 0.3.1-1, which you only get when
Tried
With the latest release 1.7.0-67 Cygwin [1.7] now works glitch-free on
FAT32 filesystems; but to run X on FAT32 we still have to revert to
1.7.0-60. The recommended fix (there may be more than one but this seems
potentially the easiest and most effective) is to run X -nolock. But
this option
