2 ms·

This seems like something created by a genius mind but honestly I don't want to think about topology when I'm navigating files in vim. Ctrl-P is about as fancy

• demosito666 6y ago
  My thoughts exactly after I tried to read the readme for second time. However, thinking a bit more about it, I simulate something like author's kind of hierarchy with vim+tmux: for each distinct activity I usually start new tmux session (e.g. frontend, backend, terraform, etc.). For each project inside the activity I usually have 1-2 tmux windows with vim opened in the root of the repo, e.g. in the backend I'd have vim with microserviceA, vim in microserviceB, vim with shared library and a shell with REPL and docker logs. So it goes tmux session -> tmux window -> file in vim. Switching files in vim within a project is a solved problem (fzf and language servers). The downside of that is that it's not always possible to jump from a file in one vim into another within a session, I have to manually switch windows. But most of the time `gd' works if you have import paths set correctly.
  • renox 6y ago
    Interesting workflow, the main issue I have with all this is that I use several worktree and sometimes I have to switch to a different worktree.. So I'd need something which stores relative path..