tmuxp VS vim-rooter

Using tmux + tmuxp[1] you can load a pre-configured session and execute arbitrary shell commands for the session, window and pane. I use this to set up shells and editors in the correct dirs (and/or hosts), load lang environments, set env vars and source some zsh aliases and functions that I only want per project. The end result is that I can set up my dev environment (shells with different environments, neovim windows, test runner, various linters I don't wannt integrate into nvim) with a single "tmuxp load ".

[1]: https://github.com/tmux-python/tmuxp

As for apps: - I also use Zathura for PDFs, which is fine for me because it also has vim bindings, and I like the recolor feature. - I mostly use Alacritty + tmux for terminals, because I also use tmuxp. Although I run some quick commands in vterm. - I'm pretty happy with Firefox + Tridactyl as my main browser (by the way, I think Tridactyl is more powerful than Vimium). - My passwords are also stored in pass, which I access with pass.el and my password-store-ivy. The latter replicates some rofi script I used earlier. - I'm fine with dired for files and archives, but I run dired-do-compress or just enter tar / zip / ... commands in dired-do-async-shell-command. I don't work with that many archives anyway. - Honestly, I very rarely have to search for something across my entire machine (or home directory), and in such cases, I just run find :-) But I often use counsel-rg and deadgrep to fuzzy search across a given project.

Looks very simple I think I can do something based on ThePrimeagen's script that works for me, someone else also commented to tmuxp. It's probably better to look for solutions without having to do everything within neovim. Thanks

https://tmuxp.git-pull.com/ does the same thing, but I think it's smoother to work with. It does support freezing current panes. yaml config

Everything is configured with tmuxp and I can set the whole thing up with a single command.

https://github.com/tmux-python/tmuxp provides essential startup utility and scriptability.

tmuxp v1.12.0, GitHub, Release notes, Docs

This or users may have monorepo style projects and vim-rooter to auto-set cwd to specific directories within the project based on certain file markers (e.g. makefile, package.json, ...etc), to accomplish something like :e dir1/file.go | make would run make and then :e dir2/file2.ts | make would run npm.

maybe you are already doing this and you want to access files outside the project directory but if not I use vim-rooter to set the root dir of the project automatically when I open vim

The airblade/vim-rooter plugin is an essential part of my Neovim workflow. It automatically changes current directory (:h current-directory) for every buffer to a more natural one (like to path of its Git repository). For me this has the following benefits:

It depends where you open vim. If you are in home and open a file (even in sub directories) like nvim directory/file.txt, uour vim's current working directory (aka cwd) will be home. A way to make this automatic I think is the built in autocd (or something like that) and plugins like vim-rooter.

An alternative would be using a plugin like vim-rooter : https://github.com/airblade/vim-rooter

I just use rooter and avoid thinking about it...

There's vim-rooter, which is great.

No, it doesn't change current directory. For that, use sessions or airblade/vim-rooter (or wait around couple of months for planned 'mini.root' :) ). And, of course, you can create custom items which will change current directory.