-
Notifications
You must be signed in to change notification settings - Fork 2
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
[Feature request] Resursively close files from command palette [Don't fixed] #1
Comments
Good idea. Will work on it. |
Hey just noticed that there is something wrong here. CloseFolder can't go back in hierarchy. So when you give CloseFolder command from |
Added the Command Palette option in new release v1.1.0 |
My feature request about go back in hierarchy( . Thanks. |
@Kristinita Well that's not possible because there is no way to define a fixed point of how back we should go in the hierarchy. Suppose, if we go unlimited levels back, we would end up closing all open tabs. (when you have just one folder in project) This is obviously something you don't want. |
@aviaryan , I save my projects, for example, in paths Thanks. |
I guess I should close this issue now as this feature can't be implemented under the scope of the project. Though the command palette addition of the command is really cool. So thanks for the report @Kristinita . |
@aviaryan , the problem not solved. I think, that will be better reopen issue — perhaps, other developers add this feature. Thanks. |
1. Request
It would be nice, if will be possible to close files recursively from command palette.
2. Justification
I think, that working in command palette — is better. This saves time in comparison with navigation in the sidebar. About more reasons see here.
3. Desirable behavior
For example, I have folder
RootFolder
:FirstFile.txt
,SecondFile.txt
andThirdFile.txt
open for me in Sublime Text. I open tab withFirstFile.txt
→ Ctrl+Shift+P →CloseFolder: Close Folder Recursively
→ all files inRootFolder
, includeSecondFile.txt
andThirdFile.txt
close for me.Thanks.
The text was updated successfully, but these errors were encountered: