Xterm: xterm-256color, Putty: putty-256color, Gnome Terminal: gnome-256color, Konsole: konsole-256color, Screen/Tmux: screen-256color
And for anyone interested, the best TERM for Terminal.app is dtterm.
I'm interested because the home and end key don't work for me, but when I use this, I get
Error opening terminal: dtterm.
when running a curses app after logging into a Fedora 14 box.Just copy over your shell config file if you're really in a poor situation like that often, and it's pretty trivial to make a script that'll automate it.
I'm not convinced auto-completion is one of them though. But hey, if you like GUI popups better it's certainly hackable!
EDIT: The way you'd do this is to provide additional functionality to the shell, not to the terminal.
> It's certainly something that could be done, but also something that shouldn't be done.
I was just thinking out loud how it could be done, so I don't see any disagreement here.
> You would have to make modifications to every possible shell the user might want to use, and these would only be a feature usable in a very select few terminal emulators.
Well, it'd be optional addition. Furthermore...
> It creates way more work because, in short, it's a violation of the Unix design philosophy.
Already shells attempt to detect if your terminal support color output, scrolling etc.
Your shell would still go around its usual business (e.g. auto-completion), the only thing that changes is how you're going to present that functionality to the user. And if terminal you're outputting to is happy to provide a popup, then why not use it? I don't see how that violates Unix design philosophy.
> EDIT: The way you'd do this is to provide additional functionality to the shell, not to the terminal.
Yes, that seems to be more accurate. The shell would make use of the additional capabilities provided by terminal.
I think you meant terminal emulator.
Surely that is best left as a shell feature...
EDIT: if the author is reading this, you link to a page which describes the incorrect way of enabling 256 colors in Vim (http://kevin.colyar.net/2011/01/pretty-vim-color-schemes-in-...). It suggests using `:set t_Co=256`, but that is generally considered by the Vim community (#vim on freenode) as the improper way of doing it. The correct way to do it is to just set your TERM env variable correctly (iterm does come with or support terminfo that indicates 256 color support, right?).