Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Quick Open - Invesigate the costs of persisting our file cache #15382

Closed
chrmarti opened this issue Nov 11, 2016 · 3 comments
Closed

Quick Open - Invesigate the costs of persisting our file cache #15382

chrmarti opened this issue Nov 11, 2016 · 3 comments
Assignees
Labels
feature-request Request for new features or functionality *out-of-scope Posted issue is not in scope of VS Code search Search widget and operation issues

Comments

@chrmarti
Copy link
Contributor

No description provided.

@chrmarti chrmarti added plan-item VS Code - planned item for upcoming search Search widget and operation issues labels Nov 11, 2016
@chrmarti chrmarti added this to the November 2016 milestone Nov 11, 2016
@chrmarti chrmarti self-assigned this Nov 11, 2016
@eddy-geek
Copy link

I am currently using vscode on an sshfs fuse filesystem, and I think this feature would help a lot for navigation in such cases (currently quick open is too slow so I have to navigate in the project explorer tree). Is the cost analysis still ongoing?

@1st
Copy link

1st commented Apr 25, 2017

Please look into Sublime Text to see how it works. I also use sshfs and with Sublime it works perfectly. Inside the VS Code it's very slow to go to file or go to definition inside the workspace.

Any estimates about when will it be done?

P.S. And please, save all cache and settings files in one place - in ~/.vscode folder, to avoid spreading configs and cache files on differen locations.

@chrmarti chrmarti added the *out-of-scope Posted issue is not in scope of VS Code label Nov 30, 2017
@vscodebot
Copy link

vscodebot bot commented Nov 30, 2017

This issue is being closed to keep the number of issues in our inbox on a manageable level, we are closing issues that have been on the backlog for a long time but have not gained traction: We look at the number of votes the issue has received and the number of duplicate issues filed. If you disagree and feel that this issue is crucial: We are happy to listen and to reconsider.

If you wonder what we are up to, please see our roadmap and issue reporting guidelines.

Thanks for your understanding and happy coding!

@vscodebot vscodebot bot closed this as completed Nov 30, 2017
@chrmarti chrmarti removed this from the Backlog milestone Nov 30, 2017
@vscodebot vscodebot bot locked and limited conversation to collaborators Jan 14, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
feature-request Request for new features or functionality *out-of-scope Posted issue is not in scope of VS Code search Search widget and operation issues
Projects
None yet
Development

No branches or pull requests

4 participants