![]() Now let’s create a simple session sessionsĮach session is described in a separate configuration file. So, just download the sources (or at least one mucks file) - and you’re ready to use it: git clone (right, there are test frameworks for UNIX Shell as well). I also tried to do some tests at least for the configuration parser It’s also just one file of ~100LOC, so it should not be hard to read or to Screen and tmux) is sed, so in theory it should be highly portable. Seems like the only external program it uses (other than Mucks (btw, it also means “protest” in German) is written in UNIX Shell, and I That’s how I started my own session manager for both, tmux and screen. Tmux-oriented, and it seems like nobody cares about the good old GNU Screen. So, I quickly googled for other alternatives, and found that most of them are Install ruby to just manage terminal sessions?! What’s wrong with this world?! Honestly, I never heard about session management tools until Manually and started programs manually and then just attached/detached until Since my laptop’s uptime is normally more than a month - I just created windows There has been a lot of talks about screen vs tmux, and then vs byubu. I used to use GNU Screen a couple of years ago, then I switched to Tmux. Sort output of Dir.glob for consistency #506 "Sort output of Dir.glob for consistency" - fix for CIĪttempt at salvaging PR #479 #507 "Attempt at salvaging PR Support specified config directory and XDG Base Dirs Spec #479" - Work around Sort output of Dir.I can’t imagine my daily work in terminal without multiplexers. Spec" - Did not run correctly in CI environment Revert "Support specified config directory and XDG Base Dirs Spec" #505 "Revert "Support specified config directory and XDG Base Dirs ![]() Support specified config directory and XDG Base Dirs Spec #479 "Support specified config directory and XDG Base Dirs Spec". Sort gem dependencies into alphabetical order Rename Config#project_in_local -> Config#local_projectįit with the naming of both global_project and default_project Shorter and corresponds to the naming of default_project Rename Config#project_in_root -> Config#global_project Nomenclature misleading as it implies a single directory. That two directories may contain project files, making the root Implementing XDG Base Dirs support with backwards compatibility means May be either $TMUXINATOR_CONFIG, $XDG_CONFIG_HOME/tmuxinator or This directory is the only one used when creating new project files, and Update commands implode and list to operate upon thisĪdd aliases for the 3 renamed methods below for backward Of returning only the first project file found in a recursive search ofĪdd Config#directories: an array of the configuration director Document in comments and tests the existing behaviour ![]() When loading a project, search $XDG_CONFIG_HOME/tmuxinator before (including its parents) if it does not exist. $XDG_CONFIG_HOME/tmuxinator for new projects. If neither ~/.tmuxinator nor $XDG_CONFIG_HOME/tmuxinator exist, use If $XDG_CONFIG_HOME/tmuxinator exists, create new projects there. With regards to user specific configuration files: Look for tmuxinatorĬonfiguration files under $XDG_CONFIG_HOME/tmuxinator.įor existing setups with no $XDG_CONFIG_HOME directory, continue toĬreate new projects in ~/.tmuxinator for backwards compatibility. Honour the XDG Base Directories Specification Specified, this will be the only configuration location used. Thisĭirectory takes preference over honouring the XDG specification (below). Will be created (including its parent directories) if it doesn't exist. Mentioned in Issue #427 - "Introduce Analytics Module"Īllow $TMUXINATOR_CONFIG to specify a configuration directory, which Resolve Issue #360 - "XDG base directory support" Resolve Issue #462 - "Tmuxinator config files in a different location" Allow setting config directory and honour XDG Base Dirs Spec ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |