Open Haffi921 opened 1 year ago
Are you able to share your settings.json here? it could help me see if there's anything potentially conflicting.
For debugging, you can have it open while you change settings in the extension. it should update the files.excluded key as you add things to the list. On Jan 24, 2023 at 02:08 -0800, Hafsteinn Ragnarsson @.***>, wrote:
Hey! First off, I love the idea of this extension. I had the same idea, because often VSCode file explorer becomes too noisy. As far as I can see, this is the only extension that does this specific thing. However, I tried it out and followed your video. I created a scope, had it include a specific folder and switched to it. Yet my File Explorer is still the same as default. Do you have any idea what might cause this? I'm also down to help you out with this extension. I really want it for myself and just might dive into the code itself. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you are subscribed to this thread.Message ID: @.***>
I might have run into the same (or similar) issue. My issue was that I had a file in my "include" list that was deleted, which seemed to have broken the extension. When I opened my User Settings (JSON) file, and removed the file from the list, the extension kicked on and started working.
This is mainly observed behavior, I didn't poke in the code to see if this is a reasonable root cause, so it's possible there was something else going on that kicked it into gear, but now I'm back up and running! 🎉
Got the same bug. Got this error.
Note that I'm working from an entreprise managed laptops.. if it change anything.
Note that I'm working from an entreprise managed laptops.. if it change anything.
Just asked my IT guy, and this folder is sync on the server. Also note that, sometime, i'm not able to move directory and need to give administrative right to delete folder. Hope that help.
I have the same issue. I've followed the instructions and the video, set up 3 scopes .
The default base
scope:
The c-code
scope:
This should show only the src-c
folder, but shows everything.
The python-code
scope:
This should show only the src-py
folder, but shows everything.
And finally the qsp-code
scope which should show only the src-qsp
folder:
The project-scopes.activeScope
value updates correctly as it can be seen on the screenshots, but the Explorer content doesn't change at all.
I have attached the settings file (can't upload with .json
extension that's why it's .txt
.)
I don't think anything can conflict with it, there aren't a lot of extensions, but who knows.
I made a release yesterday that should make thing a bit more robust, let me know if you still get these issues.
Hey! First off, I love the idea of this extension. I had the same idea, because often VSCode file explorer becomes too noisy. As far as I can see, this is the only extension that does this specific thing.
However, I tried it out and followed your video. I created a scope, had it include a specific folder and switched to it. Yet my File Explorer is still the same as default. Do you have any idea what might cause this?
I'm also down to help you out with this extension. I really want it for myself and just might dive into the code itself.