-
-
Notifications
You must be signed in to change notification settings - Fork 90
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
asyncronous log search #783
Comments
Not possible to do using virtual files |
Also dont currently have a way to kill commands |
Also repo with 1873207 revisions takes 30 seconds for me. |
Technically it's possible with redirecting to file in temp directory. Not sure whether it's that useful, as for me searching in terminal is more convenient, and you always can redirect it to vscode ( |
Yeah using a tmp file would work. Does vs code continously update files once they have been rendered? i.e. the command opens the file. vs code renders the empty file. Then does it check if the file has changed and add the new text or does it wait for user interaction like clicking on the file or swtiching tabs? I think it will be lazy for performance reasons. |
I stand corrected it will render it as it streams |
Vscode updates file's content even if the user doesn't do anything. Tested with: |
|
ignore
|
🎉 This issue has been resolved in version 2.7.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Issue
From #782
In my case (repo with about 250k revisions) searching is too long. There is no output until server scans all revisions. Line by line reading and outputing would be much useful. And maybe stop command or something.
The text was updated successfully, but these errors were encountered: