Linux

5240 readers

86 users here now

A community for everything relating to the linux operating system

Also check out [email protected]

Original icon base courtesy of [email protected] and The GIMP

founded 1 year ago

MODERATORS

[email protected]

Why is my tmux borked? (discuss.tchncs.de)

submitted 3 months ago by [email protected] to c/[email protected]

12 comments fedilink hide all child comments

cross-posted from: https://discuss.tchncs.de/post/20478370

cross-posted from: https://discuss.tchncs.de/post/20474285

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.

top 12 comments

sorted by: hot top controversial new old

[–] [email protected] 8 points 3 months ago* (last edited 3 months ago) (2 children)

Maybe it's still using the borked config because all sessions were not exited? Try exiting it and then make sure no tmux process is still running, by for example running ps -aux | grep tmux.

Otherwise there must be some tmux config still lying around in your $HOME.

Edit: I don't know anything about Macs so I'm just assuming it works similar to linux.

Does fzf search hidden folders? You could also try with this, to make extra sure: find $HOME -name "*tmux*".

[–] [email protected] 8 points 3 months ago

There was in fact a process still running. Killed it, reinstalled tmux and everythings back to default. Thanks!

[–] Perhyte 2 points 3 months ago

Try exiting it and then make sure no tmux process is still running, by for example running ps -aux | grep tmux.

For future reference: the command to kill the tmux daemon (and as a side-effect, all other running tmux processes connected to it) is tmux kill-server (or in tmux, typing :kill-server, assuming default keybindings).

[–] [email protected] 5 points 3 months ago (1 children)

It seems like you're using the standard macOS Terminal. It has all kinds of issues with many terminal applications. I recommend switching to iTerm2. You can install it with a simple brew install --cask iterm2

[–] [email protected] 1 points 3 months ago (1 children)

Huh, I had iterm running half a year ago and couldn't see any advantage and removed it because of "simple systems" purist reasons. Guess I'll try again.

[–] [email protected] 4 points 3 months ago (1 children)

macOS doesn't support some basic ways of rendering text and colors. I see iTerm as strictly necessary if you are serious about using the Terminal on a Mac.

[–] [email protected] 1 points 3 months ago

I mainly use it for git, basic files stuff and Scripting away chore tasks, so I never experienced any limits. But maybe I just touched some of that turf now.

[–] dogsnest 3 points 3 months ago* (last edited 3 months ago) (1 children)

Gonna take a stab, because I don't have a Macbook within reach, but as it's a Unix, it's possible there's a tmux.conf file at:

~/.tmux.conf

which would persist through tmux installs as it's in the user's directory.

If you've already checked this out, um...

cheers,

[–] [email protected] 1 points 3 months ago (1 children)

I'll double check later or tomorrow, but afaik I deleted all files that contain tmux.

[–] dogsnest 1 points 3 months ago* (last edited 3 months ago) (1 children)

~/ .tmux.conf

is a hidden file, denoted by the "."

[–] [email protected] 1 points 3 months ago

The file isn't there.

[–] [email protected] 3 points 3 months ago

Tmux starts a daemon the first time, it's quite opaque on that regard.