Package: tmux-dash
Tmux DashThe point of this project was to have an easily configurable dashboard fortmuxwhich would sit on window 0; essentially, it would have a todo list, various clocks, things of that nature.There are a couple of alternatives, the one that really comes up often if you're googling around the phrases "terminal" and "dashboard" iswtfutil, my core issue with this is that the module selection is a little limited, I'm also not a big fan of the way it looks and configuration available doesn't really help that.The other project of a similar nature istmuxinatorbut I didn't want to use it as a binary replacement fortmuxitself. I also wanted a config which is more focused on a specific layout, for which specific splits are defined for each pane.UsageFrom within a tmux session run this script and either use the default config ($HOME/.config/tmux-dash/config.yml) or specify a config file with the-coption.Next is to specify a tmux session, this can be done with the session id with-ior session name with-n. Alternativley, if you are within a tmux session, specify nothing and tmux-dash will pick up on your$TMUXenvironment variable.ConfigurationA sample configuration could be:dashboard:
    number: 0
    vim-pane:
      command: vim
      split: null
    htop:
      command: htop
      split: 
        direction: horz
        width: 40
    head:
      command: "watch tail /var/log/pacman.log"
      split:
        from: vim-paneThis will create a window, numbered 0. In it will bevimin the first pane, creating no split (split: null), a horizontal split of width 40 containing an instance ofhtop, finally, splitting vertically from the pane markedvim-panewatching a log.So, something like this,+-------------------+--------+
  |                   |        |
  |                   |        |
  |        Vim        |        |
  |                   |        |
  |                   |        |
  +-------------------+  Htop  |
  |                   |        |
  |                   |        |
  |   watch tail...   |        |
  |                   |        |
  |                   |        |
  +-------------------+--------+Note here that ordering is important, same as setting up a window regularly in tmux. So if you create two panes,aandb, then splitahorizontally, you have two on the top, one on the bottom. However, createaandbhorizontally, then splitavertically, you get two on the left and one on the right.The splits are literally made in the order they appear in the Yaml, and so, to reiterate, ordering is important.The meta config would look something like the following:<window name>:
    number: <window number>
    <pane id>:
      [command: <command>]
      [module: <module>]
      split: (null|
        [direction: (horz|vert)]
        [from: <pane id>]
        [width: <char width>]
        [height: <char height>])
    <pane 2 id>:
      ...
  <window 2 name>:
    ...DependenciesLiterally just the one, aside fromPython3, islibtmux.Additional Infomodulerefers to what you may find as an empty directory, these are to come, or for anyone who finds this to populate with scripts/binaries, its sole purpose is to put things that you may not necessarily want on your path, kind of pointless but hey.The only thing that I wouldn't advise it setting up a configuration and not taking into account the fact that the script is running in a particular pane, obviously, that module/command won't be launched.Hopefully, there's more to come.