I can't help as I don't have exp with tmux or brew;
but I do know that if you crosspost your post/question into c/linux you'll have a better time finding someone that knows how to help!๐ค
Programming
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
That was actually a good tip!
I'm glad that you were able to get your tmux problem solved!๐ค
What's the value of your $TERM variable?
This is usually the cause, in my experience.
Unironically try turning your computer off and on again.
Tmux settings are global and persistent. Just deleting your config files is insufficient. You have to kill the server and restart it. Uninstalling and reinstalling will not kill a running tmux server. tmux kill-server
should work too.
Now if it persists across reboots, then there must be a file still lingering somewhere. If you are sure your home directory is clean you can try searching whatever you installed in /etc.
This is all assuming you're trying to go back to a clean slate and failing. If the borked status bar is the result of your current .tmux.conf
, then you'll have to post that.
Feels like a font issue. Do you have e.g. nerdfont installed and in use in your terminal? You could check the config for plugins that makes that style, and check which fonts are in use. Could also be powerline fonts that are needed: https://github.com/powerline/fonts
I got the JetBrainsMonon Nerdfont. It was annorphan process of tmux still running after all configs and tmux itself was uninstalled.
It was exactly that. The stupid thing is: I usually shut down my Mac at the end of my workday and on the next day and start everything I need via script and always got funny looks from my co-workers because "you can just close it and keep it running" so I tried it a few days and honestly did not think about restarting because it would have been a fresh start before.
But now I know there's a tmux server running that I can kill when problems occur and I won't need to reboot Everytime tmux starts acting funny. So at least I learned from being dumb and not thinking about basic trouble shooting steps...
Reinstall or install from a different source?
Yeah I could try that, I just try to stick to one source if possible. I'll give it a try if no other solution come up.