ornstein@fdcv09.DEC (Ian Ornstein PK03/2-28C DTN 223-9145) (12/08/84)
[] > While most of the reading community uses EMACS on UNIX perhaps >(I hope) there is someone who can answer this question: > > I am working on a VAX under VMS 3.7 and have a need to do some >development work on a DEC-20 under TOPS-20. My connection is via DECnet >by setting host and logging on to the 20. The problem is: > > Under this arrangement ^X is interpreted by the 20's EMACS as C - U >this means I am unable to use any of the control - X commands. Now I have >gotten by by the means of ESC-X and typing the command...which is very >tedious. The commands for using multiple windows become extremely awkward. >Does someone have a workarround/patch/fix for this? For my first request to the net (above) I received several replys. The first approach given was to attempt to redefine ^X. This I might have attemped in Mlisp but the 20's Emacs is implemented in teco. At any rate I found the following paragraph in the info documentation which suggests (to me) that another prefix command may be created, but didn't say anything about binding ^X functionality to some other key. The way I read it was if I were to define another prefix character, I would also have to define all the command that used ^X to use my new prefix. Here is the paragraph: EMACS Node: Characters, Previous: Screen, Up: Top, Next: Basic There is another prefix character, Control-X which is used as the beginning of a large set of two-character commands known as "C-X commands". C-X is not a bit prefix character; C-X A is not a circumlocution for any single character, and it must be typed as two characters on any terminal. You can create new prefix characters when you customize. *Note Prefix: (CONV)Prefix. ----------------------end of INFO paragraph------------------------------- Thankfully, the real answer turned out to be so simple that I have to share it with all of you: before set host to the DEC System-20 $ SET TERMINAL/PASSALL I caution that it is important to switch this back to nopassall if you return to the VAX to work. I didn't and tried to go in to VAX mail... I would be interested in receiving examples of teco emacs.init files if anyone desires to send mail. Thanks for all your help, Ian Ornstein ENET: FDCV09:ORNSTEIN Office: (617) 493-9140 Home: (617) 646-5420 USMail: 14 Brattle Terrace Arlington, MA 02174
tli@uscvax.UUCP (Tony Li) (12/11/84)
> > I am working on a VAX under VMS 3.7 and have a need to do some > >development work on a DEC-20 under TOPS-20. My connection is via DECnet > >by setting host and logging on to the 20. The problem is: > > > > Under this arrangement ^X is interpreted by the 20's EMACS as C - U > >this means I am unable to use any of the control - X commands. Now I have > >gotten by by the means of ESC-X and typing the command...which is very > >tedious. The commands for using multiple windows become extremely awkward. > >Does someone have a workarround/patch/fix for this? > > Thankfully, the real answer turned out to be so simple that I have to share > it with all of you: > > before set host to the DEC System-20 > $ SET TERMINAL/PASSALL > > I caution that it is important to switch this back to nopassall if you > return to the VAX to work. I didn't and tried to go in to VAX mail... > > Ian Ornstein > ENET: FDCV09:ORNSTEIN > Office: (617) 493-9140 > Home: (617) 646-5420 > USMail: 14 Brattle Terrace > Arlington, MA 02174 Actually, there's an even easier solution, although I'm under VMS 3.5. Try prefacing your ^X with a ^P.... ^P is the VMS Set Host escape character and lets you do lots of interesting things.... Try it, you'll like it. -- Tony Li ;-) Usc Computer Science Uucp: {sdcrdcf,randvax}!uscvax!tli Csnet: tli@usc-cse.csnet Arpa: tli@usc-ecl