tmuxp VS vim-projectionist

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

Tim Pope's projectionist for navigating to files of a particular category or to related files from the current one: https://github.com/tpope/vim-projectionist.

> For myself, I'm fine with the typing being in a separate .rbs file

We type[0] by having one separate .rbs file per .rb file. Works really well with an editor's vertical splits: type outline on one side, code on the other. That, or use something like vim-projectionist[1].

[0]: (WIP: there's a huge codebase to type, but we're progressively getting there) https://github.com/DataDog/dd-trace-rb/tree/master/sig

[1]: https://github.com/tpope/vim-projectionist

One of the originals I guess must be tim pope's https://github.com/tpope/vim-projectionist

use https://github.com/tpope/vim-projectionist - define the relationships between files (example: app/*js are 'source' files and test/*js are 'test' files). Projectionist sets up `:A` to jump to the 'alternate' file (jump between a 'source' file and its 'test' for instance), and `:Esource` and `:Etest` commands to find/navigate by the kind of file. This is very powerful IMO - for projects with good structure I can quickly jump between related test/source/model/blah files very quickly using these commands. For projects without good structure I rethink or get the team to talk about how we might improve the project organization (ie, lack of structure is a code smell!)

I love Tpope’s https://github.com/tpope/vim-projectionist but this one seems like a great replacement 😎

Tim Pope's excellent Projectionist plug-in has an alternate file feature, which makes it very easy to switch between test and implementation files.

The plugin is inspired by vim-projectionist and https://github.com/vim-scripts/a.vim

This feels like a bug, since the plugin doesn't behave as expected when following the installation section verbatim. I filed a bug here: https://github.com/tpope/vim-projectionist/issues/168

You need https://github.com/tpope/vim-projectionist. Gotta have a file structure for unit tests though.