ThinkDifferently wrote:
My solution was, at the very least, to re-run setup.exe and to install the
package font-misc-misc. Once I did that, XWin stopped hanging and xterm
and xclock ran without a hitch.
I found this nugget of information buried deep in the
Siegmar Gross wrote:
...
if mpic++ -DHAVE_CONFIG_H -I. -I. -I. -I../../src
-I/usr/X11R6/include -O -MT xmpi_misc.o -MD -MP -MF
.deps/xmpi_misc.Tpo \
-c -o xmpi_misc.o `test -f 'xmpi_misc.cc' ||
echo './'`xmpi_misc.cc; \
then mv -f .deps/xmpi_misc.Tpo
John Emmas wrote:
- Original Message - From: Jon TURNEY
Subject: Re: X / gtk-x11 / flicker and other problems
btw, I use -multiwindow mode all the time, but I've obviously trained
myself not to see any of these artefacts
lol - fair point..! But I must admit, having seen how the
Mike Ayers wrote all on one line:
From where? I believe this should be ~/.Xdefaults, but the nature of cygwin can make ~ an indefinite place for startup files. I set %HOME%, which becomes $HOME to what will be ~, but if I put
XTerm*toolbar: false in $HOME/.Xdefaults I still have toolbars
I have an additional answer to Cygwin/X FAQ 6.1, X11Forwarding does not
work with OpenSSH under Cygwin
--- begin
A6:
If the *remote* machine is a Windows machine using Cygwin OpenSSH,
make sure the Cygwin xauth package is installed on the *remote*
machine. The OpenSSH server
I Have not used X in a while ( a few months). I did a complete update to the
latest Cygwin packages. When I logged onto the school system , I tried to open
an emacs window and got the following:
Warning: Cannot convert string
-*-courier-medium-r-*-*-*-120-*-*-*-*-iso8859-* to type FontStruct
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Joe Java wrote:
I Have not used X in a while ( a few months). I did a complete update to the
latest Cygwin packages. When I logged onto the school system , I tried to
open an emacs window and got the following:
Warning: Cannot convert
I recently upgraded and ran into this problem as well.
I watched the XWin.exe process using ProcMon from
sysinternals.com and it doesn't look like a problem of
directory / file / user permissions as the FAQ would suggest.
From ProcMon it looks like /tmp/.tX0-lock is being deleted
before it
