Re: Unable to install X on 64-bit Windows 7 Premium

2010-08-15 Thread Dan Tsafrir
On Sun, Aug 15, 2010 at 04:03, Dan Tsafrir da...@cs.technion.ac.il wrote: I've done exactly this, then tried to install some X stuff and got:    Package: xinit            xinit.sh exit code 8    Package: No package            xinit.sh exit code 8 It turns out that the above error message

Re: Unable to install X on 64-bit Windows 7 Premium

2010-08-14 Thread Dan Tsafrir
On Tue, Aug 10, 2010 at 15:12, Jon TURNEY jon.tur...@dronecode.org.uk wrote: On 10/08/2010 00:19, Bob Kline wrote: I finally had to replace my ancient Windows XP box, and ended up with a Windows 7 Home Premium 64-bit system. If I run setup.exe to install a fresh cygwin, it succeeds as long

Re: emacs-x11 takes 30-40 sec to open after upgrading to cygwin-1.7

2010-04-14 Thread Dan Tsafrir
On Tue, Apr 13, 2010 at 14:16, Ken Brown kbr...@cornell.edu wrote: On 4/12/2010 7:52 PM, Dan Tsafrir wrote: On Tue, Apr 6, 2010 at 00:39, Jon TURNEYjon.tur...@dronecode.org.uk  wrote: I've conducted a few repeated measurements and it looks as though setting LANG to be en_US somewhat reduces

Re: emacs-x11 takes 30-40 sec to open after upgrading to cygwin-1.7

2010-04-14 Thread Dan Tsafrir
On Tue, Apr 13, 2010 at 17:22, Jon TURNEY jon.tur...@dronecode.org.uk wrote: The mechanism that loads ~/.Xdefaults into the X server resource database is nicely obscure, so I'm not sure that -q actually avoids that. The definitive way to check would be to move ~/.Xdefaults aside, restart the

Re: emacs-x11 takes 30-40 sec to open after upgrading to cygwin-1.7

2010-04-14 Thread Dan Tsafrir
On Tue, Apr 13, 2010 at 17:55, Markus Hoenicka markus.hoeni...@mhoenicka.de wrote: Jon TURNEY jon.tur...@dronecode.org.uk was heard to say: So far it seems that (1) emacs takes a long time to start up (2) xterm starts up quickly.  Are there other X applications that you use and how do they

Re: emacs-x11 takes 30-40 sec to open after upgrading to cygwin-1.7

2010-04-14 Thread Dan Tsafrir
On Wed, Apr 14, 2010 at 10:17, Dan Tsafrir da...@cs.technion.ac.il wrote: On Tue, Apr 13, 2010 at 17:22, Jon TURNEY jon.tur...@dronecode.org.uk wrote: [snip] So far it seems that (1) emacs takes a long time to start up (2) xterm starts up quickly.  Are there other X applications that you use

Re: emacs-x11 takes 30-40 sec to open after upgrading to cygwin-1.7

2010-04-14 Thread Dan Tsafrir
On Wed, Apr 14, 2010 at 12:24, Markus Hoenicka markus.hoeni...@mhoenicka.de wrote: I've had a look at your strace log. I've noticed the same block of statements which seems to be repeated over and over again (see my previous post).  Did you watch the strace output on the console in real time

Re: emacs-x11 takes 30-40 sec to open after upgrading to cygwin-1.7

2010-04-13 Thread Dan Tsafrir
On Tue, Apr 13, 2010 at 09:46, Bengt-Arne Fjellner bengt-arne.fjell...@ltu.se wrote: On 2010-04-13 1:52 AM, Dan Tsafrir wrote: I've invoked emacs with -Q (and also, just to make sure, removed my ~/.Xdefaults). It did not change anything: emacs still takes ~30 seconds to open. A shot (well

Re: emacs-x11 takes 30-40 sec to open after upgrading to cygwin-1.7

2010-04-12 Thread Dan Tsafrir
On Tue, Apr 6, 2010 at 00:39, Jon TURNEY jon.tur...@dronecode.org.uk wrote: I've conducted a few repeated measurements and it looks as though setting LANG to be en_US somewhat reduces the start time of emacs-x11: instead of ~30 seconds with LANG=C.UTF-8, it take ~27 seconds LANG=en_US. While

Re: emacs-x11 takes 30-40 sec to open after upgrading to cygwin-1.7

2010-03-29 Thread Dan Tsafrir
On Mon, Mar 29, 2010 at 19:14, Jon TURNEY jon.tur...@dronecode.org.uk wrote: On 29/03/2010 11:33, Dan Tsafrir wrote: After I've upgraded to cygwin-1.7 my emacs takes 30-40 seconds to open. Following http://x.cygwin.com/docs/faq/cygwin-x-faq.html#poor-performance, disabling my antivirus has

Re: Reproducing the cygwin X clipboard problems

2009-02-26 Thread Dan Tsafrir
On Wed, Feb 25, 2009 at 5:51 PM, Jon TURNEY jon.tur...@dronecode.org.uk wrote: I've built a version of 1.5.3-7, with this patch reverted and lots more clipboard debugging added.  You can download it from [2] It would be most helpful if you could try this and see if the clipboard problems you

Re: Reproducing the cygwin X problems

2009-02-24 Thread Dan Tsafrir
On Tue, Feb 24, 2009 at 2:13 PM, Jon TURNEY It seems likely that this clipboard contention between multiple applications might behave differently on machines with multi-core processors (which I don't have the capability to test on), so can you indicate if you are using single-core or

Re: xdvi unexplained locale problem

2009-02-20 Thread Dan Tsafrir
On Wed, Feb 18, 2009 at 3:02 PM, Mike Ayers mike_ay...@tvworks.com wrote: Dan Tsafrir wrote: open xdvi, I get the following error message: Warning: locale not supported by C library, locale unchanged Warning: locale not supported by Xlib, locale set to C Warning: X locale modifiers

Re: Reproducing the cygwin X problems

2009-02-20 Thread Dan Tsafrir
On Fri, Feb 20, 2009 at 1:05 PM, Mike Ayers mike_ay...@tvworks.com wrote: I can neither confirm nor deny this, as I don't have ClipBook available. Did you try to run 'clipbrd' through start-run ? I just kill Xwin.exe forcibly in task manager - it takes all X apps with it.

Re: Reproducing the cygwin X problems

2009-02-20 Thread Dan Tsafrir
On Fri, Feb 20, 2009 at 3:19 PM, Williams, Chris (Marlboro) christopherb.willi...@amd.com wrote: I use the file C:\cygwin\bin\startxwin.bat Me too, so I would guess that the difference in the copy-paste behavior we observe, is unrelated. --Dan -- Unsubscribe info:

Re: R: starxwin.bat always misfires the xterm once - it works!

2009-02-18 Thread Dan Tsafrir
On Wed, Feb 18, 2009 at 12:14 PM, Jon TURNEY jon.tur...@dronecode.org.uk wrote: Making startxwin.bat just launch startx or xinit would also largely solve the problem of overwriting people's customisations to startxwin.bat, as it has defined places to put those. I would like to point out that

Re: xdvi unexplained locale problem

2009-02-14 Thread Dan Tsafrir
On Sat, Feb 14, 2009 at 1:46 PM, Jon TURNEY jon.tur...@dronecode.org.uk wrote: NLSPATH = 'C:\Programs\IBM\RunTime\%N;' You should probably try without that in your environment, just to rule it out. $ unset NLSPATH $ xdvi It didn't work :( Any other ideas? -- Unsubscribe info: