Re: Unexpected network-traffic
On Thu, 20 Nov 2003, Christian Göbel wrote: What I expect is that X11 causes network traffic when I am connected to a X-server somewhere over a network - but why it causes network traffic without beeing connected to another computer? Is there any (perhaps technical) explanation for that? Yes. X11 can be used over TCP and over Unix Domain Sockets. Unix Domain Sockets is emulated in cygwin with TCP. So X11 in cygwin does always use TCP. You might have noticed that xterm connects to a 127.0.0.0 address which is a local only address. The xserver connects to IN_ADDR_ANY and not to a specific network interface. All network traffic (except the DNS query) is only local. bye ago -- [EMAIL PROTECTED] http://www.gotti.org ICQ: 126018723
Cygwin XFree86 startx Problem
hi... I having problem using startx to startx the X window or X server... here are the error: Chan Seng [EMAIL PROTECTED] ~ $ startx + userclientrc=/home/Chan Seng Loong/.xinitrc + userserverrc=/home/Chan Seng Loong/.xserverrc + sysclientrc=/usr/X11R6/lib/X11/xinit/xinitrc + sysserverrc=/usr/X11R6/lib/X11/xinit/xserverrc + defaultclient=/usr/X11R6/bin/xterm + defaultserver=/usr/X11R6/bin/X + defaultclientargs= + defaultserverargs= + clientargs= + serverargs= + [ -f /home/Chan Seng Loong/.xinitrc ] [: Seng: unknown operand + [ -f /usr/X11R6/lib/X11/xinit/xinitrc ] + defaultclientargs=/usr/X11R6/lib/X11/xinit/xinitrc + [ -f /home/Chan Seng Loong/.xserverrc ] [: Seng: unknown operand + [ -f /usr/X11R6/lib/X11/xinit/xserverrc ] + whoseargs=client + [ x != x ] + [ x = x ] + [ x = x ] + client=/usr/X11R6/lib/X11/xinit/xinitrc + [ x = x ] + [ x = x -a x = x ] + server= + [ x = x ] + XAUTHORITY=/home/Chan Seng Loong/.Xauthority + export XAUTHORITY + removelist= + xinit /usr/X11R6/lib/X11/xinit/xinitrc -- + userresources=/home/Chan Seng Loong/.Xresources + usermodmap=/home/Chan Seng Loong/.Xmodmap + sysresources=/usr/X11R6/lib/X11/xinit/.Xresources + sysmodmap=/usr/X11R6/lib/X11/xinit/.Xmodmap + [ -f /usr/X11R6/lib/X11/xinit/.Xresources ] + [ -f /usr/X11R6/lib/X11/xinit/.Xmodmap ] + [ -f /home/Chan Seng Loong/.Xresources ] [: Seng: unknown operand + [ -f /home/Chan Seng Loong/.Xmodmap ] [: Seng: unknown operand + twm + xclock -geometry 50x50-1+1 + xterm -geometry 80x50+494+51 + xterm -geometry 80x20+494-0 + exec xterm -geometry 80x66+0+0 -name login Fontconfig error: Cannot load default config file Warning: Cannot convert string to type XftFont I tried to fix the probelm using the XF86Config and .xinitrc file. but failed. Can someone help me to solve the problem..? Thanks John __ Do you Yahoo!? Protect your identity with Yahoo! Mail AddressGuard http://antispam.yahoo.com/whatsnewfree
Re: Cygwin XFree86 startx Problem
John, I recommend using startxwin.bat. I don't recommend using startx. With that being said, looks like you are missing the fontconfig and freetype2 packages. Harold Chan Seng Loong wrote: hi... I having problem using startx to startx the X window or X server... here are the error: Chan Seng [EMAIL PROTECTED] ~ $ startx + userclientrc=/home/Chan Seng Loong/.xinitrc + userserverrc=/home/Chan Seng Loong/.xserverrc + sysclientrc=/usr/X11R6/lib/X11/xinit/xinitrc + sysserverrc=/usr/X11R6/lib/X11/xinit/xserverrc + defaultclient=/usr/X11R6/bin/xterm + defaultserver=/usr/X11R6/bin/X + defaultclientargs= + defaultserverargs= + clientargs= + serverargs= + [ -f /home/Chan Seng Loong/.xinitrc ] [: Seng: unknown operand + [ -f /usr/X11R6/lib/X11/xinit/xinitrc ] + defaultclientargs=/usr/X11R6/lib/X11/xinit/xinitrc + [ -f /home/Chan Seng Loong/.xserverrc ] [: Seng: unknown operand + [ -f /usr/X11R6/lib/X11/xinit/xserverrc ] + whoseargs=client + [ x != x ] + [ x = x ] + [ x = x ] + client=/usr/X11R6/lib/X11/xinit/xinitrc + [ x = x ] + [ x = x -a x = x ] + server= + [ x = x ] + XAUTHORITY=/home/Chan Seng Loong/.Xauthority + export XAUTHORITY + removelist= + xinit /usr/X11R6/lib/X11/xinit/xinitrc -- + userresources=/home/Chan Seng Loong/.Xresources + usermodmap=/home/Chan Seng Loong/.Xmodmap + sysresources=/usr/X11R6/lib/X11/xinit/.Xresources + sysmodmap=/usr/X11R6/lib/X11/xinit/.Xmodmap + [ -f /usr/X11R6/lib/X11/xinit/.Xresources ] + [ -f /usr/X11R6/lib/X11/xinit/.Xmodmap ] + [ -f /home/Chan Seng Loong/.Xresources ] [: Seng: unknown operand + [ -f /home/Chan Seng Loong/.Xmodmap ] [: Seng: unknown operand + twm + xclock -geometry 50x50-1+1 + xterm -geometry 80x50+494+51 + xterm -geometry 80x20+494-0 + exec xterm -geometry 80x66+0+0 -name login Fontconfig error: Cannot load default config file Warning: Cannot convert string to type XftFont I tried to fix the probelm using the XF86Config and .xinitrc file. but failed. d Can someone help me to solve the problem..? Thanks John __ Do you Yahoo!? Protect your identity with Yahoo! Mail AddressGuard http://antispam.yahoo.com/whatsnewfree
RE: Cygwin XFree86 startx Problem
With that being said, looks like you are missing the fontconfig and freetype2 packages. No, they just need to enclose long file names with spaces in quotes ... - Henrik
Re: TTF-font rendering not working anymore
Kirk, Somebody needs to give me a three-click test case or I won't even be able to confirm that this is indeed a problem. You do have the fontconfig and freetype2 packages installed on your machine, right? Harold Kirk Erickson wrote: Sorry I didn't report this earlier. I've been plagued by the TTF font problem reported by Fridger Schrempp and Michael Bax and Fridger Schrempp. Perhaps if someone were to review the checkins previous to Michael's reporting the problem (11 Nov 2003), it could be resolved. This is really a showstopper class bug that folks who made recent checkins should be made aware of.
Re: Cygwin XFree86 startx Problem
Henrik, Henrik Schultz wrote: With that being said, looks like you are missing the fontconfig and freetype2 packages. No, they just need to enclose long file names with spaces in quotes ... Not so sure about that. That may fix some of the problems, but what about the last problem in the list: Fontconfig error: Cannot load default config file Warning: Cannot convert string to type XftFont Harold
Re: unable to open the display on local machine
Run startxwin.bat first, then run gv from within the xterm that pops up. Harold Christopher Faylor wrote: On Thu, Nov 20, 2003 at 08:12:56AM +0100, [EMAIL PROTECTED] wrote: Hello, I have installed cygwin localy on a W2K PC. I have installed the package ghostview, using the setup.exe utility. Now, if I try to start ghostview, I type: $ gv I get the error message: gv: Unable to open the display. I tried to set the DISPLAY variable: $setenv DISPLAY localhost:0.0 But the setenv command is not known. So I tried with set: $set DISPLAY localhost:0.0 But this does not seem to do anything. When I echo the variable DISPLAY: $echo $DISPLAY I just get a blank line. Help would be very apreciated. Redirecting to the mailing list devoted to Cygwin/X and shutting down this thread. cgf
Re: Updated: XFree86-xserv-4.3.0-22
Alexander Gottwald wrote: If this is the case I can add code to use the windows default autorepeat settings to configure Xwin. But this will again change the old behavior of Xwin and some users might be unhappy with it. It would be consistent with other behavior to get autorepeat settings from Windows, not from X settings. For example, we try to use the Windows language settings, right? Since Xwin is a Windows application, there's little reason for it to have its own autorepeat configuration. -JT
Keyboard autorepeat settings [Was: Updated: XFree86-xserv-4.3.0-22]
Jack Tanner wrote: Alexander Gottwald wrote: If this is the case I can add code to use the windows default autorepeat settings to configure Xwin. But this will again change the old behavior of Xwin and some users might be unhappy with it. It would be consistent with other behavior to get autorepeat settings from Windows, not from X settings. For example, we try to use the Windows language settings, right? Sort of... it isn't quite that cut and dried. Besides, we have been using *both* X autorepeat and Windows autorepeat until recently. This was not a good solution. Since Xwin is a Windows application, there's little reason for it to have its own autorepeat configuration. It might be nice, but the Windows autorepeat caused problems with systems running in Japanese... so they need the XKB autorepeat functionality, since the Windows autorepeat needs to be disabled for them. So, we can't just remove XKB support or disable it permanently... it is required by some non-U.S. users. It may seems like we are being indecisive here... but there are really a lot of concerns that need to be considered in order to get a correct solution. Harold
Lesstif segmentation fault after cygwin update
I have just updated my cygwin installation, including XFree86 4.3.0-1 and Lesstif 0.93.91-4. My program compiles, but with info messages which I did not get with my previous cygwin installation, as follows: cc -g -I/usr/X11R6/include -o prog.exe callBacks.o draw.o drawingRegion.o drawPrims.o elems2Prims.o fileReading.o inter.o menu.o orient.o readDetails.o savRet.o selection.o util.o vector.o -L/usr/X11R6/lib -lXm -lXt -lSM -lICE -lX11 -lm -lXp -lXext Info: resolving __XmStrings by linking to __imp___XmStrings (auto-import) Info: resolving _XtStrings by linking to __imp__XtStrings (auto-import) Info: resolving _xmDrawingAreaWidgetClass by linking to __imp__xmDrawingAreaWidgetClass (auto-import) Info: resolving _xmBulletinBoardWidgetClass by linking to __imp__xmBulletinBoardWidgetClass (auto-import) Info: resolving _xmSeparatorGadgetClass by linking to __imp__xmSeparatorGadgetClass (auto-import) Info: resolving _xmPushButtonGadgetClass by linking to __imp__xmPushButtonGadgetClass (auto-import) Info: resolving _xmLabelGadgetClass by linking to __imp__xmLabelGadgetClass (auto-import) Info: resolving _xmCascadeButtonGadgetClass by linking to __imp__xmCascadeButtonGadgetClass (auto-import) Info: resolving _xmArrowButtonGadgetClass by linking to __imp__xmArrowButtonGadgetClass (auto-import) When I run, I get a segmentation fault which I traced using gdb to the following functions: #0 0x10032103 in cygX11-6!XGetGCValues () from /cygdrive/c/Program Files/Cygwin/usr/X11R6/bin/cygX11-6.dll #1 0x00513b26 in cygXm-2!_XmArrowBG_TraitAddCallback () from /cygdrive/c/Program Files/Cygwin/usr/X11R6/bin/cygXm-2.dll #2 0x007a5ecc in cygXt-6!XtSetSensitive () from /cygdrive/c/Program Files/Cygwin/usr/X11R6/bin/cygXt-6.dll #3 0x007a64cb in cygXt-6!XtSetValues () from /cygdrive/c/Program Files/Cygwin/usr/X11R6/bin/cygXt-6.dll #4 0x007a5c6f in cygXt-6!XtGetSelectionParameters () from /cygdrive/c/Program Files/Cygwin/usr/X11R6/bin/cygXt-6.dll #5 0x007a5d87 in cygXt-6!XtSetSensitive () from /cygdrive/c/Program Files/Cygwin/usr/X11R6/bin/cygXt-6.dll #6 0x004397d0 in setGraphicsSensitive (status=0 '\0') at util.c:16 #7 0x00401113 in manageSelection (callWidget=0x1015d730, data=0x4421e4, event=0x22fa20) at callBacks.c:69 #8 0x007826b3 in cygXt-6!XtCallCallbackList () from /cygdrive/c/Program Files/Cygwin/usr/X11R6/bin/cygXt-6.dll #9 0x0057744a in cygXm-2!_XmPushBG_TraitAddCallback () from /cygdrive/c/Program Files/Cygwin/usr/X11R6/bin/cygXm-2.dll #10 0x00576275 in cygXm-2!_XmPushB_TraitAddCallback () from /cygdrive/c/Program Files/Cygwin/usr/X11R6/bin/cygXm-2.dll #11 0x005498bf in cygXm-2!_XmDispatchGadgetInput () from /cygdrive/c/Program Files/Cygwin/usr/X11R6/bin/cygXm-2.dll #12 0x005841c4 in cygXm-2!_XmMenuBtnUp () #13 0x007b6f41 in cygXt-6!_XtMatchAtom () from /cygdrive/c/Program Files/Cygwin/usr/X11R6/bin/cygXt-6.dll #14 0x007b73e9 in cygXt-6!_XtMatchAtom () from /cygdrive/c/Program Files/Cygwin/usr/X11R6/bin/cygXt-6.dll #15 0x007b797b in cygXt-6!_XtTranslateEvent () from /cygdrive/c/Program Files/Cygwin/usr/X11R6/bin/cygXt-6.dll #16 0x00790165 in cygXt-6!XtDispatchEventToWidget () from /cygdrive/c/Program Files/Cygwin/usr/X11R6/bin/cygXt-6.dll #17 0x00790c6f in cygXt-6!_XtOnGrabList () from /cygdrive/c/Program Files/Cygwin/usr/X11R6/bin/cygXt-6.dll #18 0x00790ebf in cygXt-6!XtDispatchEvent () from /cygdrive/c/Program Files/Cygwin/usr/X11R6/bin/cygXt-6.dll #19 0x007913e4 in cygXt-6!XtAppMainLoop () from /cygdrive/c/Program Files/Cygwin/usr/X11R6/bin/cygXt-6.dll #20 0x007913a3 in cygXt-6!XtMainLoop () from /cygdrive/c/Program Files/Cygwin/usr/X11R6/bin/cygXt-6.dll #21 0x0041fe43 in _fu292__xmBulletinBoardWidgetClass () at inter.c:62 #22 0x61005018 in forkpty () from /usr/bin/cygwin1.dll #23 0x610052ed in [EMAIL PROTECTED] () from /usr/bin/cygwin1.dll #24 0x0043af71 in cygwin_crt0 () #25 0x0040103c in mainCRTStartup () #26 0x77e814c7 in KERNEL32!GetCurrentDirectoryW () from /cygdrive/c/WINDOWS/system32/kernel32.dll I have tried many things, including a reinstall of all the Cygwin packages, but no luck! I would appreciate any help on how to remedy this problem. Bassam.
Re: Lesstif segmentation fault after cygwin update
Just replying to say that I don't have any ideas. At least you got a reply. Other LessTif users may be able to help you. Harold Izzuddin, Bassam A wrote: I have just updated my cygwin installation, including XFree86 4.3.0-1 and Lesstif 0.93.91-4. My program compiles, but with info messages which I did not get with my previous cygwin installation, as follows: cc -g -I/usr/X11R6/include -o prog.exe callBacks.o draw.o drawingRegion.o drawPrims.o elems2Prims.o fileReading.o inter.o menu.o orient.o readDetails.o savRet.o selection.o util.o vector.o -L/usr/X11R6/lib -lXm -lXt -lSM -lICE -lX11 -lm -lXp -lXext Info: resolving __XmStrings by linking to __imp___XmStrings (auto-import) Info: resolving _XtStrings by linking to __imp__XtStrings (auto-import) Info: resolving _xmDrawingAreaWidgetClass by linking to __imp__xmDrawingAreaWidgetClass (auto-import) Info: resolving _xmBulletinBoardWidgetClass by linking to __imp__xmBulletinBoardWidgetClass (auto-import) Info: resolving _xmSeparatorGadgetClass by linking to __imp__xmSeparatorGadgetClass (auto-import) Info: resolving _xmPushButtonGadgetClass by linking to __imp__xmPushButtonGadgetClass (auto-import) Info: resolving _xmLabelGadgetClass by linking to __imp__xmLabelGadgetClass (auto-import) Info: resolving _xmCascadeButtonGadgetClass by linking to __imp__xmCascadeButtonGadgetClass (auto-import) Info: resolving _xmArrowButtonGadgetClass by linking to __imp__xmArrowButtonGadgetClass (auto-import) When I run, I get a segmentation fault which I traced using gdb to the following functions: #0 0x10032103 in cygX11-6!XGetGCValues () from /cygdrive/c/Program Files/Cygwin/usr/X11R6/bin/cygX11-6.dll #1 0x00513b26 in cygXm-2!_XmArrowBG_TraitAddCallback () from /cygdrive/c/Program Files/Cygwin/usr/X11R6/bin/cygXm-2.dll #2 0x007a5ecc in cygXt-6!XtSetSensitive () from /cygdrive/c/Program Files/Cygwin/usr/X11R6/bin/cygXt-6.dll #3 0x007a64cb in cygXt-6!XtSetValues () from /cygdrive/c/Program Files/Cygwin/usr/X11R6/bin/cygXt-6.dll #4 0x007a5c6f in cygXt-6!XtGetSelectionParameters () from /cygdrive/c/Program Files/Cygwin/usr/X11R6/bin/cygXt-6.dll #5 0x007a5d87 in cygXt-6!XtSetSensitive () from /cygdrive/c/Program Files/Cygwin/usr/X11R6/bin/cygXt-6.dll #6 0x004397d0 in setGraphicsSensitive (status=0 '\0') at util.c:16 #7 0x00401113 in manageSelection (callWidget=0x1015d730, data=0x4421e4, event=0x22fa20) at callBacks.c:69 #8 0x007826b3 in cygXt-6!XtCallCallbackList () from /cygdrive/c/Program Files/Cygwin/usr/X11R6/bin/cygXt-6.dll #9 0x0057744a in cygXm-2!_XmPushBG_TraitAddCallback () from /cygdrive/c/Program Files/Cygwin/usr/X11R6/bin/cygXm-2.dll #10 0x00576275 in cygXm-2!_XmPushB_TraitAddCallback () from /cygdrive/c/Program Files/Cygwin/usr/X11R6/bin/cygXm-2.dll #11 0x005498bf in cygXm-2!_XmDispatchGadgetInput () from /cygdrive/c/Program Files/Cygwin/usr/X11R6/bin/cygXm-2.dll #12 0x005841c4 in cygXm-2!_XmMenuBtnUp () #13 0x007b6f41 in cygXt-6!_XtMatchAtom () from /cygdrive/c/Program Files/Cygwin/usr/X11R6/bin/cygXt-6.dll #14 0x007b73e9 in cygXt-6!_XtMatchAtom () from /cygdrive/c/Program Files/Cygwin/usr/X11R6/bin/cygXt-6.dll #15 0x007b797b in cygXt-6!_XtTranslateEvent () from /cygdrive/c/Program Files/Cygwin/usr/X11R6/bin/cygXt-6.dll #16 0x00790165 in cygXt-6!XtDispatchEventToWidget () from /cygdrive/c/Program Files/Cygwin/usr/X11R6/bin/cygXt-6.dll #17 0x00790c6f in cygXt-6!_XtOnGrabList () from /cygdrive/c/Program Files/Cygwin/usr/X11R6/bin/cygXt-6.dll #18 0x00790ebf in cygXt-6!XtDispatchEvent () from /cygdrive/c/Program Files/Cygwin/usr/X11R6/bin/cygXt-6.dll #19 0x007913e4 in cygXt-6!XtAppMainLoop () from /cygdrive/c/Program Files/Cygwin/usr/X11R6/bin/cygXt-6.dll #20 0x007913a3 in cygXt-6!XtMainLoop () from /cygdrive/c/Program Files/Cygwin/usr/X11R6/bin/cygXt-6.dll #21 0x0041fe43 in _fu292__xmBulletinBoardWidgetClass () at inter.c:62 #22 0x61005018 in forkpty () from /usr/bin/cygwin1.dll #23 0x610052ed in [EMAIL PROTECTED] () from /usr/bin/cygwin1.dll #24 0x0043af71 in cygwin_crt0 () #25 0x0040103c in mainCRTStartup () #26 0x77e814c7 in KERNEL32!GetCurrentDirectoryW () from /cygdrive/c/WINDOWS/system32/kernel32.dll I have tried many things, including a reinstall of all the Cygwin packages, but no luck! I would appreciate any help on how to remedy this problem. Bassam.
Re: twm takes no control
Dai, Dai Itasaka wrote: It is not just Cygwin version of twm. Exactly the same symptom is observed when using a twm on a RedHat or SuSE box managing a cygwin display. It is obvious that it is not twm that is broken. So it is another little issue related to the shared Xt and Xaw libraries. I did a search in the twm sources for Vendor, Shell, VendorShell, etc. but didn't find anything. I am sure that you can probably find info on how the OS/2 guys handled this bug, but searching for OS2 turned up nothing in the twm sources either. I am at a loss. As I said, this is yours to debug further. If twm is the only app that is broken by the shared libs, then I am still not particularly concerned. If it turns out that every other app is broken, or a significant number of other apps are broken, then I will certainly become concerned. Harold
Re: Keyboard autorepeat settings [Was: Updated: XFree86-xserv-4.3.0-22]
Harold L Hunt II wrote: It might be nice, but the Windows autorepeat caused problems with systems running in Japanese... so they need the XKB autorepeat functionality, since the Windows autorepeat needs to be disabled for them. Huh. Not that I'm completely amazed, but it seems strange that Windows would be unable to handle Japanese keyboards. Is this an underlying Windows bug? Perhaps there's some workaround from Microsoft? -JT
Re: twm takes no control
On Thu, 20 Nov 2003, Harold L Hunt II wrote: Dai, Dai Itasaka wrote: It is not just Cygwin version of twm. Exactly the same symptom is observed when using a twm on a RedHat or SuSE box managing a cygwin display. It is obvious that it is not twm that is broken. So it is another little issue related to the shared Xt and Xaw libraries. I did a search in the twm sources for Vendor, Shell, VendorShell, etc. but didn't find anything. I am sure that you can probably find info on how the OS/2 guys handled this bug, but searching for OS2 turned up nothing in the twm sources either. I don't think so, Harold. If this happens with twm run from other OSs, that eliminates twm itself and all its dlls, doesn't it? It must be internal to the Cygwin X server, or its dlls, right? Dai, could you test the inverse? Cygwin's twm controlling a RedHat or SuSE X server? I think that would definately rule out twm and its dlls. I am at a loss. As I said, this is yours to debug further. If twm is the only app that is broken by the shared libs, then I am still not particularly concerned. If it turns out that every other app is broken, or a significant number of other apps are broken, then I will certainly become concerned. I don't have any examples, but to me, the description implies the latter ought to be the case. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444
Re: twm takes no control
Brian, Brian Ford wrote: On Thu, 20 Nov 2003, Harold L Hunt II wrote: Dai, Dai Itasaka wrote: It is not just Cygwin version of twm. Exactly the same symptom is observed when using a twm on a RedHat or SuSE box managing a cygwin display. It is obvious that it is not twm that is broken. So it is another little issue related to the shared Xt and Xaw libraries. I did a search in the twm sources for Vendor, Shell, VendorShell, etc. but didn't find anything. I am sure that you can probably find info on how the OS/2 guys handled this bug, but searching for OS2 turned up nothing in the twm sources either. I don't think so, Harold. If this happens with twm run from other OSs, that eliminates twm itself and all its dlls, doesn't it? It must be internal to the Cygwin X server, or its dlls, right? Hmmm... sounds reasonable. Harold
Re: Keyboard autorepeat settings [Was: Updated: XFree86-xserv-4.3.0-22]
Harold L Hunt II [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED]... Jack Tanner wrote: Alexander Gottwald wrote: If this is the case I can add code to use the windows default autorepeat settings to configure Xwin. But this will again change the old behavior of Xwin and some users might be unhappy with it. It would be consistent with other behavior to get autorepeat settings from Windows, not from X settings. For example, we try to use the Windows language settings, right? Sort of... it isn't quite that cut and dried. Besides, we have been using *both* X autorepeat and Windows autorepeat until recently. This was not a good solution. Since Xwin is a Windows application, there's little reason for it to have its own autorepeat configuration. It might be nice, but the Windows autorepeat caused problems with systems running in Japanese... so they need the XKB autorepeat functionality, since the Windows autorepeat needs to be disabled for them. So, we can't just remove XKB support or disable it permanently... it is required by some non-U.S. users. It seems to me that what is being asked for is that XKB support is kept but its default configuration (delay, repeat rate, etc.) is whatever Windows is currently set to. I think this makes very good since - if I really want a repeat rate different for X applications I can configure it, otherwise it should be the same as it is on all my other Windows apps. From the above comments it looks like Alexander understood this but Harold thought everyone was asking to remove XKB support and go back to using Windows autorepeat. Forgive me if I misread you, Harold. It may seems like we are being indecisive here... but there are really a lot of concerns that need to be considered in order to get a correct solution. Harold Cary
Re: Keyboard autorepeat settings [Was: Updated: XFree86-xserv-4.3.0-22]
Cary, Cary Jamison wrote: It seems to me that what is being asked for is that XKB support is kept but its default configuration (delay, repeat rate, etc.) is whatever Windows is currently set to. I think this makes very good since - if I really want a repeat rate different for X applications I can configure it, otherwise it should be the same as it is on all my other Windows apps. From the above comments it looks like Alexander understood this but Harold thought everyone was asking to remove XKB support and go back to using Windows autorepeat. Forgive me if I misread you, Harold. I think you hit the nail on the head. People are asking for XKB to handle the generation of autorepeat key events, but for it to grab its default settings from the Windows autorepeat settings? Is that what is going on here? Harold
Re: mapping the right mouse button
J S [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED]... I remember seeing recently that there was a fix for mapping the mouse buttons in XFree86. I'm trying to get an application called EMC (which does disk management on MVS) to work with XFree but the problem is the right mouse button doesn't seem to work. It should bring up a menu when I right click on one of the disk images. I found that I could use Shift-F10 instead though and wondered if someone could tell me how to map these keys to the right mouse button? Thanks for any help. Make sure your numlock is off - that has caused similar problems for some people. JS. Cary
Re: unable to open the display on local machine
On Thu, Nov 20, 2003 at 08:12:56AM +0100, [EMAIL PROTECTED] wrote: Hello, I have installed cygwin localy on a W2K PC. I have installed the package ghostview, using the setup.exe utility. Now, if I try to start ghostview, I type: $ gv I get the error message: gv: Unable to open the display. I tried to set the DISPLAY variable: $setenv DISPLAY localhost:0.0 But the setenv command is not known. So I tried with set: $set DISPLAY localhost:0.0 But this does not seem to do anything. When I echo the variable DISPLAY: $echo $DISPLAY I just get a blank line. Help would be very apreciated. Redirecting to the mailing list devoted to Cygwin/X and shutting down this thread. cgf
