You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the config file, we should have an option for allowing automatic creation of namedtmux(or other terminal multiplexers like zellij) sessions and what to run in them.
If the tmux session name doesn't exist already, we should create it by default. We should have this be off by default, and be an opt in feature, because a bunch of tmux sessions everywhere, sounds like pain to clean up, but here's an idea of how the feature would work:
Config File Update proposal [Draft1]
terminal_multiplexer:
# change this to true, to enable terminal multiplexer sessionsenabled: false# this can be any program name, but we'll support tmux and zellij out of the boxprogram_name: zellij# name of the session to create with: tmux new -s name# we will only create this if it doesn't already exist
- session_name: spotify_tuicommand: spt
then we could generate a script to automatically create a session for them, or just do it for them by putting that script in a cronjob to make sure those sessions always exist.
The text was updated successfully, but these errors were encountered:
This might actually make sense as a jessebot/dot_files ticket, as I've been using zellij so much that I don't use tmux much at all lately and zellij has this built in.
jessebot
changed the title
Feature Request: default tmux sessions, starting with a jukebox 🎶
Feature Request: default terminal multiplexer sessions, starting with a jukebox 🎶
Dec 25, 2022
Describe the feature you'd like, and why
In the config file, we should have an option for allowing automatic creation of named
tmux
(or other terminal multiplexers likezellij
) sessions and what to run in them.If the tmux session name doesn't exist already, we should create it by default. We should have this be off by default, and be an opt in feature, because a bunch of tmux sessions everywhere, sounds like pain to clean up, but here's an idea of how the feature would work:
Config File Update proposal [Draft1]
then we could generate a script to automatically create a session for them, or just do it for them by putting that script in a cronjob to make sure those sessions always exist.
The text was updated successfully, but these errors were encountered: