AW: AW: 'de' keyboard layout issues
> > > In Windows, all blind keys followed by a space result in that character. > > > Same in XWin, but with one exception: > > > dead-´ plus space gives ' instead of ´. > > > > > > Please check out my patch for that. > > [...] for files /usr/share/x11/locale/iso8859-1/Compose and > /usr/share/x11/locale/iso8859-15/Compose. > > > > > This patch makes sense to me, but doesn't seem to go far enough. Since the > > compose sequences are selected by the locale, this fixes things if > > LANG=de_DE.iso8859-1 or LANG=de_DE.iso8859-15, but not if LANG=de_DE.UTF-8. > > > > I'll try to take another look when I'm back from my holiday :-) > Hi Jon, agreed. But isn't a partial fix better than no fix? 8-) Regards, Paul Compose.patch Description: Binary data -- 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/
AW: AW: AW: AW: AW: Can't paste text or type dead keys when mouse is out of the window
> >>> The problem here is, when running vi in an xterm and the mouse slowly > >>> (unnoticed) > >>> moves over the scrollbar or out of the xterm, and you want to jump to > >>> mark "a, > >>> you need to enter `a, that is in keystrokes > >> > > > >> I'll experiment to see if I can reproduce this effect with my environment. > >> thanks for the detailed explanation. > > > > > > Hi Thomas, > > > > yes, I'm talking about dead keys = compose sequences. > > > > Was it possible to you to reproduce it in your environment? Typing dead key > > ` apostrophe > > then press letter "a" while the mouse pointer is over the scrollbar area of > > an xterm? > > yes - I can reproduce it. Actually once I was made aware of the issue, > I could see in my mind where the problem might lie. But I just verified > it since you reminded me (on one of my Linux machines). > > My idea about the problem is that since xterm has setup translations > (which capture the input) on more than one widget (without appearing to > address this special case), that it might be that there's a better point > in the widget to attach the translations to. > > This was discussed a little late in the #277 cycle to want to hold that > up, so I had in mind to spend some time investigating a solution for it > during #278. > Hi Thomas, I would like to report, that above problem still exists. I tested against xterm-281. Regards, Paul -- 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/
Levovo trackpoint events come delayed (reproducable with xev)
> > - I hold the button down and shift the trackpoint up and down. > > xterm shows no scrolling movement at all. > > - Log in /var/log/xwin/XWin.0.log during this: > > a) still comes at the moment when I shift the trackpoint up and down, > > b) but it doesn't look regular any more: > > There are MUCH more lines > >winMouseButtonsSendEvent: iEventType: 4, iButton: 5, nEvents 2 > >winMouseButtonsSendEvent: iEventType: 5, iButton: 5, nEvents 2 > > and only a few lines > >winWindowProc - WM_MOUSEWHEEL > > in between. > > Looks like this: > > [ 473.447] winMouseButtonsSendEvent: iEventType: 5, iButton: 5, nEvents 2 > > [ 473.447] winMouseButtonsSendEvent: iEventType: 4, iButton: 5, nEvents 2 > > This looks a bit like the trackpoint is sending us a WM_MOUSEWHEEL for a much > larger mouse movement (which we need to break down into multiple button 5 > press/releases) > > > Maybe this is an interesting section, it contains an "EQ overflowing": > > [ 350.612] [mi] EQ overflowing. The server is probably stuck in an > > infinite loop. > > This means that the events are being generated faster than the server can > process them. > > > - I release the button. At the moment when I release the button, the xterm > > jumps to a new position. > > During this, there is absolutely no output to /var/log/xwin/XWin.0.log. > > So it sounds almost like the X server is being prevented from processing X > events until the mouse button is released. > > It might be interesting to try as separate test with some application which > constantly draws to it's window (like ico), if that continues drawing when the > trackpoint button is down. Hi Jon, here a log of my recent tests. The most interesting point is the last. 1. I modified file C:\Program Files\Synaptics\SynTP\TP4table.dat according to new FAQ and reboot PC. -> No change of behaviour. 2. Download XWin.20120129-git-45e67e363e19a481.exe.bz2. /bin/startxwin -- /bin/XWin.20120129-git-45e67e363e19a481.exe -logverbose 3 -clipboard -emulate3buttons 100 -nounixkill -nowinkill -xkboptions nbsp:level3 -> Doesn't start. Error message on the console is: giving up. /bin/startxwin: No such file or directory (errno 2): unable to connect to X server /bin/startxwin: No such process (errno 3): Server error. -> No output at all to file /var/log/xwin/XWin.0.log. 3. I took above startxwin command line and replace XWin.20120129-git-45e67e363e19a481.exe by XWin.20110803-git-a493c0465e56ce0b.exe -> Immediately starts. All further tests with (old) XWin.20110803-git-a493c0465e56ce0b.exe. 4. Today I couldn't get to the broken, jumpy behaviour by scrolling a Windows dialog. So this is not the breaking condition as I previously meant. But after some time, the scrolling behaviour breaks and xterm scrolls in jumpy way. Sorry, I have no glue what's the condition that breaks it. After reboot of PC it scrolls fine. Any work of 1 minute or so seems to break smooth scrolling. 5. Then I started ico. -> While ico runs, xterm scrolls fine and smooth. As soon as I stop ico, xterm scrolls jumpy. -> Pressing the trackpoint button has no effect to ico. It keeps painting fine eather way. 6. I started ico with -sleep 1 ico -sleep 1 I constantly hold the trackpoint button down and scroll the xterm. -> I observe jump scrolling movements every second, one jump each second. xterm jump scrolls exactly at the time when ico refreshes 7. close ico, start xpdf -> xpdf and xterm both have broken = jumpy scroll 8. start ico -> both xpdf and xterm both scroll fine and smooth 9. stop ico, start ico -sleep 1 -> ico -sleep 1 starts, but doesn't paint anything. I do several tests. -> ico without sleep option starts fine. close xpdf -> ico -sleep 1 starts, but doesn't paint anything. I do several tests. -> ico without sleep option starts fine. -> ico -sleep 1 starts and repaints in 1 second rhythm. Fine. => an open xpdf seems to break "ico -sleep 1", and "ico -sleep 1" can be repaired by closing xpdf and then once running "ico" without options. Very weird. > > > > 2. Download XWin.20120129-git-45e67e363e19a481.exe.bz2. > > > /bin/startxwin -- /bin/XWin.20120129-git-45e67e363e19a481.exe > > > -logverbose 3 - > clipboard - > > emulate3buttons 100 -nounixkill -nowinkill > > > -xkboptions nbsp:level3 > > >-> Doesn't start. Error message on the console is: > > > > > > giving up. > > > /bin/startxwin: No such file or directory (errno 2): unable to connect > > > to X server > > > /bin/startxwin: No such process (errno 3): Server error. > > > > > >-> No output at all to file /var/log/xwin/XWin.0.log. > > > > Possibly you need to 'chmod +x /bin/XWin.20120129-git-45e67e363e19a481.exe' > > > > -- > > Jon TURNEY > > Volunteer Cygwin/X X Server maintainer > > > Hi Jon, > > x bit was set: > > $ls -lg *.exe > -r-xr-xr-x+ 1 13762945 02.02.2012 19.3
possible to run XWin as windows service?
Hi, I would like to start XWin automatically on Windows startup (Windows user login). I couldn't find any hint in the manual. Is it possible to run (and automatically start) XWin as windows service? I tried these attempts, but they don't work: sc create testabc1 binpath= "D:\Programme\cygwin\bin\startxwin.exe -- /bin/XWin -clipboard -emulate3buttons 100 -nounixkill -nowinkill -xkboptions nbsp:level3" displayname= "testabc1" start= demand sc create testabc2 binpath= "D:\Programme\cygwin\bin\XWin.exe -clipboard -emulate3buttons 100 -nounixkill -nowinkill -xkboptions nbsp:level3" displayname= "testabc2" start= demand ... they all come with the same error message on startup: sc start testabc2 [SC] StartService FEHLER 1053: Der Dienst antwortete nicht rechtzeitig auf die Start- oder Steuerungsanforderung. Thank you very much for ideas! Regards, Paul -- 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/
AW: possible to run XWin as windows service?
> > I would like to start XWin automatically on Windows startup (Windows user > > login). > > I couldn't find any hint in the manual. > > > > Is it possible to run (and automatically start) XWin as windows service? > > Possible? Yes. > [...] > > Running it from the "Startup" program group is the correct approach. > Hi Jon, running it from the Startup program group worked fine as long as my ~/.startxwinrc has been empty. But I had to add the line /bin/ico -r -obj cube -sleep .05 & to ~/.startxwinrc to fix http://cygwin.com/ml/cygwin-xfree/2012-07/msg00012.html That workaround is perfect, but as a side effect, startxwin won't terminate any more; it blocks as long ico runs, and ico runs forever, so startxwin never terminates. This results in an annoying task bar entry staying there all day. This X Server task bar entry is (obviously) not being attached to any visible window or application, so this entry shouldn't exist in the task bar. Can you recommend me how to start the X Server without getting a task bar entry? Thank you & regards, Paul -- 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/
typo in "man xterm"
Hi, the word "not" should be added to this description: man xterm [...] +maximized This option indicates that xterm should ask the window manager to maximize its layout on startup. It should read: ... should *not* ask the window manager ... Regards, Paul -- 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/
"xterm -si" doesn't hold the line
Hi, xterm -si doesn't work as expected. To reproduce (think of a "tail -f" instead of xev): 1. xterm -si -e /bin/xev 2. move the mouse in the xev window to produce some lines 3. scroll the xterm up half way and remember the visible lines 4. while looking at the xterm, again move the mouse in the xev window You see: xterm scrolls slowly down. I would expect xterm to hold the current view while xev produces more lines at the end. Suppose you have a "tail -f" running and scroll the xterm up to view a specific line. I would expect that line to stay visible until I scroll somewhere else. But it's not: as the "tail -f" produces output, the xterm scrolls slowly down. To clarify: xterm does not scroll down to the very end but it scrolls down line by line, as if xterm would try to keep the same distance between the current scrolling position and the most recent line. I would expect xterm to keep the same distance between the current scrolling position and the *FIRST* line. In case above behaviour is the desired behaviour, I wanted to suggest another command line option like "-si-top" for my use case. Regards, Paul -- 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/
AW: typo in "man xterm"
> > Hi, > > > > the word "not" should be added to this description: > > > > > > man xterm > >[...] > >+maximized > >This option indicates that xterm should ask the window > > manager to > maximize its layout on startup. > > > > > > It should read: > > ... should *not* ask the window manager ... > > The immediate call is made via the X server, but the window manager > is in control of the subsequent reconfiguration requests, and as > a result can keep xterm's window from changing size. To simplify > the manpage, xterm does "ask". > Hi Thomas, so what is the difference between options "+maximized" and "-maximized"? The behaviour is different: one maximizes, the other not, but the descriptions in the man page are exactly the same. I still think the word "not" should be added to the description of "+maximized" to match the behaviour of this option. Regards, Paul -- 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/
AW: AW: possible to run XWin as windows service?
> > The cygwin program run.exe is designed to do just that. > It's what I use for this purpose :-) ... > Hi Eliot, thank you for your input. 8-) I was using run.exe too. run.exe used to hide the window and the task bar entry. But since my upgrade from Cygwin 1.7.9 to 1.7.15, run.exe only hides the window but not the task bar entry, when invoked from the Startup menu in some cases. This seems buggy, see my thread: http://cygwin.com/ml/cygwin/2012-07/msg00473.html But I don't have the impression that a developer accepted this as bug. Do you have a suggestion how to avoid this situation? Regards, Paul -- 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/
clipboard integration doesn't work
Hi, I have problems with my clipboard integration. When I select something in X, the Windows clipboard gets cleared, so there is some interaction between X' and Windows' clipboards. But no data is transferred from X to Windows or vice versa. I am running cygwin-1.7.7-1 (downloaded 2010-11-02) on a Windows XP SP 3. I am starting X with: /bin/startxwin -- /bin/XWin -emulate3buttons 100 I also tried to add an explicit -clipboard parameter, but that doesn't change anything. (According to the man page of XWin, -clipboard is set by default.) Does anybody have an advice? Thanks a lot! Paul -- 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/
AW: clipboard integration doesn't work
Hi Jon, thanks for giving your attention to this. 8-) > Can you give a detailed set of reproduction steps e.g. what > application are > your cutting from, pasting to? It is reproducable in both directions (Win -> X, X -> Win), with any application on both sides. So I choose a xterm with a vim for X, and a notepad for Windows. /bin/startxwin -- /bin/XWin -emulate3buttons 100 -logverbose 3 As a setup I type "eins-zwei-drei" into X's vim, and "hallo" into the notepad. Then I select the "eins-zwei-drei" text in X. Then I select the "hallo" text in the notepad and press CONTROL C. Effect: the highlighting of the text "eins-zwei-drei" in vim/X disappears immediately. Then in both editors I open a new line and paste the text of the clipboard in it. In vim/X it pastes "eins-zwei-drei" (using both mouse keys via middle mouse button emulation). In notepad it pasts "hello" (using CONTROL V). Then I close both editors, kill XWin and get the Log. -> See Log 1 (attached). Now for the other direction: /bin/startxwin -- /bin/XWin -emulate3buttons 100 -logverbose 3 As a setup I again type "eins-zwei-drei" into X's vim, and "hallo" into a notepad. Then I select the "hallo" text in the notepad and press CONTROL C. I press CONTROL V several times to verify that I have selected something. Notepad pastes: "hallo". Then I select the "eins-zwei-drei" text in X/vim. I check out the result: I go back to the notepad and continue to press CONTROL V: nothing gets pasted any more. I go to the X/vim window, open a new vim line and (using both mouse keys via middle mouse button emulation) I check what gets pasted: "eins-zwei-drei". Then I close both editors, kill XWin and get the Log. -> See Log 2 (attached). In both logs I found the name of my PC and my user name, and I replaced that information by XXX. > Are you running any Windows programs which continuously > monitor the clipboard > like 'Clipbook Viewer', VNC client, etc.? Sorry, I don't know these programs. Regards, Paul. -- 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/
AW: AW: clipboard integration doesn't work
> As a workaround, you could perhaps set your locale to > de_DE.ISO8859-1 (which > is a subset of CP1252), if you actually need to work with > CP1252 encoded data, Hi Jon, that WORKS!! 8-))) Thanks for the help. It's fine for me now. Paul -- 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/
X doesn't start for user without admin rights
Hi, X starts fine under a user with local administrator rights. When logged in to the same machine with another user that has no admin rights, X won't start. The log indicates that another X were already running, but it's not. Output on the console is: giving up. /bin3/startxwin: Connection refused (errno 111): unable to connect to X server /bin3/startxwin: No such process (errno 3): Server error. Log attached. Thanks for help! Regards, Paul XWin.0.log Description: Binary data -- 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/
AW: X doesn't start for user without admin rights
Hi Jon, great help, yes the problem is related to /tmp/.X11-unix/X0 and /tmp/.X0-lock. When these files are not present, the underpriviledged user can start X fine. The situation is now as follows: SCENARIO 1: Log in as administrator. Start X. Reboot PC and log in as normal user. -> The files are present. => The normal user can't start X. SCENARIO 2: Log in as administrator. Start X. Manually shut down X by double-clicking on the X-icon in the taskbar (near the clock). Reboot PC and log in as normal user. -> The files are not present. => The normal user can start X. It seems that on reboot of the PC, X doesn't shut down properly, and instead just gets killed. I played around with the access rights of the /tmp dir: I gave everybody (world) full rights. But that doesn't help because the files get their own ACL when they are (re)created. So currently the administrator is required to not forget to manually shut down his X server, otherwise normal users can't start X. Cygwin and Cygwin/X are great products, BTW. With kind regards, Paul. -- 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/
I lose characters because keycode of Fn is same than DEL
Hi, on a a IBM Lenovo Laptop T60 there is a "Fn" key to adjust the screen brightness and such. That "Fn" key has the same keycode than the DEL key. Therefore I can't change the Fn key with xmodmap (because I would change the DEL key the same way.) When I adjust the screen brightness, I lose characters in the editor. Unfortunately the Fn key REPEATS firing delete while the key is pressed. And several times I didn't notice the loss before saving and leaving the editor. Here is the output of xev when I press the Fn key: (Pressing the DEL key would yield the very same output.) KeyPress event, serial 20, synthetic NO, window 0xa1, root 0x101, subw 0xa2, time 42594031, (35,42), root:(259,282), state 0x0, keycode 107 (keysym 0x, Delete), same_screen YES, XLookupString gives 1 bytes: (7f) "<7f>" XFilterEvent returns: False What can we do? Thank you! Paul -- 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/
AltGr key mostly fires an additional CONTROL key
Hi Jon, another issue with the keyboard on a Lenovo T60 (Windows XP) and Lenovo T510 (Windows 7). The AltGr key mostly fires and locks (!) an additional CONTROL key press. This makes the AltGr key basically inusable (and a xmodmap workaround is not possible). The AltGr key is a modifier key e. g. needed to get the @ sign (AltGr + Q) on a German keyboard. This is, what I found out on this issue: This is the output of xev when that occured. I pressed AltGR+Q once and released it again. Then (without any other modifier key pressed) I hit once a normal A. As you can see, instead of a @ I get a CONTROL-@ (= control character 00) and instead of an a I get a CONTROL-A (= control character 01). xev logs out very clear that there is an additionally (unwanted) KeyPress for key 37 = CONTROL_L. There is no KeyRelease for the keycode 37 = CONTROL_L in the log: KeyPress event, serial 23, synthetic NO, window 0xa1, root 0x101, subw 0xa2, time 32794468, (47,57), root:(73,99), state 0x10, keycode 113 (keysym 0xfe03, ISO_Level3_Shift), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False KeyPress event, serial 23, synthetic NO, window 0xa1, root 0x101, subw 0xa2, time 32795046, (47,57), root:(73,99), state 0x90, keycode 37 (keysym 0xffe3, Control_L), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False KeyPress event, serial 23, synthetic NO, window 0xa1, root 0x101, subw 0xa2, time 32795531, (47,57), root:(73,99), state 0x94, keycode 24 (keysym 0x40, at), same_screen YES, XLookupString gives 1 bytes: (00) "" XFilterEvent returns: False KeyRelease event, serial 23, synthetic NO, window 0xa1, root 0x101, subw 0xa2, time 32795640, (47,57), root:(73,99), state 0x94, keycode 24 (keysym 0x40, at), same_screen YES, XLookupString gives 1 bytes: (00) "" XFilterEvent returns: False KeyRelease event, serial 23, synthetic NO, window 0xa1, root 0x101, subw 0xa2, time 32798390, (47,57), root:(73,99), state 0x94, keycode 113 (keysym 0xfe03, ISO_Level3_Shift), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False KeyPress event, serial 23, synthetic NO, window 0xa1, root 0x101, subw 0xa2, time 32799890, (47,57), root:(73,99), state 0x14, keycode 38 (keysym 0x61, a), same_screen YES, XLookupString gives 1 bytes: (01) "" XFilterEvent returns: False KeyRelease event, serial 23, synthetic NO, window 0xa1, root 0x101, subw 0xa2, time 32800015, (47,57), root:(73,99), state 0x14, keycode 38 (keysym 0x61, a), same_screen YES, XLookupString gives 1 bytes: (01) "" XFilterEvent returns: False The ISO_Level3_Shift without the additional Control_L (left control key) would be the expected behaviour. It happens quite often (but I couldn't find the rule behind), pressing the AltGr ONCE also LOCKS the Control_L key in a way that if you later press a normal letter, say: a normal c, you get a CONTROL-C into the application. The Control_L (left control key) stays locked until you press the real CONTROL key. Meanwhile XWin.0.log logs out this: [ 32804,781] winSendKeyEvent: dwKey: 105, fDown: 1, nEvents 2 [ 32805,984] winTranslateKey: wParam 0011 lParam e01d0001 [ 32805,984] winSendKeyEvent: dwKey: 29, fDown: 0, nEvents 2 [ 32805,984] winTranslateKey: wParam 0012 lParam c1380001 [ 32805,984] winSendKeyEvent: dwKey: 105, fDown: 0, nEvents 2 [ 32809,859] winTranslateKey: wParam 0041 lParam 001e0001 [ 32809,859] winSendKeyEvent: dwKey: 30, fDown: 1, nEvents 2 [ 32809,968] winTranslateKey: wParam 0041 lParam c01e0001 [ 32809,968] winSendKeyEvent: dwKey: 30, fDown: 0, nEvents 2 Key 29 seems to be the stuck control key. To emphasize again, I didn't press the control key on my keyboard. I just pressed AltGr Q (in the intention to get a @), released it again, then I pressed "a". Greetings, Paul -- 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/
AW: AW: AltGr key mostly fires an additional CONTROL key
> Thanks for the logs, that was very useful. > > I still can't reproduce this (although holding AltGr down to make it > autorepeat seems the best way to try to do that). It is a timing issue with > the keypress/release messages so it might be sensitive to CPU speed, or > perhaps you have some software installed which looks at keypress/release > messages and changes the timing? > > I've had a go at fixing it. Can you please try the build I've uploaded at [1] > and see if it still shows the problem for you? > > [1] ftp://cygwin.com/pub/cygwinx/XWin.20110803-git-a493c0465e56ce0b.exe.bz2 Hi Jon, works fine for me. I Played around quite a while, but the CONTROL-locking didn't occur any more. Yippie! Is it ok, if I leave the hotfix file permanently in on my PC (I mean, did you base it on a recent XWin released version with just my bug fix in - or is there other experimental stuff inside?), then I'll use it automatically during work and I can let you know in case of problems. I wouldn't have started a thread with the following, but since we have already started looking at this keyboard, maybe you are interested in some of these: Tilde sign (~) should be a normal (not a blind) key. In Windows I hit AltGr+"+" to get ~, in XWin I need to type AltGr+"+" then space to get a ~. See attachment for the initial XWin xmodmap -pke table. Possible xmodmap correction (works fine): keycode 35 = plus asterisk plus asterisk asciitilde Euro Currency sign doesn't work. I know - it's not a latin1 character, but together with CP1252 this xmodmap correction works like Windows: keycode 26 = e E e E 0x0080 ALT+Space produces a NBSP character (HEX A0) in Windows, but not in XWin. xmodmap correction is unfortunately not possible, because the xmodmap setting on ISO_Level3_Shift+Space is just thrown away: Something like keycode 65 = space NoSymbol space NoSymbol nobreakspace or keycode 65 = space space space space nobreakspace doesn't work: it's discarded and the setting is not shown on a "xmodmap -pke". So I put nobreakspace to the fifth place of another key - there it works. That would be good if key 65 (space key) would accept above xmodmap setting or have it initially. Number block is not working. See attachment for the initial XWin xmodmap -pke table (all these KP_* settings look good at the first sight, but the keys don't produce numbers). Possible xmodmap correction (works fine): keycode 63 = asterisk asterisk keycode 79 = 7 7 keycode 80 = 8 8 keycode 81 = 9 9 keycode 82 = minus minus keycode 83 = 4 4 keycode 84 = 5 5 keycode 85 = 6 6 keycode 86 = plus plus keycode 87 = 1 1 keycode 88 = 2 2 keycode 89 = 3 3 keycode 90 = 0 0 keycode 91 = period period keycode 108 = Return Return keycode 112 = slash slash Regards, Paul keycode 8 = keycode 9 = Escape NoSymbol Escape keycode 10 = 1 exclam 1 exclam onesuperior exclamdown onesuperior keycode 11 = 2 quotedbl 2 quotedbl twosuperior oneeighth twosuperior keycode 12 = 3 section 3 section threesuperior sterling threesuperior keycode 13 = 4 dollar 4 dollar onequarter currency onequarter keycode 14 = 5 percent 5 percent onehalf threeeighths onehalf keycode 15 = 6 ampersand 6 ampersand notsign fiveeighths notsign keycode 16 = 7 slash 7 slash braceleft seveneighths braceleft keycode 17 = 8 parenleft 8 parenleft bracketleft trademark bracketleft keycode 18 = 9 parenright 9 parenright bracketright plusminus bracketright keycode 19 = 0 equal 0 equal braceright degree braceright keycode 20 = ssharp question ssharp question backslash questiondown U1E9E keycode 21 = dead_acute dead_grave dead_acute dead_grave dead_cedilla dead_ogonek dead_cedilla keycode 22 = BackSpace NoSymbol BackSpace keycode 23 = Tab ISO_Left_Tab Tab ISO_Left_Tab keycode 24 = q Q q Q at Greek_OMEGA at keycode 25 = w W w W lstroke Lstroke lstroke keycode 26 = e E e E EuroSign EuroSign EuroSign keycode 27 = r R r R paragraph registered paragraph keycode 28 = t T t T tslash Tslash tslash keycode 29 = z Z z Z leftarrow yen leftarrow keycode 30 = u U u U downarrow uparrow downarrow keycode 31 = i I i I rightarrow idotless rightarrow keycode 32 = o O o O oslash Oslash oslash keycode 33 = p P p P thorn THORN thorn keycode 34 = udiaeresis Udiaeresis udiaeresis Udiaeresis dead_diaeresis dead_abovering dead_diaeresis keycode 35 = plus asterisk plus asterisk dead_tilde dead_macron dead_tilde keycode 36 = Return NoSymbol Return keycode 37 = Control_L NoSymbol Control_L keycode 38 = a A a A ae AE ae keycode 39 = s S s S U017F U1E9E U017F keycode 40 = d D d D eth ETH eth keycode 41 = f F f F dstroke ordfeminine dstroke keycode 42 = g G g G eng ENG eng keycode 43 = h H h H hstroke Hstroke hstroke keycode 44 = j J j J dead_belowdot dead_abovedot dead_belowdot keycode 45 = k K k K kra ampersand kra keycode 46 = l L l L lstroke Lstroke lstroke keycode 47 = odiaeresis Odiaeresis odiaeresis Odiaeresis d
XWin -ignoremousewheelpress
Hi Jon, maybe you are interested in this idea: The wheel of a wheel mouse also working as middle mouse button can be quite annoying, when you accidently paste lots of lines into an xterm while scrolling up and down. I thought an option -ignoremousewheelpress to XWin would be a great enhancement. Scrolling were possible, but clicking the wheel were ignored. (Using it would only make sense together with -emulate3buttons.) Luckily I found another mouse driver which allowed me to diable this directly on Windows, so it's fine for me, but such a mouse driver might not be available for all mice. Regards, Paul -- 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/
xterm: scrollbar bug
Hi, I wanted to ask if it's already known, with which release xterm's scrollbar bug will be resolved. Thanks! Paul -- 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/
Can't paste text or type blind keys when mouse is out of the window
Hi, when xterm has keyboard focus, but mouse pointer is outside of the window (or even on Window's blue title bar): - all blind keys are ignored: o instead of 'à' (key '`' then 'a') you get just a normal 'a' o can't type '^' character (on a German keyboard done with blind '^' key then space) -> you will just get the space instead o same with '`' or '´': all blind keys are affected - can't paste text with the mouse - all other keys work as expected Effect: - While working and not noticing that the mouse pointer slowly left the window, in vi you want to jump to mark a (typing `a). '`' is ignored and the 'a' brings vi into append mode! - typing something like ":%s/^xxx/yyy/" is annoying, because you can't type ^, until you reposition the mouse pointer inside the window 100 % reproducable. When the mouse pointer is inside the xterm, everything works fine: you get à or ^ and can paste text. It makes no difference whether I use XWin.20110803-git-a493c0465e56ce0b or XWin.exe from the release. Logs of xev and XWin.log (with -logverbose 3) are in the attachment. The XWin.logs are the same regardless if mouse is inside or outside, but I notice a small difference in xev's output. Thanks & regards, Paul KeyPress event, serial 23, synthetic NO, window 0xa1, root 0x101, subw 0x0, time 6034149, (-65,-31), root:(1064,196), state 0x0, keycode 49 (keysym 0xfe52, dead_circumflex), same_screen YES, XLookupString gives 1 bytes: (5e) "^" XFilterEvent returns: False KeyRelease event, serial 23, synthetic NO, window 0xa1, root 0x101, subw 0x0, time 6034243, (-65,-31), root:(1064,196), state 0x0, keycode 49 (keysym 0xfe52, dead_circumflex), same_screen YES, XLookupString gives 1 bytes: (5e) "^" XFilterEvent returns: False KeyPress event, serial 23, synthetic NO, window 0xa1, root 0x101, subw 0x0, time 6035631, (-65,-31), root:(1064,196), state 0x0, keycode 65 (keysym 0x20, space), same_screen YES, XLookupString gives 1 bytes: (20) " " XFilterEvent returns: False KeyRelease event, serial 23, synthetic NO, window 0xa1, root 0x101, subw 0x0, time 6035741, (-65,-31), root:(1064,196), state 0x0, keycode 65 (keysym 0x20, space), same_screen YES, XLookupString gives 1 bytes: (20) " " XFilterEvent returns: False [ 5642.306] winTranslateKey: wParam 00dc lParam 00290001 [ 5642.306] winSendKeyEvent: dwKey: 41, fDown: 1, nEvents 2 [ 5642.353] winTranslateKey: wParam 00dc lParam c0290001 [ 5642.353] winSendKeyEvent: dwKey: 41, fDown: 0, nEvents 2 [ 5643.944] winTranslateKey: wParam 0020 lParam 00390001 [ 5643.944] winSendKeyEvent: dwKey: 57, fDown: 1, nEvents 2 [ 5644.053] winTranslateKey: wParam 0020 lParam c0390001 [ 5644.053] winSendKeyEvent: dwKey: 57, fDown: 0, nEvents 2 KeyPress event, serial 20, synthetic NO, window 0xa1, root 0x101, subw 0xa2, time 6030249, (49,37), root:(1178,264), state 0x0, keycode 49 (keysym 0xfe52, dead_circumflex), same_screen YES, XLookupString gives 1 bytes: (5e) "^" XFilterEvent returns: False KeyRelease event, serial 23, synthetic NO, window 0xa1, root 0x101, subw 0xa2, time 6030359, (49,37), root:(1178,264), state 0x0, keycode 49 (keysym 0xfe52, dead_circumflex), same_screen YES, XLookupString gives 1 bytes: (5e) "^" XFilterEvent returns: False KeyPress event, serial 23, synthetic NO, window 0xa1, root 0x101, subw 0xa2, time 6031638, (49,37), root:(1178,264), state 0x0, keycode 65 (keysym 0x20, space), same_screen YES, XLookupString gives 1 bytes: (20) " " XFilterEvent returns: False KeyRelease event, serial 23, synthetic NO, window 0xa1, root 0x101, subw 0xa2, time 6031747, (49,37), root:(1178,264), state 0x0, keycode 65 (keysym 0x20, space), same_screen YES, XLookupString gives 1 bytes: (20) " " XFilterEvent returns: False [ 5627.268] winTranslateKey: wParam 00dc lParam 00290001 [ 5627.268] winSendKeyEvent: dwKey: 41, fDown: 1, nEvents 2 [ 5627.346] winTranslateKey: wParam 00dc lParam c0290001 [ 5627.346] winSendKeyEvent: dwKey: 41, fDown: 0, nEvents 2 [ 5628.968] winTranslateKey: wParam 0020 lParam 00390001 [ 5628.984] winSendKeyEvent: dwKey: 57, fDown: 1, nEvents 2 [ 5629.093] winTranslateKey: wParam 0020 lParam c0390001 [ 5629.093] winSendKeyEvent: dwKey: 57, fDown: 0, nEvents 2 -- 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/
AW: 'de' keyboard layout issues (Re: AW: AW: AltGr key mostly fires an additional CONTROL key)
Hi Jon, 1. Tilde sign - > > Tilde sign (~) should be a normal (not a blind) key. > >In Windows I hit AltGr+"+" to get ~, in XWin I need to type AltGr+"+" > > then space to > get a ~. > >See attachment for the initial XWin xmodmap -pke table. > >Possible xmodmap correction (works fine): > >keycode 35 = plus asterisk plus asterisk asciitilde > > This is a can of worms I don't want to open :-) > > At the moment, in the 'de' layout, the tilde deadkey will add a macron > diacritic, e.g. AltGr + "+" + a = ã. > > I really lack the expertise to determine if this is a bug in xkeyboard-config > (if this german keyboard behavior is something no german keyboard user would > ever expect or want) > > The xkb configurations we use come from the xkeyboard-config project, and > aren't trying to be identical to Windows, but to conform to the appropriate > national standards and user expectations. > > However, I can see in the case of XWin this is problematic, as it will be > confusing to switch between X and normal Windows windows which have different > keyboard behavior. I did some research: German computer keyboard layout is defined in DIN 2137-2. And to my surprise I found, that tilde is a dead key there. That means, that the xkeyboard-config project perfectly matches the DIN norm, while Windows (where the key is not dead) does not match it. So I understand, that you may want to stick to the DIN norm. A workaround for guys like me, who want the XWin keyboard work the same like Windows, is possible with xmodmap, so yeah ... let's close this point. 2. Euro currency sign - > > Euro Currency sign doesn't work. > >I know - it's not a latin1 character, but together with CP1252 this > > xmodmap > correction works like Windows: > >keycode 26 = e E e E 0x0080 > > I guess this is another symptom of Xlib not understanding the de_DE.CP1252 > locale. > This works fine in the de_DE.UTF-8 locale. I agree to concentrate on more important stuff. 3. Non breaking space (NBSP) on ALT+space - > > ALT+Space produces a NBSP character (HEX A0) in Windows, but not in XWin. > >xmodmap correction is unfortunately not possible, because the xmodmap > > setting on > ISO_Level3_Shift+Space is just thrown away: > >Something like > >keycode 65 = space NoSymbol space NoSymbol nobreakspace > >or > >keycode 65 = space space space space nobreakspace > >doesn't work: it's discarded and the setting is not shown on a "xmodmap > > -pke". > >So I put nobreakspace to the fifth place of another key - there it works. > >That would be good if key 65 (space key) would accept above xmodmap > > setting or have > it initially. > > Reading [1], this looks like an (undocumented) Windows-ism > > http://en.wikipedia.org/wiki/Non-breaking_space#Keyboard_entry_methods I found out, that DIN 2137-2:2003-09 defines two different keyboard layouts, the one having ALT+space undefinied (the common layout with an extra "<"/">" key left to the y key; see page 27 of that DIN norm), the other one defining ALT+space as NBSP (see page 9 of that DIN norm, table 2, line 1). So it's fine, that ALT+space is undefined by default. But it wouldn't harm anybody, if ALT+space were xmodmap redefinable, so that those guys, who got used to using ALT+space in Windows, have a chance to xmodmap it themselves. And: for all other keys you can xmodmap what you like on ALT+key, so why not for ALT+space? I can easily xmodmap the NBSP onto another key, but if you try to do the same with the space key, XWin doesn't take it: Try xmodmapping keycode 65 = space NoSymbol space NoSymbol nobreakspace or keycode 65 = space space space space nobreakspace then issue a "xmodmap -pke" ... and the NBSP is not on the space key. 4. Number block --- > I can't reproduce this problem. > > I wonder if this is a problem with handling numpad overlaid onto normal keys > on a laptop keypad? Again, -logverbose 3 output together with xev output > would be helpful. That was referring to plugging an external (USB) keyboard to the Laptop. I got a new external keyboard recently. The number block was not working with my old external keyboard, but with the new one I can't reproduce the problem, with other words, it is working there. Unfortunately I don't have the old keyboard any more, so I can't help you debugging this issue. Maybe somebody else calls. Regards, Paul -- 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/
AW: 'de' keyboard layout issues (Re: AW: AW: AltGr key mostly fires an additional CONTROL key)
> > 1. Tilde sign > > - > > > >>> Tilde sign (~) should be a normal (not a blind) key. > >>> In Windows I hit AltGr+"+" to get ~, in XWin I need to type AltGr+"+" > >>> then space > to > >> get a ~. > >>> See attachment for the initial XWin xmodmap -pke table. > >>> Possible xmodmap correction (works fine): > >>> keycode 35 = plus asterisk plus asterisk asciitilde > >> > >> This is a can of worms I don't want to open :-) > > In case it wasn't clear, the can of worms here is ensuring that XWin selects a > keyboard layout which matches the Windows one in all cases. > > >> At the moment, in the 'de' layout, the tilde deadkey will add a macron > >> diacritic, e.g. AltGr + "+" + a = ã. > > Obviously I meant to write 'tilde diacritic' here :-) > > >> I really lack the expertise to determine if this is a bug in > >> xkeyboard-config > >> (if this german keyboard behavior is something no german keyboard user > >> would > >> ever expect or want) > >> > >> The xkb configurations we use come from the xkeyboard-config project, and > >> aren't trying to be identical to Windows, but to conform to the appropriate > >> national standards and user expectations. > >> > >> However, I can see in the case of XWin this is problematic, as it will be > >> confusing to switch between X and normal Windows windows which have > >> different > >> keyboard behavior. > > > > I did some research: German computer keyboard layout is defined in DIN > > 2137-2. > > And to my surprise I found, that tilde is a dead key there. > > That means, that the xkeyboard-config project perfectly matches the DIN > > norm, > > while Windows (where the key is not dead) does not match it. > > So I understand, that you may want to stick to the DIN norm. > > Usability comes before standards compliance :-) > > > A workaround for guys like me, who want the XWin keyboard work the same > > like Windows, > > is possible with xmodmap, so yeah ... let's close this point. > > Doing some more research, I found an upstream bug [1], which seems to make the > opposite claim about DIN 2137-2(1998) > > I also discovered that the nodeadkeys variant of the de layout was at one > stage the default used by XWin when a German Windows keyboard layout was > reported [2] > > Maybe the 'correct' solution is possibly to create a 'nodeadtilde' variant of > the de layout in xkeyboard-config, and then to arrange for that to be the > default used by XWin when Windows reports a German keyboard layout. > > Perhaps you'd like to try the attached patch to /usr/share/X11/xkb/symbols/de, > which adds a nodeadtilde variant, which you can then select with -xkbvariant > nodeadtilde. > > Or perhaps the correct solution is to use one of the existing deadgraveacute > or deadacute variants as the XWin default when Windows reports a German > keyboard layout? > > [1] https://bugs.freedesktop.org/show_bug.cgi?id=9752 > [2] http://cygwin.com/ml/cygwin-xfree/2003-05/msg00495.html Hi Jon, thanks for your work. I myself have made 2 patches and include them in this mail: - One patch for files /usr/share/x11/locale/iso8859-1/Compose and /usr/share/x11/locale/iso8859-15/Compose. - My patch for the "de" file: de.patch.patch patches your patch, whereas de.patch is the same thing patching the original de file. Here is the explanation (I'm referring to the original pargraph numbering): 1. Tilde sign - Yes, file "de" patched with your de.patch and XWin invoked with "-xkbvariant nodeadtilde" results in a German Windows keyboard (regarding the tilde). I did just a renaming of the Group description there to match the pattern of the other xkbvariants. 3. Non breaking space (NBSP) on ALT+space - In my patch I provide a xkbvariant "windowscompatible", that puts nobreakspace onto Alt+Space, like Windows has it. Furthermore, I added a line to the default German layout. It doesn't change the behaviour of the space key with shift, Alt, AltGr, but (and that's the reason why I've put it there), it makes the space key xmodmap redefinable in regard to the Alt key. Without that patch the key definition has not enough numbers of layers, resulting in that xmodmap discards a change of AltGr layer of space. 5. New dead acute issue --- Sorry to say, I found another difference while testing. This is, what the Compose.patch is for. In Windows, all blind keys followed by a space result in that character. Same in XWin, but with one exception: dead-´ plus space gives ' instead of ´. Please check out my patch for that. Regards, Paul Compose.patch Description: Binary data de.patch.patch Description: Binary data de.patch Description: Binary data -- 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/
AW: AltGr key mostly fires an additional CONTROL key
> Hi, > > I also had problems with the AltGr key. These could reliably > be reproduced by holding the AltGr for some seconds (causing > Windows generating auto repeat events). > > Unfortunately the test version at > > ftp://cygwin.com/pub/cygwinx/XWin.20110801-git-2d9f9305cb559907.exe.bz2 > > doesn't fix this problem for me. > > I discovered that the mechanism in winkeybd.c function > winIsFakeCtrl_L had a problem if PeekMessage cannot obtain > the next Alt_R message because it is not there. > > I prepared a patch that remembers the last Ctrl_L event and > reacts on a later following Alt_R. It was also necessary to > alter the order in winWindowProc in winwndproc.c: the invocation > of winIsFakeCtrl_L had to be done before discarding auto-repeated > key presses. > > The attached patch is against the sources of xserver-cygwin-1.10.3-1. > > Best regards, > Oliver Hi Oliver, the ftp://.exe.bz2 that you mention wasn't intended to contain any fix; it only produces additional debug statements. This is the one, that contains Jon's fix (works fine for me): ftp://cygwin.com/pub/cygwinx/XWin.20110803-git-a493c0465e56ce0b.exe.bz2 Paul. -- 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/
AW: Can't paste text or type blind keys when mouse is out of the window
> -Ursprüngliche Nachricht- > On 07/08/2011 10:05, Paul Maier wrote: > > when xterm has keyboard focus, but mouse pointer is outside of the window > > (or > > even on Window's blue title bar): > > > > > > - all blind keys are ignored: > > > >o instead of 'à' (key '`' then 'a') you get just a normal 'a' > > > >o can't type '^' character (on a German keyboard done with blind '^' > > key then space) > > -> you will just get the space instead > > > >o same with '`' or '´': all blind keys are affected > > > > - can't paste text with the mouse > > > > - all other keys work as expected > > Thanks for reporting this issue and the clear reproduction step. > > I can reproduce this problem. I can also reproduce it under XWin in windowed > mode with twm, but not on Xorg on Linux, so this seems to be XWin specific, > but not related to multiwindow mode WM, which is a real puzzler. > > I assume that you see the same behavior with other X applications, i.e. it's > not xterm-specific? > > > The XWin.logs are the same regardless if mouse is inside or outside, > > but I notice a small difference in xev's output. > > Yes, it looks like the events are delivered to the top window of xterm's > hierarchy when the mouse is on the non-client area of the window or the > desktop, but to the bottom window of the xterm hierarchy when the mouse is > over the xterm window. > > I also note that if you type a deadkey with the mouse in the client area, then > move the mouse over the frame, type a key, it is passed straight though, then > move the mouse back over the client area, and type a key, it is modified by > the previous deadkey. Hi Jon, welcome back from your holiday. > I assume that you see the same behavior with other X applications, i.e. it's > not xterm-specific? No, at least xedit works fine on my PC, with blind keys and with mouse text pasting, no matter if the mouse pointer is really inside or on blue window frame or (for blind keys:) really outside. Mouse pointer on blue window frame comes from a typical use case: when clicking focus to the window. Then the mouse pointer stays there. The window has the focus but you can't paste inside xterm before moving the mouse really inside. With xedit that works. Paul. -- 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/
xterm: scrollbar bug
Hi everybody, xterm doesn't show the scroll bar properly; the jpegs in this link show the problem as it still exists: http://www.cygwin.com/ml/cygwin-xfree/2010-06/msg00071.html I also found some emails from 2010 towards a solution: http://www.cygwin.com/ml/cygwin-xfree/2010-07/msg00028.html http://www.cygwin.com/ml/cygwin-xfree/2010-06/msg00077.html http://www.cygwin.com/ml/cygwin-xfree/2010-08/msg00061.html Above mails indicate, that the solution is already (almost) found. Will a fix be available in some of the next releases? Thanks & Regards Paul -- 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/
AW: AW: AltGr key mostly fires an additional CONTROL key
> -Ursprüngliche Nachricht- > > I've had a go at fixing it. Can you please try the build I've uploaded at > > [1] > > and see if it still shows the problem for you? > > > > [1] ftp://cygwin.com/pub/cygwinx/XWin.20110803-git-a493c0465e56ce0b.exe.bz2 > > > Hi Jon, > > works fine for me. I Played around quite a while, but the CONTROL-locking > didn't occur any > more. Yippie! Hi Jon, regarding XWin.20110803-git-a493c0465e56ce0b.exe.bz2 on my PC fixes AltGr problem: I wanted to ask, if that fix will be available with the next release? Regards, Paul -- 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/
AW: AW: Can't paste text or type blind keys when mouse is out of the window
> >> I assume that you see the same behavior with other X applications, i.e. > >> it's > >> not xterm-specific? > > > > No, at least xedit works fine on my PC, with blind keys and with mouse text > > pasting, > > no matter if the mouse pointer is really inside or on blue window frame or > > (for blind keys:) really outside. > > > > Actually, maybe this is an xterm problem? > > It seems to be somehow related to the xterm's --enable-toolbar configuration > (which is turned on in the cygwin package). If I rebuild xterm with that > disabled, the problem goes away, and I can also reproduce the problem on F15 > under twm if I build xterm with --enable-toolbar there (which is not enabled > in the distro supplied package) Hi Jon, maybe it's a workaround to include two xterm builds in the cygwin release: one xterm compiled with --enable-toolbar and the other having it disabled. I don't use the toolbar, so I would have the blind keys working fine at zero cost. Paul -- 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/
AW: AW: 'de' keyboard layout issues
> > In Windows, all blind keys followed by a space result in that character. > > Same in XWin, but with one exception: > > dead-´ plus space gives ' instead of ´. > > > > Please check out my patch for that. > [...] for files /usr/share/x11/locale/iso8859-1/Compose and /usr/share/x11/locale/iso8859-15/Compose. > > This patch makes sense to me, but doesn't seem to go far enough. Since the > compose sequences are selected by the locale, this fixes things if > LANG=de_DE.iso8859-1 or LANG=de_DE.iso8859-15, but not if LANG=de_DE.UTF-8. > > I'll try to take another look when I'm back from my holiday :-) Hi Jon, agreed, my patch is a partial solution. Is there an issue tracker in use, where we can put my patch and the idea behind it? Regards, Paul Compose.patch Description: Binary data -- 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/
AW: AW: AW: Can't paste text or type blind keys when mouse is out of the window
> I assume that you see the same behavior with other X applications, i.e. > it's > not xterm-specific? > >>> > >>> No, at least xedit works fine on my PC, with blind keys and with mouse > >>> text pasting, > >>> no matter if the mouse pointer is really inside or on blue window frame or > >>> (for blind keys:) really outside. > >>> > >> > >> Actually, maybe this is an xterm problem? > >> > >> It seems to be somehow related to the xterm's --enable-toolbar > >> configuration > >> (which is turned on in the cygwin package). If I rebuild xterm with that > >> disabled, the problem goes away, and I can also reproduce the problem on > >> F15 > >> under twm if I build xterm with --enable-toolbar there (which is not > >> enabled > >> in the distro supplied package) > > hmm - I'm not clear on precisely what a "blind key" is. Sounds like a > compose sequence - and if so, it's puzzling that passing key-presses from > different levels in the widget hierarchy would interfere with that. > > The main difference with the toolbar configuration is that xterm's using a > form to contain the toolbar and the vt100 window. The buttons take care > of themselves, but that area to the right of the buttons is dead. > > To make it somewhat friendlier, xterm adds the actions used for the vt100 > window (except for the ones related to the mouse) to the toolbar area. > > I omitted the mouse-related ones since it seems that they'd interfere with > the menus. I also did the same for the scrollbar widget (since keystrokes > there used to be lost - it would seem that you could reproduce your > problem also by looking at the behaviour around the scrollbar). Hi Thomas, yes, with mouse over the scrollbar the problem is reproducable. A blind key is a key that needs to be followed by another key to produce something. The problem here is, when running vi in an xterm and the mouse slowly (unnoticed) moves over the scrollbar or out of the xterm, and you want to jump to mark "a, you need to enter `a, that is in keystrokes 1. blind key ` 2. space 3. letter a, the bug will drop the `, so you will not end up with the cursor at mark "a, but you will move the cursor one character forward and there enter append mode. Which is something totally different than the intention. Or if you type :%s/^x/y/ You will really get :%s/ x/y Hopefully you notice it before pressing Enter ... Exaples refer to a German keyboard layout. Thank you for looking into this. Regards, Paul -- 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/
AW: AW: AW: AW: Can't paste text or type blind keys when mouse is out of the window
It seems to be somehow related to the xterm's --enable-toolbar configuration (which is turned on in the cygwin package). If I rebuild xterm with that disabled, the problem goes away, and I can also reproduce the problem on F15 under twm if I build xterm with --enable-toolbar there (which is not enabled in the distro supplied package) >> The main difference with the toolbar configuration is that xterm's using a >> form to contain the toolbar and the vt100 window. The buttons take care >> of themselves, but that area to the right of the buttons is dead. >> >> To make it somewhat friendlier, xterm adds the actions used for the vt100 >> window (except for the ones related to the mouse) to the toolbar area. >> >> I omitted the mouse-related ones since it seems that they'd interfere with >> the menus. I also did the same for the scrollbar widget (since keystrokes >> there used to be lost - it would seem that you could reproduce your >> problem also by looking at the behaviour around the scrollbar). > > yes, with mouse over the scrollbar the problem is reproducable. > > The problem here is, when running vi in an xterm and the mouse slowly > > (unnoticed) > > moves over the scrollbar or out of the xterm, and you want to jump to mark > > "a, > > you need to enter `a, that is in keystrokes > > I'll experiment to see if I can reproduce this effect with my environment. > thanks for the detailed explanation. Hi Thomas, yes, I'm talking about dead keys = compose sequences. Was it possible to you to reproduce it in your environment? Typing dead key ` apostrophe then press letter "a" while the mouse pointer is over the scrollbar area of an xterm? Please let me know in case you need more information or in case you want me to run some test. Thank you very much for looking into this. Regards, Paul -- 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/
scrolling xterm with Levovo trackpoint
Hi there, when I reboot my PC, scrolling an xterm with a Levovo trackpoint works (mostly) fine, very smooth and good speed. Then I work for a while and some condition, that I couldn't find out yet, corrupts it. It then doesn't scroll WHILE you hold that Trackpoint middle button down, but after you RELEASED it; on release it catches up for all the scrolling that should have appeared before. It's then not really scrolling but guesswork, how much of pressure might be the right, then you release and you see where you got scrolled by that. Does anybody have the same experience or an idea what could be the cause of that switching from working to not working? With trackpoint I mean that red button in the middle of a Lenovo laptop. Thanks & regards, Paul -- 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/
AW: scrolling xterm with Levovo trackpoint
> > when I reboot my PC, scrolling an xterm with a Levovo trackpoint works > > (mostly) fine, very smooth > and good speed. > > Then I work for a while and some condition, that I couldn't find out yet, > > corrupts it. > > It then doesn't scroll WHILE you hold that Trackpoint middle button down, > > but after you RELEASED it; > > on release it catches up for all the scrolling that should have appeared > > before. > > It's then not really scrolling but guesswork, how much of pressure might be > > the right, then you > release > > and you see where you got scrolled by that. > > > > Does anybody have the same experience or an idea what could be the cause of > > that switching from > working to not working? > > not exactly - if it's using wheel mouse (buttons 4/5) those should be > sent continuously. xterm isn't necessarily going to keep up with > a continuous stream of events, so there could be a buildup of events > making xterm not seem to do much for a while. I made some improvements > to filter out duplicate window movement/resizing, but that shouldn't be > related. Hi Thomas! thank you for your response. I experience a difference between the Trackpoint and the mouse wheel: the mouse wheel always works fine. Even an xterm that lived for quite a while and that shows this deferred scrolling on using the trackpoint, I can without problem scroll using the wheel or using xterm's scrollbar. I think we agree, that the trackpoint events ARE generated (because otherwise there would not be deferred scrolling but no scrolling). So the question is, where these events get buffered. If xterm treats wheel and trackpoint the same, the trackpoint events get buffered in a component between XWin and xterm? In case you want me to run a beta test, also for the blind key (dead key) issue, pls let me know. Regards, Paul -- 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/
Levovo trackpoint come delayed (reproducable with xev)
Hi there, Lenovo trackpoint scrolling events get buffered somewhere until I release the button: then I get hundreds of scrolling events all at once. I can clearly see these events in xev. Result is that I don't really experience scrolling, rather jumping up and down with a random-like distance. With trackpoint I mean that red button in the middle of a Lenovo laptop. (Mouse wheel scrolling works perfect, in contrast.) Thanks & regards, Paul -- 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/
AW: Levovo trackpoint come delayed (reproducable with xev)
> On 22/01/2012 23:10, Paul Maier wrote: > > Lenovo trackpoint scrolling events get buffered somewhere until I release > > the button: > > then I get hundreds of scrolling events all at once. > > > > I can clearly see these events in xev. > > > > Result is that I don't really experience scrolling, rather jumping up and > > down > > with a random-like distance. > > > > With trackpoint I mean that red button in the middle of a Lenovo laptop. > > > > (Mouse wheel scrolling works perfect, in contrast.) > > Have you tried the workaround given in [1] ? > > According to the internet, the trackpoint driver tries to be too clever and > doesn't send WM_MOUSEWHEEL messages, but tries to fiddle with the Windows > scrollbars directly itself, which obviously isn't going to work well for an X > window :S > > [1] http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-trackpoint > Hi Jon, I can't find any of the files tp4*.dat on my PC (I'm running Windows 7) - see console output below. And I do get the trackpoint events, they are just delayed until I release that button; on release I get hundreds of correct events scrolling my window to somewhere. How many events I get depends on how long or how intense I pressed the track point (sounds reasonable to me). Paul. C:\Windows\System32>dir tp*.dat Datenträger in Laufwerk C: ist Systemplatte Verzeichnis von C:\Windows\System32 Datei nicht gefunden C:\Windows\System32>dir *.dat Datenträger in Laufwerk C: ist Systemplatte Verzeichnis von C:\Windows\System32 10.06.2009 22.34 215.943 dssec.dat 14.10.2011 14.31 369.104 FNTCACHE.DAT 10.06.2009 22.13 3.698.584 ieapfltr.dat 10.06.2009 22.26 673.088 mlang.dat 10.06.2009 22.32 741 NOISE.DAT 29.12.2011 07.53 152.404 perfc007.dat 29.12.2011 07.53 125.350 perfc009.dat 14.07.2009 09.4938.104 perfd007.dat 14.07.2009 01.3431.548 perfd009.dat 29.12.2011 07.53 711.580 perfh007.dat 29.12.2011 07.53 665.164 perfh009.dat 14.07.2009 09.49 295.922 perfi007.dat 14.07.2009 01.34 291.294 perfi009.dat 13 Datei(en), 7.268.826 Bytes 0 Verzeichnis(se), 54.902.112.256 Bytes frei -- 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/
AW: QAW: AW: Levovo trackpoint come delayed (reproducable with xev)
> -Ursprüngliche Nachricht- > On 29/01/2012 13:36, Paul Maier wrote: > > I did several tests and now I can send you a detailed report: > > Thanks for taking the time to do that. > > > Notes: > > - I found that file at C:\Program Files\Synaptics\SynTP\TP4table.dat and I > > have added the > > lines from FAQ, but that didn't change anything. > > Hmm... the sixth item in the rule (which I'm guessing is a windows classname), > doesn't look like it's correct anymore. > > I'm not sure if that's related to your problems, but I've fixed the FAQ. > > > The following description is done with the patched version of the file. > > - Your download reference "[1]" seems to be missing in your mail, therfore > > I used > > XWin.20110803-git-a493c0465e56ce0b instead, that I still had from our > > last debugging. > > Yes, sorry about that. I meant to write: > > [1] ftp://cygwin.com/pub/cygwinx/XWin.20120129-git-45e67e363e19a481.exe.bz2 > > Can you try again with the latest snapshot, there should be some additional > numbers after the WM_MOUSEWHEEL messages which should help with debugging ths > problem. > > > - I hold the button down and shift the trackpoint up and down. > > xterm shows no scrolling movement at all. > > - Log in /var/log/xwin/XWin.0.log during this: > > a) still comes at the moment when I shift the trackpoint up and down, > > b) but it doesn't look regular any more: > > There are MUCH more lines > >winMouseButtonsSendEvent: iEventType: 4, iButton: 5, nEvents 2 > >winMouseButtonsSendEvent: iEventType: 5, iButton: 5, nEvents 2 > > and only a few lines > >winWindowProc - WM_MOUSEWHEEL > > in between. > > Looks like this: > > [ 473.447] winMouseButtonsSendEvent: iEventType: 5, iButton: 5, nEvents 2 > > [ 473.447] winMouseButtonsSendEvent: iEventType: 4, iButton: 5, nEvents 2 > > This looks a bit like the trackpoint is sending us a WM_MOUSEWHEEL for a much > larger mouse movement (which we need to break down into multiple button 5 > press/releases) > > > Maybe this is an interesting section, it contains an "EQ overflowing": > > [ 350.612] [mi] EQ overflowing. The server is probably stuck in an > > infinite loop. > > This means that the events are being generated faster than the server can > process them. > > > - I release the button. At the moment when I release the button, the xterm > > jumps to a new position. > > During this, there is absolutely no output to /var/log/xwin/XWin.0.log. > > So it sounds almost like the X server is being prevented from processing X > events until the mouse button is released. > > It might be interesting to try as separate test with some application which > constantly draws to it's window (like ico), if that continues drawing when the > trackpoint button is down. Hi Jon, here a log of my recent tests. The most interesting point is the last. 1. I modified file C:\Program Files\Synaptics\SynTP\TP4table.dat according to new FAQ and reboot PC. -> No change of behaviour. 2. Download XWin.20120129-git-45e67e363e19a481.exe.bz2. /bin/startxwin -- /bin/XWin.20120129-git-45e67e363e19a481.exe -logverbose 3 -clipboard -emulate3buttons 100 -nounixkill -nowinkill -xkboptions nbsp:level3 -> Doesn't start. Error message on the console is: giving up. /bin/startxwin: No such file or directory (errno 2): unable to connect to X server /bin/startxwin: No such process (errno 3): Server error. -> No output at all to file /var/log/xwin/XWin.0.log. 3. I took above startxwin command line and replace XWin.20120129-git-45e67e363e19a481.exe by XWin.20110803-git-a493c0465e56ce0b.exe -> Immediately starts. All further tests with (old) XWin.20110803-git-a493c0465e56ce0b.exe. 4. Today I couldn't get to the broken, jumpy behaviour by scrolling a Windows dialog. So this is not the breaking condition as I previously meant. But after some time, the scrolling behaviour breaks and xterm scrolls in jumpy way. Sorry, I have no glue what's the condition that breaks it. After reboot of PC it scrolls fine. Any work of 1 minute or so seems to break smooth scrolling. 5. Then I started ico. -> While ico runs, xterm scrolls fine and smooth. As soon as I stop ico, xterm scrolls jumpy. -> Pressing the trackpoint button has no effect to ico. It keeps painting fine eather way. Regards, Paul -- 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/
AW: QAW: AW: Levovo trackpoint come delayed (reproducable with xev)
> > -Ursprüngliche Nachricht- > > On 29/01/2012 13:36, Paul Maier wrote: > > > I did several tests and now I can send you a detailed report: > > > > Thanks for taking the time to do that. > > > > > Notes: > > > - I found that file at C:\Program Files\Synaptics\SynTP\TP4table.dat and > > > I have added the > > > lines from FAQ, but that didn't change anything. > > > > Hmm... the sixth item in the rule (which I'm guessing is a windows > > classname), > > doesn't look like it's correct anymore. > > > > I'm not sure if that's related to your problems, but I've fixed the FAQ. > > > > > The following description is done with the patched version of the file. > > > - Your download reference "[1]" seems to be missing in your mail, > > > therfore I used > > > XWin.20110803-git-a493c0465e56ce0b instead, that I still had from our > > > last debugging. > > > > Yes, sorry about that. I meant to write: > > > > [1] ftp://cygwin.com/pub/cygwinx/XWin.20120129-git-45e67e363e19a481.exe.bz2 > > > > Can you try again with the latest snapshot, there should be some additional > > numbers after the WM_MOUSEWHEEL messages which should help with debugging > > ths > > problem. > > > > > - I hold the button down and shift the trackpoint up and down. > > > xterm shows no scrolling movement at all. > > > - Log in /var/log/xwin/XWin.0.log during this: > > > a) still comes at the moment when I shift the trackpoint up and down, > > > b) but it doesn't look regular any more: > > > There are MUCH more lines > > >winMouseButtonsSendEvent: iEventType: 4, iButton: 5, nEvents 2 > > >winMouseButtonsSendEvent: iEventType: 5, iButton: 5, nEvents 2 > > > and only a few lines > > >winWindowProc - WM_MOUSEWHEEL > > > in between. > > > Looks like this: > > > [ 473.447] winMouseButtonsSendEvent: iEventType: 5, iButton: 5, nEvents > > > 2 > > > [ 473.447] winMouseButtonsSendEvent: iEventType: 4, iButton: 5, nEvents > > > 2 > > > > This looks a bit like the trackpoint is sending us a WM_MOUSEWHEEL for a > > much > > larger mouse movement (which we need to break down into multiple button 5 > > press/releases) > > > > > Maybe this is an interesting section, it contains an "EQ > > > overflowing": > > > [ 350.612] [mi] EQ overflowing. The server is probably stuck in an > > > infinite loop. > > > > This means that the events are being generated faster than the server can > > process them. > > > > > - I release the button. At the moment when I release the button, the > > > xterm jumps to a new > position. > > > During this, there is absolutely no output to /var/log/xwin/XWin.0.log. > > > > So it sounds almost like the X server is being prevented from processing X > > events until the mouse button is released. > > > > It might be interesting to try as separate test with some application which > > constantly draws to it's window (like ico), if that continues drawing when > > the > > trackpoint button is down. > > > > Hi Jon, > > here a log of my recent tests. The most interesting point is the last. > > 1. I modified file C:\Program Files\Synaptics\SynTP\TP4table.dat according to > new FAQ and reboot PC. >-> No change of behaviour. > > 2. Download XWin.20120129-git-45e67e363e19a481.exe.bz2. > /bin/startxwin -- /bin/XWin.20120129-git-45e67e363e19a481.exe -logverbose 3 > -clipboard - > emulate3buttons 100 -nounixkill -nowinkill -xkboptions nbsp:level3 >-> Doesn't start. Error message on the console is: > > giving up. > /bin/startxwin: No such file or directory (errno 2): unable to connect to X > server > /bin/startxwin: No such process (errno 3): Server error. > >-> No output at all to file /var/log/xwin/XWin.0.log. > > 3. I took above startxwin command line and replace > XWin.20120129-git-45e67e363e19a481.exe by > XWin.20110803-git-a493c0465e56ce0b.exe >-> Immediately starts. All further tests with (old) > XWin.20110803-git-a493c0465e56ce0b.exe. > > 4. Today I couldn't get to the broken, jumpy behaviour by scrolling a Windows > dialog. >So this is not the breaking condition as I previously meant. >But after some time, the scrolling behaviour breaks and xterm scrolls in > jumpy way. >Sorry, I have no g
AW: AW: QAW: AW: Levovo trackpoint come delayed (reproducable with xev)
> > 2. Download XWin.20120129-git-45e67e363e19a481.exe.bz2. > > /bin/startxwin -- /bin/XWin.20120129-git-45e67e363e19a481.exe -logverbose > > 3 -clipboard - > emulate3buttons 100 -nounixkill -nowinkill > > -xkboptions nbsp:level3 > >-> Doesn't start. Error message on the console is: > > > > giving up. > > /bin/startxwin: No such file or directory (errno 2): unable to connect to > > X server > > /bin/startxwin: No such process (errno 3): Server error. > > > >-> No output at all to file /var/log/xwin/XWin.0.log. > > Possibly you need to 'chmod +x /bin/XWin.20120129-git-45e67e363e19a481.exe' > > -- > Jon TURNEY > Volunteer Cygwin/X X Server maintainer Hi Jon, x bit was set: $ls -lg *.exe -r-xr-xr-x+ 1 13762945 02.02.2012 19.38 XWin.20120129-git-45e67e363e19a481.exe What about the other interesting results? Please note, that yesterday I sent 2 mails, the second mail continues paragraph counting from 6 to 9. Regards, Paul -- 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/
