Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Post History
When you do: cd /some/path code . VS Code opens with that location shown in the "Explorer" sidebar. However, the state of the file tree and the currently open files will be the same as what wa...
Question
vs-code
#2: Post edited
by
matthewsnyder
·
2023-10-06T14:29:59Z (about 1 year ago)
- When you do:
- ```sh
- cd /some/path
- code .
- ```
- VS Code opens with that location shown in the "Explorer" sidebar. However, the state of the file tree and the currently open files will be the same as what was remembered from the last session.
Let's say that last time I was editing `/some/path/foo/bar/baz` and closed VS Code. I'm done with `/some/path/foo/bar/baz`. Now I want to edit `/some/path/completely/different/path`. When I open VS Code in `/some/path` (particularly there, because it happens to be a Git repo) I must tediously close the old open files, collapse all file tree nodes, open the new ones, and start editing.- Is there a way to use the `code` CLI to start VS Code with *only specified folders expanded*?
- It's okay if the command is complicated, I can wrap it in a script.
- When you do:
- ```sh
- cd /some/path
- code .
- ```
- VS Code opens with that location shown in the "Explorer" sidebar. However, the state of the file tree and the currently open files will be the same as what was remembered from the last session.
- Let's say that last time I was editing `/some/path/foo/bar/baz` and closed VS Code. I'm done with `/some/path/foo/bar/baz`. Now I want to edit `/some/path/completely/different/path`. When I open VS Code in `/some/path` (particularly there, because it happens to be a Git repo) I must tediously close the old open files, collapse all file tree nodes, open the new ones, and start editing. I figured out how to [set the open editors](https://software.codidact.com/posts/289857/289860#answer-289860), but the explorer is still set to the last state. It does expand to the file that I open, but does not collapse other folders.
- Is there a way to use the `code` CLI to start VS Code with *only specified folders expanded*?
- It's okay if the command is complicated, I can wrap it in a script.
#1: Initial revision
by
matthewsnyder
·
2023-10-06T14:25:19Z (about 1 year ago)
How to open VS code with a particular path expanded?
When you do: ```sh cd /some/path code . ``` VS Code opens with that location shown in the "Explorer" sidebar. However, the state of the file tree and the currently open files will be the same as what was remembered from the last session. Let's say that last time I was editing `/some/path/foo/bar/baz` and closed VS Code. I'm done with `/some/path/foo/bar/baz`. Now I want to edit `/some/path/completely/different/path`. When I open VS Code in `/some/path` (particularly there, because it happens to be a Git repo) I must tediously close the old open files, collapse all file tree nodes, open the new ones, and start editing. Is there a way to use the `code` CLI to start VS Code with *only specified folders expanded*? It's okay if the command is complicated, I can wrap it in a script.