Hyper: 256 terminal color support

Created on 22 Jul 2016 · 16Comments · Source: vercel/hyper

Does hyperterm support 256 colors? I am using hyperterm-tomorrow-night, base16-tomorrow-night.vim, and base16-tomorrow-night shell themes but unless I have something configured wrong 256 colors are not working. I have tried other themes as well.

screen shot 2016-07-22 at 6 34 11 am

Enhancement

Source

codedmart

👍7

Most helpful comment

Adding set termguicolors in neovim config works here.

nicholasc on 13 Dec 2016

👍6

All 16 comments

I was running the script wrong. It seems to be working ok in hyperterm itself, but vim colors are still not correct. Still investigating.

codedmart on 22 Jul 2016

Also to note that vim looks fine and correct in iTerm2.app and Terminal.app.

codedmart on 22 Jul 2016

I also have color issues on vim. They work correctly on Neovim however.

Colours are incorrect with and without set termguicolors.

bpinto on 22 Jul 2016

I have neovim but 256 colors are not working for me.. Am I doing something wrong?

tnguyen14 on 23 Jul 2016

Is there any update on when this will be scheduled for?

tnguyen14 on 26 Oct 2016

Same problem here, in iTerm2 vim(nvim) colours look fine, but in hyperterm there wrong.

mak42 on 27 Oct 2016

Colors work when running tmux with set -g default-terminal "screen-256color" in the tmux.conf.

I created a work-around in my ~/.zshrc that fixes my vim colors. It creates a new tmux session named with the shell's PID and attaches a kill-session call when that shell is closed to cleanup after itself and not gather tons of tmux sessions.

alias tmuxn='tmux new-session -s $$'
_trap_exit() { tmux kill-session -t $$; }
trap _trap_exit EXIT
if ! [ -n "$TMUX" ]; then
    tmuxn
fi

It's quite dirty but it works for now. I wonder why running tmux fixes the colors. I also wonder if this issue is not linked to hterm itself.

nicholasc on 15 Nov 2016

Adding set termguicolors in neovim config works here.

nicholasc on 13 Dec 2016

👍6

With Hyper, tput colors outputs 256 and $TERM is set to xterm-256color. However, any number of test scripts which use the \e[<38|48>;5;<0..255>mOUT\e[0m ANSI codes, shows that the terminal is only supporting 16 colors. Is $TERM set by the terminal, in this case Hyper? This is really playing havoc with my .dircolors and makes using Hyper practically unusable. I have already configured Bash in Bash on Ubuntu on Windows (WSL) and I want to be able to switch back and forth at will.

rbeesley on 20 Mar 2017

I can't reproduce
capture d ecran 2017-04-19 a 00 18 16

Maybe only a WSL issue (see #1733)

chabou on 19 Apr 2017

@chabou Yes, that could be. I know the Console supports True Color now, but I suspect Hyper and bash.exe are going to have slightly different environments and terminal settings.

rbeesley on 19 Apr 2017

Does not work with foreground or background

test

Windows, using bash.exe and angel-PS1

s5bug on 28 May 2017

is there any workaround for that?

how do you, guys, use zsh-autosuggestions? any setting for ZSH_AUTOSUGGEST_HIGHLIGHT_STYLE='fg=[0-7]' is either too bright, or just the same color as prompt text.

my setup: win10+cygwin+zsh