yyp has joined #foot
novakane has joined #foot
novakane has quit [Client Quit]
novakane has joined #foot
yyp has quit [Remote host closed the connection]
novakane has quit [Quit: WeeChat 3.2]
yyp has joined #foot
yyp has quit [Read error: Connection reset by peer]
yyp has joined #foot
yyp has quit [Remote host closed the connection]
amk has quit [Remote host closed the connection]
yyp has joined #foot
yyp has quit [Read error: Connection reset by peer]
yyp has joined #foot
kmarius has joined #foot
yyp has quit [Read error: Connection reset by peer]
<
ericonr>
will try, thanks!
yyp has joined #foot
amk has joined #foot
novakane has joined #foot
st3r4g has joined #foot
cbb has joined #foot
cbb has quit [Ping timeout: 258 seconds]
cbb has joined #foot
yyp has quit [Remote host closed the connection]
<
ericonr>
dnkl: doesn't seem to be enough; exporting TERM=screen-256color to htop did work tho
cbb has quit [Ping timeout: 252 seconds]
novakane has quit [Quit: WeeChat 3.2]
cbb has joined #foot
<
cbb>
ericonr: have you restarted tmux (foot --server, if applicable)...?
<
cbb>
and foot --server *
<
ericonr>
cbb: yes, and I'm not using foot server yet
<
cbb>
and it doesn't work
<
cbb>
is it possible that $TERM is set to something other than "foot" in the outer terminal?
<
ericonr>
cbb: have verified it with both foot and foot-direct; but yes, TERM is correct in the outer terminal
<
cbb>
ericonr: what output do you get if you run the following in a tmux session:
<
cbb>
tmux show-environment -g | grep ^TERM=
<
ericonr>
TERM=foot-direct rn
<
ericonr>
I can restart to get TERM=foot
<
ericonr>
but it didn't work when I had that value
<
cbb>
the override mentioned in that comment above will only work for TERM=tmux
<
ericonr>
that grep without quotes hangs fish shell :p
<
ericonr>
ooh it hangs old fish
<
ericonr>
the just released 3.3.0 is fine
<
cbb>
the reason I asked is because sometimes misguided shell configs that people copy around do something like "export TERM=xterm-256color"
<
ericonr>
cbb: you mean TERM=foot, right?
<
cbb>
you mean as opposed to xterm-256color?
<
cbb>
No, I mean sometimes TERM will be set to foot by the terminal but then some shell config or plugin will change it
<
cbb>
which may affect tmux, depending on how you start it
<
cbb>
but that doesn't seem to be the case here anyway
<
cbb>
dnkl seems to have assumed your problem is caused by true color support not working correctly
<
cbb>
but perhaps it's something else
<
cbb>
the first thing to check would be if true color support is actually working in your current setup
<
cbb>
but I just noticed true color isn't working in my tmux either
<
cbb>
no sure since when though...I guess I don't use true colors often enough to notice
cbb has quit [Quit: WeeChat 3.2]
cbb has joined #foot
<
ericonr>
cbb: so there's something wonky going on for you too?
<
cbb>
ericonr: actually no, it was just a unrelated problem with my config
<
cbb>
the tmux override is working for me
<
cbb>
I do have an idea of how to fix the problem though
<
cbb>
without needing any hacks in .tmux.conf
<
cbb>
I think the "Tc" capability should just be added to both of the foot terminfo files
<
cbb>
upstream I mean
<
cbb>
I'll mention it to dnkl when he's next online
<
cbb>
ericonr: if you want to test it...
<
cbb>
try adding "Tc," under the "foot+base" line in foot.info
<
cbb>
and then rebuild and install
jer0me has quit [Ping timeout: 244 seconds]
jeromenerf has joined #foot
<
ericonr>
cbb: ok, can't do it immediately though