erikw / tmux-powerline

⚡️ A tmux plugin giving you a hackable status bar consisting of dynamic & beautiful looking powerline segments, written purely in bash.
BSD 3-Clause "New" or "Revised" License
3.4k stars 513 forks source link

Easier config process #439

Open s1nistr4 opened 1 week ago

s1nistr4 commented 1 week ago

As of now there's a lot of stuff you have to configure ootb to get this working

For example you first have to generate a config using a bash script, you then have to more config.default.sh to config.sh (the bash script could just generate this), then you open the file and everything is just comments and folded code, so you have to manually uncomment every single line to get it working. A massive time consuming process for just a status line.

This could be made way easier. For example after being installed it could just run a script to generate a stock config and config.default in ~/.config/tmux-powerline/ and you edit that file directly with the default version to fall back on. Much easier and less work for the end user.

xx4h commented 1 week ago

Hi there, thank you for your feedback.

I'd like to better understand, where you see the massive time consuming process.

tmux-powerline is providing a working default status line right away after install. The generation of the config.sh.default is already optional and provides you with the actual config for the default. You only need to cp/move and change/uncomment something there if you want to change the status line.

However, i agree that it would be nice to have the default config being generated automatically on install directly into ~/.config/tmux-powerline/config.sh (of course only if not already existing). I'll have a look into that.

While we're at it, we should also provide some examples in the default config on how to set/override the actual status bar segments of the theme.

Happy to hear your thoughts

s1nistr4 commented 1 week ago

Hi there, thank you for your feedback.

I'd like to better understand, where you see the massive time consuming process.

tmux-powerline is providing a working default status line right away after install. The generation of the config.sh.default is already optional and provides you with the actual config for the default. You only need to cp/move and change/uncomment something there if you want to change the status line.

However, i agree that it would be nice to have the default config being generated automatically on install directly into ~/.config/tmux-powerline/config.sh (of course only if not already existing). I'll have a look into that.

While we're at it, we should also provide some examples in the default config on how to set/override the actual status bar segments of the theme.

Happy to hear your thoughts

What I mean by it being difficult is that you have to uncomment and unfold a lot of code to get the stock config, it would make more sense for it to just generate the default config so people can just tweak the values they need from it

xx4h commented 1 week ago

Hi there, thank you for your feedback.

I'd like to better understand, where you see the massive time consuming process.

tmux-powerline is providing a working default status line right away after install. The generation of the config.sh.default is already optional and provides you with the actual config for the default. You only need to cp/move and change/uncomment something there if you want to change the status line.

However, i agree that it would be nice to have the default config being generated automatically on install directly into ~/.config/tmux-powerline/config.sh (of course only if not already existing). I'll have a look into that.

While we're at it, we should also provide some examples in the default config on how to set/override the actual status bar segments of the theme.

Happy to hear your thoughts

What I mean by it being difficult is that you have to uncomment and unfold a lot of code to get the stock config, it would make more sense for it to just generate the default config so people can just tweak the values they need from it

As said, if you move the config.sh.default to config.sh you have the "stock" config, you don't have to uncomment/unfold anything. So basically the behaviour should already be like you wish it to be (besides you have to move the file, which could be improved like we already discussed). Maybe you have an example?