#30 On shell.sf.net vim doesn't work.

closed-works-for-me
nobody
None
5
2008-08-03
2006-04-18
Seiichi SATO
No

how to reproduce:

on mlterm (-y mlterm -e ssh user@shell.sf.net)
$ vim foo.c (or foo.html)

Discussion

  • Logged In: YES
    user_id=643728

    I cannot reproduce this. vim works fine here in mlterm over
    ssh.

    I assume your problem is simply that TERM is set to
    mlterm and there's no such (c)urses/terminfo/termcap entry on
    the remote machine. It's best to stick with TERM=xterm (or
    vt100 in extreme cases) because otherwise you'll get a dumb
    terminal as fallback which makes it very difficult to control
    vi, vim and many other terminal software. The alternative is
    to install a private terminfo entry (usually under
    ~/.terminfo) but that's only sensible if you use a small set
    of remote machines. Otherwise, it'll be a lot of work and
    it's pretty useless because TERM=xterm should work pretty
    much everywhere with no problems.

     
  • Seiichi SATO
    Seiichi SATO
    2006-10-21

     
    Attachments
  • Seiichi SATO
    Seiichi SATO
    2006-10-21

     
    Attachments
  • Seiichi SATO
    Seiichi SATO
    2006-10-21

    Logged In: YES
    user_id=480729

    > I assume your problem is simply that TERM is set to
    > mlterm and there's no such (c)urses/terminfo/termcap entry
    > on
    > the remote machine.

    I'd already installed terminfo entry.

    seiichi@sf-usr-shell:~$ tic ~/mlterm/doc/term/mlterm.ti

    Also shell.sf.net has ncurses, and vim is linked with
    libncurses.so.5.

    > Otherwise, it'll be a lot of work and
    > it's pretty useless because TERM=xterm should work pretty
    > much everywhere with no problems.

    I know that TERM=xterm works fine.

    We are improving mlterm.{ti,tc}, so I think this problem
    must be solved.

     
    • status: open --> closed-works-for-me