1 |
On Tue, Sep 06, 2005 at 09:19:51PM +0200, Jan Kundrát wrote: |
2 |
> Joe Wells wrote: |
3 |
> > The best solution to this that I can think of is to extend OpenSSH |
4 |
> > with the capability to copy terminfo information to ~/.terminfo on the |
5 |
> > remote system. |
6 |
> |
7 |
> IMHO automated overwriting files in $HOME on every login is a *very* bad |
8 |
> thing. And if you wanted to remove those "-via-ssh-#" lines after |
9 |
> logout, what will happen if your connection hungs? |
10 |
> |
11 |
> -jkt |
12 |
|
13 |
As said ssh can transport environment variables to the other system. |
14 |
Usualy people use it to transfer $TERM.. why not make a variable |
15 |
$TERMINFO_DESC ($TERMINFO is allready used by curses for the path to |
16 |
local terminfo) and put the hole terminfo description into it, mark it |
17 |
for export via ssh, and write a few commands in your bashrc on the other |
18 |
side to put $TERMINFO_DESC into a file say ~/.terminfo/${TERM:0:1}/$TERM |
19 |
if it does not exist... (or do the new-uniqe-name stuff Joe suggested) |
20 |
|
21 |
Or just simpler, put a termcap descritption into $TERMCAP, and mark that |
22 |
for ssh export. Downside is that you would have to change TERM to |
23 |
something that isn't in the other systems terminfo database, or |
24 |
the $TERMCAP won't be used. |
25 |
|
26 |
Or better, hack curses to use $TERMINFO_DESC from environment to |
27 |
override the system terminfo databes, and just export that variable... |
28 |
Downside is that applications that don't use ncurses won't use it... |
29 |
|
30 |
But best way is to clear the mess as suggested and persuade konsole, |
31 |
gnome-terminal and others to use their own terminal type. |
32 |
|
33 |
-- |
34 |
_ |
35 |
| |
36 |
YoYo () Siska |
37 |
|
38 |
-- |
39 |
gentoo-dev@g.o mailing list |