I’ve been trying tmux and followed a video that showcases and offers a prebuilt config for styling and plugins. Something happended (guess I did something wrong?) the styling broke and I decided I’ll go bare bones and customize to my needs when needed instead of using preconfigured stuff. I deleted all configs and caches I could find with fzf and even reinstalled tmux, but still some broken styling is present and makes it unpleasent to work with. Some of my configs seem to be present even after uninstall, as the prefix is still C-Space instead of the default. There are some oh-my-zsh subfolders that contain tmux. I don’t know if those have been there before and I also don’t know, if I can delete them without breaking the next thing.

I’m on a MacBook and installed tmux via brew.

  • sudo@programming.dev
    52·
    3 months ago

    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.

    • xtapa@discuss.tchncs.deOP
      31·
      3 months ago

      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.

  • xtapa@discuss.tchncs.deOP
    1·
    3 months ago

    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…