My custom config changes won't load when I exit tmux server/session.

[sgss-jeff]

I am trying to learn my way through the configs for this code. I have explicitly followed the setup instructions.

I am making very simple config changes to the segments, but they do not appear when I exit tmux and relaunch it.

(My config.sh https://gist.github.com/sgss-jeff/bf66ed7fb41c75fc1ffba2938b4ce6e3 with the only change, in line 444)

The default configuration works as show in the screen shot.

I expect the Weather segment display to change to "F" when I change export TMUX_POWERLINE_SEG_WEATHER_UNIT="f" in my config.sh but this does not happen.

I have made changes to config.sh and exited tmux, then relaunched it. I have made changes while no TMUX sessions were running, closed my SSH session (and all other SSH sessions to the same machine), reconnected, and launched tmux. None of these seem to work.

The only way I can get the change to take effect is to REBOOT the machine I am running tmux-powerline on.

It's like I am reliving 1999 and Windows NT4.0.

Where, why, and how are my configurations getting cached, and how do I fix this?

[erikw]

Hello,

A reboot should certainly not be needed, that's for sure! Actually changes in your config.sh should be picked up instantly, i.e. on the next render of the statusbar. Unless you have some other settings in your tmux.conf, the default re-render of the statusbar is set to be every 1 second.

Could you please make sure to try with a minimal tmux.conf, having no custom tmux settings and just the initialization of TPM and this plugin.

From what you describe, it sounds like it's an issue with the paths used. Could you please detail and investigate the location of:

• tmux.conf
• tmux-powerline installation
• tmux-powerline's config directory

Please try out the steps at the README debugging session. As a shell setup is quite complex, in the end you are the best person to debug this, as there could be some many possible issues. Please try to find out if the right config files are edited and then actually used by tmux-powerline. Specifically, you can run the statusbar rendering on cli directly and see if changes have been picked up or not. ($ bash -x powerline.sh (left|right))

Please let us know how it goes :).

Edit.
I'm not sure I got your setup completely. Make sure you are keeping it simple, avoid ssh things etc first to make a working setup.

You can also easily spin up a Codespace container to get a working live example of how it should work properly. You can spin it up and compare with how it works locally on your own shell setup. Click the "Open in Codespaces" button at the top of the README.

[xx4h]

To add to @erikw's answer, in your specific case, the weather segment has a cache, which defaults to 600 seconds and can be changed through TMUX_POWERLINE_SEG_WEATHER_UPDATE_PERIOD.

So if you change the TMUX_POWERLINE_SEG_WEATHER_UNIT, this can take up to TMUX_POWERLINE_SEG_WEATHER_UPDATE_PERIOD seconds until you see the changes in your tmux-powerline.

Besides changing the already mentioned TMUX_POWERLINE_SEG_WEATHER_UPDATE_PERIOD to something like 10 seconds while testing, the actual cache-directory defaults to /tmp/tmux-powerline_${USER} and the weather cache file is named weather_cache_data.txt, which can be safely deleted to manually trigger an update.