The launch command is simply wsl -d tmux_posh
TMUX RENAME WINDOW WINDOWS
Set up a PowerShell Core tmux profile in Windows Terminal, ConEmu, or however you prefer. Set -g default-terminal "screen-256color"Ĭreate a ~/.profile with the following: if tmux has-session -t=posh thenĮxec tmux new-session -s posh -n PowerShell # Recommended, to avoid the Ctrl+B finger-gymnastics # Give this tmux a "PowerShell blue" color to differentiate it Set the default user for the instance by creating /etc/wsl.conf with the following contents: Įxit the session, relaunch with wsl ~ -d tmux (omitting the username, since it will now default to the tmux user)Ĭreate a ~/.nf with the following: set -g default-command "cd $(pwsh.exe -c 'Write-Host -NoNewLine \$env:userprofile' | xargs -0 wslpath) exec pwsh.exe -nologo" Launch the WSL instance as root with wsl -d posh_tmux -u root Mkdir $env:userprofile\Documents\WSL\images mkdir $env:userprofile\Documents\WSL\instances # Or wherever you want to set this up You could just use the default Alpine instance, but I like to have single-purpose WSL instances, similar to Docker containers. I create a new, cloned WSL instance for PowerShell tmux. I use this as the base for the tmux feature, since it has very low overhead (less than 12MB, including tmux). You don't have to enable WSL2 just WSL v1 will work fine for this (and perhaps better than WSL2). There are several ways to set this up, but here's how I'm doing it at the moment:
However, you can attach multiple clients at once, as long as the original remains open.
In a WSL instance with tmux installed, set up your ~/.nf with: set -g default-command "cd $(pwsh.exe -c 'Write-Host -NoNewLine \$env:userprofile' | xargs -0 wslpath) exec pwsh.exe -nologo" Recommended) … oh well.Although it wasn't possible when this question was originally asked, with Windows Subsystem for Linux, it's now possible to use a "real" tmux to manage PowerShell windows. I hope this post has been helpful! Although, I have to admit that this post # Setup an additional shell tmux new-window -t $SESSION:3 -n 'Shell' tmux send-keys -t 'Shell' "zsh" C-m 'clear' C-mįi # Attach Session, on the Main window tmux attach-session -t $SESSION:0 # Name first Pane and start zsh tmux rename-window -t 0 'Main' tmux send-keys -t 'Main' 'zsh' C-m 'clear' C-m # Switch to bind script? # Create and setup pane for hugo server tmux new-window -t $SESSION:1 -n 'Hugo Server' tmux send-keys -t 'Hugo Server' 'hugo serve -D -F' C-m # Switch to bind script? # setup Writing window tmux new-window -t $SESSION:2 -n 'Writing' tmux send-keys -t 'Writing' "nvim" C-m # Set Session Name SESSION = "Website" SESSIONEXISTS = $(tmux list-sessions | grep $SESSION ) # Only create tmux session if it doesn't already exist if then # Start New Session with our name tmux new-session -d -s $SESSION SESSIONEXISTS variable, defined directly under SESSION in the script. For Cleanliness, I took the output of that process and saved it in a The session name, which we’ve already conveniently stored in our $SESSION This can be done by “grep’ing” the output of tmux list-sessions for Checking if the Session Already Existsįirst, I needed a way to check whether the desired tmux session already existed If statement, and only run them if the tmux session didn’t already exist. To fix this issue, I decided to wrap the initialization commands inside of an Have to go through each window, close out whatever and was running, and then Just double up the windows in that session.
The script when there was a tmux session with the same name already, it would However, there was one issue I still had. The script would create duplicate windows if the tmuxĪt this point, I was done with the tmux script.
0 kommentar(er)
