Re: remote login from SGI

[rbaxter]

Dear Billy,


'export TERM=linux' gets Emacs to load but there are no menus and most things
don't work, like Alt, F10, arrow keys (CTRL key works now though). I get better
results with 'export TERM=ansi' but still not as good as when I spawn an xterm
on the local machine before ssh login (F10 works there, thanks v. much).

Q. I cp'ed the iris-ansi files into /usr/share/terminfo/i and /etc/terminfo/i on
the linux box, and I checked and found that 'iris-ansi' defn is in the
/etc/termcap file on the linux box. Could the problem be on the local SGI, it
doesn't have a 'linux' or 'ansi' entry in its /usr/lib/terminfo directory? I
tried cp'ing the appropriate entries from the remote box and then setting the
environment variable in the local shell before I ssh'ed. The terminal type was
recognized on the remoate machine, but still Emacs didn't work properly. Setting
the environment variable to 'xterm' within a native SGI shell window does not
work the same as spawning a new xterm window on the SGI before ssh'ing to the
linux box.

Finally, using xterm I have a basically functional Emacs session, but the
minibuffer is not refreshed properly. For instance, if I type C-x C-f to open a
file, the path does not appear in the minibuffer where I can edit it, to get
this I have to go via F10 f o to use the menu system.

Any advice appreciated.

regards,

Richard Baxter

Quoting Billy O'Connor <billyoc@gnuyork.org>:

> rbaxter@uchicago.edu writes:
> 
> >   emacs: Terminal type iris-ansi is not defined.
> >
> export TERM=linux; emacs -nw
> >
> > P.S. how to access the menus in the terminal version of Emacs?
> 
> That'd be F10 here.
> 
> -- 
> GNU/Linux revenues last quarter: $1 Billion.
> micros~1  revenues last quarter: $4 Billion.
> It's no longer a question of windows or GNU, it's a question of *Unix* or
> GNU.
> _______________________________________________
> Help-gnu-emacs mailing list
> Help-gnu-emacs@gnu.org
> http://mail.gnu.org/mailman/listinfo/help-gnu-emacs
>