Re: cscope -d can't find trailer offset if path contains space (was: vim mlcscope interface issues)
Hello, an easy work around for the problem that cscope and its variant mlcscope cannot deal with paths containing spaces under Cygwin is to replace such paths with their DOS short name equivalents, since these do not contain spaces. The error surfaces as the error message mlcscope: cannot read trailer offset from file ./cscope.out and in that mlcscope recreates the program database each time it is started. When starting cscope using relative paths (the most frequent case), eliminating spaces must be done for the current working directory. The cygpath utility comes in handy for this. E.g., invoking mlcscope as (cd $(cygpath -u $(cygpath -d $PWD));mlcscope -b) solves the problem. In the above line, the inner call to cygpath converts the working directory to DOS format, the outer call converts the result to Cygwin format; preserving the short names of DOS, but replacing backslashes with forward slashes, for example. Unfortunately, it is not possible to combine the -u and -d flags in a single invocation of cygpath; this would be a useful extension. Regards, Konrad Schwarz P.S.: Sorry for resurrecting an old thread from Jan 2007. However, this thread seems to be the only place the problem was discussed. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: cscope -d can't find trailer offset if path contains space (was: vim mlcscope interface issues)
On 4/17/2012 9:55 AM, Schwarz, Konrad wrote: Hello, an easy work around for the problem that cscope and its variant mlcscope cannot deal with paths containing spaces under Cygwin is to replace such paths with their DOS short name equivalents, since these do not contain spaces. the easy solution is to not use paths with space in cygwin Regards, Konrad Schwarz P.S.: Sorry for resurrecting an old thread from Jan 2007. However, this thread seems to be the only place the problem was discussed. the right way is to open a new thread, not resurrecting the dead. Things are changed in 5 years Marco -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: [PATCH] Fix command line arguments for multiple monitors
On 14/04/2012 16:28, Jörg Mensmann wrote: placing the X server on a specific monitor using something like -screen 0 @2 is broken since November. The attached patch restores the old behaviour. Thanks very much for investigating this issue and for the patch. I'll include this in the next X server build. This happened since commit 3ead1d810b0e157078db39712e02ea6dc85216d8, because EnumDisplayMonitor() returns FALSE if its callback function returns FALSE (which is not clearly documented), and QueryMonitor() would then also return FALSE. I don't observe this behaviour on my test machine, EnumDisplayMonitor() returns TRUE, so I'd be interested to know what version of Windows you are using. I am a little concerned that I can't find any evidence using google of anyone else reporting having the MonitorEnumProc callback function return FALSE to terminate the enumeration causes EnumDisplayMonitor() to return 0, indicating failure, so maybe there is something else going on here... -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Workaround Possible Cause - Failed to activate core device - Could not invoke xkbcomp on Failed X Server Launch
On 13/04/2012 03:30, Charles Sheridan wrote: This week, after upgrading my Cygwin installation for the first time since ~April of 2011, X server startup failed, with the below oft-reported entries at the end of /cywin/var/log/xwin/Xwin.0.log -- ... [ 10092.016] (II) GLX: Initialized Win32 native WGL GL provider for screen 0 [ 10092.235] (EE) Couldn't open compiled keymap file /var/lib/xkb/server-0.xkm [ 10092.235] (EE) XKB: Failed to load keymap. Loading default keymap instead. [ 10092.313] (EE) Couldn't open compiled keymap file /var/lib/xkb/server-0.xkm [ 10092.313] XKB: Failed to compile keymap [ 10092.313] Keyboard initialization failed. This could be a missing or incorrect setup of xkeyboard-config. [ 10092.313] Fatal server error: [ 10092.313] Failed to activate core devices. [ 10092.313] Server terminated with error (1). Closing log file. This occurs on startup attempts from Xwin, startx, startxwin. I have not previously seen X server startup failure, over 10 years of Cygwin-X use on several different mswin machines. X server startup failure persists after Cygwin re-installation following an HP Vista Enterprise laptop reboot, without any Cygwin processes running, and despite post-install run of several recommended variations on `rebaseall` -- `rebaseall -b 0x7700` under both ash dash, and without the -b arg. = WORKAROUND: The new Xlaunch in the All Programs/Cygwin-X dir off the Windows Start Button starts X without issue. = POSSIBLE CAUSE: The same Xwin.0.log errors are reported in several X windows fora for platforms other than Cygwin. The first link below is a long entry in a Debian forum concluding that the issue relates to a problematic memory module, that can be bypassed via the nopat option to XWin. I couldn't get the Cygwin XWin cmd to recognize this option. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=646987 Read more carefully. nopat is a linux kernel option, which is being used there to work-around a kernel bug. So all that bug tells you is when running the xkbcomp program at xserver startup fails, you get these error messages. -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: FW: RE: Cut and Paste between X and WindowsXP sometimes fails
On 09/04/2012 16:53, Bennett, Tony wrote: The fix continues to work well... ...will this fix be integrated into X soon...??? Thanks for testing. Unfortunately, this fix seems to break other clipboard uses (In my testing, copying from a native Firefox to cygwin X emacs didn't work anymore), so I need to find the time to look at it some more before I can include it. -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Taskbar appearance changes between xorg-server 11 series and 12.0 series (more)
On 11/04/2012 11:39, Eliot Moss wrote: When playing around with xlaunch configurations and such, I ran startxwin several times this morning. ONCE, X came up without the iconized StartXWin window (i.e., things displayed as they used to before I upgraded xorg-server). This makes me suspect that there may be some kind of timing-related behavior. Perhaps the relevant code did not change between releases, but other changes affected relative timing of various actions, exposing a latent bug or race condition. I'm still not entirely sure what process in running in this window you complain of. Can you be say what the title and contents of this window are? I'm also not sure if this problem is related to he X server at all. Can you try creating a shortcut which runs the following command, for example, and see if the bash window is always successfully hidden? C:\cygwin\bin\run.exe /usr/bin/bash.exe -l -c sleep 10 -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
startx with different displays
I have intermittent problems to start XWin. My client would wait for an accessible server. In recent times, when this happens with :0, I try to use :1 instead, which usually works. Today, the two processes interferred. I was waiting on :0, and as I started a sttrax session on :1, both clients rose up, both reporting DISPLAY=:1! Marc -- View this message in context: http://old.nabble.com/startx-with-different-displays-tp33702991p33702991.html Sent from the cygwin-xfree mailing list archive at Nabble.com. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
[ANNOUNCEMENT] Updated: xorg-server-1.12.0-4
The following packages have been updated in the Cygwin distribution: *** xorg-server-1.12.0-4 *** xorg-server-common-1.12.0-4 *** xorg-server-dmx-1.12.0-4 *** xorg-server-extra-1.12.0-4 *** xorg-server-devel-1.12.0-4 These packages contain XWin and the other X.Org X11 servers. The following cygwin-specific changes have been made since 1.12.0-3: * Fix a problem which could prevent multiple monitor support from working on some systems (Thanks to Jörg Mensmann for patch) * If a window has had its taskbar button removed (e.g. by the _NET_WM_STATE_SKIP_TASKBAR hint), disable its minimize button to prevent it becoming lost (Thanks to Colin Harrison for patch) 134fcc78f06512dac97ba3ff8b601b52 *xorg-server-1.12.0-4.tar.bz2 6639dda222775a2046246cfa5c6f1aaf *xorg-server-common-1.12.0-4.tar.bz2 71aff2a88b9860269da2899910a69740 *xorg-server-devel-1.12.0-4.tar.bz2 677e7b631aca77cf1ce14d5de571679e *xorg-server-dmx-1.12.0-4.tar.bz2 224d9f4af8d68d556f91853e8e6cfcc5 *xorg-server-extra-1.12.0-4.tar.bz2 6fcb163089f7b78530ee1e145725ffc5 *xorg-server-1.12.0-4-src.tar.bz2 -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: [PATCH] Fix command line arguments for multiple monitors
Jon TURNEY wrote: I'll include this in the next X server build. Thanks! I don't observe this behaviour on my test machine, EnumDisplayMonitor() returns TRUE, so I'd be interested to know what version of Windows you are using. The problem appeared on a Windows 7 machine with two monitors connected. I will run some additional tests to find out what exactly makes the function return FALSE in this case. ciao Jörg -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: cscope -d can't find trailer offset if path contains space (was: vim mlcscope interface issues)
On Tue, Apr 17, 2012 at 2:07 AM, marco atzeri wrote: the easy solution is to not use paths with space in cygwin Not so easy. Cygwin inherits the Windows path, and I have several directories in my Windows PATH with spaces in them. -- Jim Reisert AD1C, jjreis...@alum.mit.edu, http://www.ad1c.us -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: cscope -d can't find trailer offset if path contains space (was: vim mlcscope interface issues)
On 4/18/12, Jim Reisert AD1C jjreis...@alum.mit.edu wrote: On Tue, Apr 17, 2012 at 2:07 AM, marco atzeri wrote: the easy solution is to not use paths with space in cygwin Not so easy. Cygwin inherits the Windows path, and I have several directories in my Windows PATH with spaces in them. -- Jim Reisert AD1C, jjreis...@alum.mit.edu, http://www.ad1c.us -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ -- Thanks Regards, Vivek Agarwal -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
