Path: utzoo!attcan!uunet!lll-winken!ames!mailrus!nrl-cmf!ukma!rutgers!mit-eddie!bloom-beacon!ATHENA.MIT.EDU!swick From: swick@ATHENA.MIT.EDU (Ralph R. Swick) Newsgroups: comp.windows.x Subject: Re: Help needed with xterm translations Message-ID: <8902011514.AA01412@LYRE.MIT.EDU> Date: 1 Feb 89 15:14:03 GMT References: Sender: daemon@bloom-beacon.MIT.EDU Organization: DEC/MIT Project Athena Lines: 41 >Problem: I have "#override F1:string("something")\n >and that works just peachy. However, I can't seem to find a way to >specify something like: "F1:string("somethingelse")" You probably don't really want this second translation binding; it's not really legal (I'll have to check the code to see why there was no message), but there is an almost-reasonable interpretation for it, vis: "" is an abbreviation for the specification "Shift", thus the almost-reasonable interpretation is the two-event sequence "Shift,F1". You should have really gotten an error message about the missing ",", but the implementation doesn't actually interpret your specification this way anyway. You can see the difference by actually inserting the "," in your version -- I don't claim it's useful :-). Any of the following will work as you probably expect: *VT100.translations: #override \ ShiftF1:string("else") \n\ F1:string("something") *VT100.translations: #override \ F1:string("else") \n\ F1:string("something") *VT100.translations: #override \ ~ShiftF1:string("something") \n\ ShiftF1:string("else") *VT100.translations: #override \ ~ShiftF1:string("something") \n\ F1:string("else") The order in the first two versions is significant; since the event "F1" allows any modifier state, it is crucial to first specify the more specific event. Since the last two versions explicitly state the state of the Shift modifier in both bindings, the order is not significant. Enjoy! -R