3 ms·
In my case, often several times an hour. I work across 6-10 dofferent repositories. Opening them all at once is impractical, so being able to open each of the t
by nicoburns 7y ago
In my case, often several times an hour. I work across 6-10 dofferent repositories. Opening them all at once is impractical, so being able to open each of the them quickly is quite important.
- rhlsthrm 7y agoHave you tried multiple repositories in a VSCode workspace? It does a great job of managing multiple repos, git diffs, etc.
- nicoburns 7y agoThe problem I have with this is it makes "Go to file" functionality a bit too broad. e.g. If I want to open `package.json` I now have to choose between 10 different files. As I often `Cmd-P`, type pa, `Enter` without even looking, this makes it considerably slower. I also have to do a lot of context switching (e.g. to review someone else's code), and being able to have a separate set of tabs (even within the same repo) is super-useful for this. At previous jobs with less separated out code, I have taken this approach (although with Sublime Text rather than VSCode).
- tracker1 7y agoAgreed... deeply nested directory structures are also pretty painful. Even in the mono-repos I work with, I'll generally open an editor per inner repo. Mostly ./feature/featurename/filename is as far as I have to open. Some of the C# projects are deeper though.