Hello, I have a box that runs OpenBSD that sshes into my Debian box. On OpenBSD, the default colour term is vt220 so when I ssh to debian, TERM is set to vt220. When I run mc, all is well; colour, line draw, whatever. When I run lynx or mutt, I get black on white with no colour. On Lynx this means that my blue on gray ends up as white on black; with mutt I don't get the blue top and bottom lines or the red thread lines. If I ssh in from an xterm, with TERM=xterm, everything is fine. Does anyone have any clues on this? Thanks, Doug. -- To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org with a subject of "unsubscribe". Trouble? Contact email@example.com
env TERM=xterm-color ssh@debianbox
Hangs things up since I'm going from a vt not an xterm. xterm's work fine. Doug.
termcap/termlib db's are different between openbsd and debian. curses implementations are different between openbsd and debian. some apps (like vim off the top of my head?), don't use termcap/termlib or curses, they got their own thing going on. They read TERM and do their own capabilities on it. Terminals lie (You're not using a vt220 afterall, are you?), and terminal capabilities lie. There are kilo's of documentation for termincal capabilities and sequences out there, and they conflict each other. curses has a .hascolor() boolean apps will read. You can print colors, but curses will snuff them if .hascolor() returns false. I've seen xterm-color return false, but xterm-256color return true! what?? Anyway, wsvt25 from console works great from openbsd on openbsd. If you're on net and freebsd, pcvt25 works fairly well. Logging into linux, I generaly use vt220 or vt102. keep these aliases handy: alias vt220='export TERM=vt220; tset -I -Q' alias vt102='export TERM=vt102; tset -I -Q' alias wsvt25='export TERM=wsvt25; tset -I -Q' alias pcvt25='export TERM=pcvt25; tset -I -Q' alias xterm256='export TERM=xterm-256color; tset -I -Q' alias xtermcolor='export TERM=xterm-color; tset -I -Q'
Yahoo! wsvt25 works just fine obsd to debian, for mutt. Interestingly, it doesn't work so well natively on obsd. Also, I don't need to set it before sshing; standard vt220 on obsd and ssh to debian and set TERM=wsvt25 seems to work just fine. Thanks. Doug.
Just to follow-up. TERM=screen works well for both OBSD and linux so that's now my default screen type in /etc/ttys. Problem solved. Thanks. Doug.
I had the same problem. I solved it using xterm-xfree86 but now I have a different one. I cannot use backspace to scroll up. The error message is "Key is not bound." any idea of how to fix that? Pau
Try TERM=screen. I didn't know about the backspace to scroll up; I just use page up. I just tried it and yes it works with TERM=screen. Note that I can't use TERM=xterm* since I'm not using X for this. Doug.
yes, I tried this before I posted here but no way... it's not working
Did you use TERM=screen on both ends of the ssh, i.e. on OBSD before ssh
yes... it doesn't help I thought left-clicking on the xterm, and selecting "Backarrow Key (BS/DEL)" would do it, and afterwards typing `stty erase ` and then ctrl-v and then hitting backspace and enter... but that's only for xterm. What, if you're using a different terminal, like aterm, eterm, konsole or gnome-terminal? you don't have that menu... I also saw this... but... don't know...
|Michael Trimarchi||Re: [PATCH] VFS: make file->f_pos access atomic on 32bit arch|
|Miklos Szeredi||[patch 14/15] vfs: more path_permission() conversions|
|Serge E. Hallyn||Re: [RFC v5][PATCH 7/8] Infrastructure for shared objects|
|Bernd Schmidt||Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3|
|Takashi Iwai||[PATCH 2/2] input: Add LED support to Synaptics device|
|Junio C Hamano||Re: mingw, windows, crlf/lf, and git|
|Eyvind Bernhardsen||Re: Where has "git ls-remote" reference pattern matching gone?|
|Shawn O. Pearce||Re: Switching from CVS to GIT|
|Todd Zullinger||Re: [PATCH 2/2] send-email: rfc2047-quote subject lines with non-ascii characters|
|Santi Béjar||Re: How to use git-fmt-merge-msg?|
|Ramkrishna Vepa||[net-2.6 PATCH 1/10] Neterion: New driver: Driver help file|
|Mark Anthony||invitation / inquiry|
|Ingo Molnar||Re: [PATCH 08/16] dma-debug: add core checking functions|
|David Miller||Re: [PATCH 1/3] f_phonet: dev_kfree_skb instead of dev_kfree_skb_any in TX callback|
|Sascha Hauer||[PATCH 03/12] fec: do not typedef struct types|
|Linux Kernel Mailing List||amba: struct device - replace bus_id with dev_name(), dev_set_name()|
|Linux Kernel Mailing List||MIPS: Yosemite: Convert SMP startup lock to arch spinlock.|
|Linux Kernel Mailing List||ARM: S5PC100: IRQ and timer|
|Linux Kernel Mailing List||davinci: edma: clear interrupt status for interrupt enabled channels only|
|Linux Kernel Mailing List||x86, mm, kprobes: fault.c, simplify notify_page_fault()|
|Daniel A. Ramaley||Re: [semi-OT] Can anyone recommend an OpenBSD-compatible colour laser printer?|
|Matthias Kilian||Re: can't get vesa @ 1280x800 or nv|
|Tobias Ulmer||Re: Problem after upgrade 4.5 to 4.6: ERR M|
|Philip Guenther||Re: SIGCHLD and libpthread.so|
|J.C. Roberts||Re: [semi-OT] Can anyone recommend an OpenBSD-compatible colour laser printer?|