lwv27@CAS.BITNET (Larry W. Virden ext. 2487) (06/26/91)
We are having a VERY weird problem under OpenWindows 2.0 using MIT's X11R4 xterm. We have several users who continue to get error messages such as the following when starting an xterm: Warning: Missing '"'. Warning: translation table syntax error: Missing ')' while parsing action sequen Warning: ... found while parsing 'Shift<Key>F1: string("echo this is shi followed by a series of other similar messages. What is strange is that xrdb -query has the following for XTerm*VT100.translatio XTerm*VT100.translations: \ #override \n \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ Shift<Key>F1: string("echo this is shift F1\n") \n \ Ctrl<Key>F1: string("echo this is ctrl F1\n") \n \ Meta<Key>F1: string("echo this is meta F1\n") \n \ Alt<Key>SunF36: string("echo this is alt F11") string(0x07) \n \ \ Any<Key>F28: string(0x7f) \n \ \ Any<Key>F1: string(0x1b) string("1") \n \ \ Any<Key>SunF36: string(0x1b) string("[234z") \n \ Any<Key>SunF37: string(0x1b) string("[235z") \n \ \ !:<Key>F30: string(0x1b) string("[254z") \n \ Shift<Key>KP_Add: string("+") \n \ ~Mod2<Key>KP_Add: string(0x1b) string("[253z") \n \ Shift<Key>KP_Enter: string(0x0d) \n \ ~Mod2<Key>KP_Enter: string(0x1b) string("[250z") \n \ !:<Key>Delete: string(0x1b) string("[249z") \n \ Shift<Key>Insert: string("0") \n \ !:<Key>Insert: string(0x1b) string("[247z") \n \ \ !:<Key>F31: string(0x1b) string("[B") \n \ \ Shift<Key>Tab: string(0x1b) string("[240z") \n \ Ctrl<Key>Tab: string(0x1b) string("[252z") \n \ Any<Key>Tab: string(0x09) \n \ \ Shift<Key>Help: string(0x1b) string("[255z") \n \ \ Any<Key>L6: start-extend() select-end(PRIMARY, CLIPBOARD, CUT_BUFFER0) \n \ Any<Key>L8: insert-selection(CLIPBOARD) It is as if the translation manager is getting lost. The stranger thing is that the users having problems with this do not, as far as we can tell, have anything set up differently than other users who are not having problems. Does anyone have any ideas? -- Larry W. Virden UUCP: osu-cis!chemabs!lwv27 Same Mbox: BITNET: lwv27@cas INET: lwv27%cas.BITNET@CUNYVM.CUNY.Edu Personal: 674 Falls Place, Reynoldsburg,OH 43068-1614 America Online: lvirden
swick@athena.mit.EDU (Ralph Swick) (06/26/91)
Shift<Key>F1: string("echo this is shift F1\n") \n \ The Xt specification only permits Latin-1 characters inside the double quotes, so the new-line is the cause of problem. (The MIT implementation is more permissive than the spec, but new-line is still not allowed.)
swick@athena.mit.EDU (Ralph Swick) (06/27/91)
I said --- >> >> Shift<Key>F1: string("echo this is shift F1\n") \n \ >> >> The Xt specification only permits Latin-1 characters inside the double >> quotes, so the new-line is the cause of problem. (The MIT implementation >> is more permissive than the spec, but new-line is still not allowed.) >> but I was wrong about the last statement. In patch 17, I changed the MIT implementation to allow embedded newlines in quoted action parameters, in response to a bug report. Only a second quote or a NUL will terminate the scan now. Sorry bout that loss of consciousness. Back to packing...