6 ms·

Somewhat related, but I am still recovering from the aftermath of the 2.8 to 2.9+ migration https://github.com/tmux/tmux/issues/1689 https://github.com/tmux/tmu

by harikb 6y ago

Somewhat related, but I am still recovering from the aftermath of the 2.8 to 2.9+ migration https://github.com/tmux/tmux/issues/1689 https://github.com/tmux/tmux/issues/1689 It is my own fault of blindly following someone's online configuration without truly understanding each line of the setup. I spent a whole day trying to recover my customized prefix and lost in pane vs window differences. Now my .tmux.conf only has 4 lines and I am done with over-customizations. It was unnecessary emergency when I was already behind on work. I don't think I will ever migrate the rest of the config.

ehsankia 6y ago
It was a bit annoying -fg -bg -attr into single config lines, I really wish they either supported backward compatibility or at the very least did provided an automated conversion. It was a pretty straight forward operation that could easily be automated.
- chaps 6y ago
  Yep. The devs make random breaking changes all the time. They don't have any issue with doing it since they post breaking changes ahead of time.. but who actually watches for these things? It's super frustrating
  - ehsankia 6y ago
    I don't think posting ahead of time justifies it. Unless there are clear reason for a breaking change, having some code to parse old config into new one, or at the very least convert the first time an old config is seen, is pretty trivial compare to the amount of time wasted by every single users manually converting their config.
    - nightcracker 6y ago
      Beyond that, tmux is (for me and probably many others) critical software used constantly when SSH'ing into many different boxes. Different boxes running different versions of tmux. Making it impossible to share one config file everywhere - you either need to have multiple config files for each version or simply drop any custom config that isn't cross-version compatible.
  - capableweb 6y ago
    > but who actually watches for these things On the other hand, who is using any linux-like OS on a daily basis and upgrades major software versions when they have work to do? I usually only do full system upgrades (including essential software like tmux, vim and such) only when I know I have spare time in case there is things breaking, as 1 out of 10 times, something will break/be deprecated/have changes somehow.
    - chaps 6y ago
      Upgrade time often happens when new features are needed for some project. So, yeah, it gets in the way of work ;)
      - capableweb 6y ago
        What kind of projects do you work on where new features to tmux are needed/required? Or put the other way around, what features in tmux were absolutely required for you to complete a project?
        chaps 6y ago
        ...apt-get upgrade, friend.
        capableweb 6y ago
        Yeah I get if you work on `apt` itself your use case might be a bit different. Although I'm not quite sure on what `apt` depends on from `tmux` but I digress.
        chaps 6y ago
        Hm. That's not what apt-get upgrade does. Can't tell if you're trolling, but I digress.
        capableweb 6y ago

by harikb 6y ago

ehsankia 6y ago

It was a bit annoying -fg -bg -attr into single config lines, I really wish they either supported backward compatibility or at the very least did provided an automated conversion. It was a pretty straight forward operation that could easily be automated.

chaps 6y ago
Yep. The devs make random breaking changes all the time. They don't have any issue with doing it since they post breaking changes ahead of time.. but who actually watches for these things? It's super frustrating
- ehsankia 6y ago
  I don't think posting ahead of time justifies it. Unless there are clear reason for a breaking change, having some code to parse old config into new one, or at the very least convert the first time an old config is seen, is pretty trivial compare to the amount of time wasted by every single users manually converting their config.
  - nightcracker 6y ago
    Beyond that, tmux is (for me and probably many others) critical software used constantly when SSH'ing into many different boxes. Different boxes running different versions of tmux. Making it impossible to share one config file everywhere - you either need to have multiple config files for each version or simply drop any custom config that isn't cross-version compatible.
- capableweb 6y ago
  > but who actually watches for these things On the other hand, who is using any linux-like OS on a daily basis and upgrades major software versions when they have work to do? I usually only do full system upgrades (including essential software like tmux, vim and such) only when I know I have spare time in case there is things breaking, as 1 out of 10 times, something will break/be deprecated/have changes somehow.
  - chaps 6y ago
    Upgrade time often happens when new features are needed for some project. So, yeah, it gets in the way of work ;)
    - capableweb 6y ago
      What kind of projects do you work on where new features to tmux are needed/required? Or put the other way around, what features in tmux were absolutely required for you to complete a project?
      - chaps 6y ago
        ...apt-get upgrade, friend.
        capableweb 6y ago
        Yeah I get if you work on `apt` itself your use case might be a bit different. Although I'm not quite sure on what `apt` depends on from `tmux` but I digress.
        chaps 6y ago
        Hm. That's not what apt-get upgrade does. Can't tell if you're trolling, but I digress.
        capableweb 6y ago