search

microsoft / vscode

Visual Studio Code
https://code.visualstudio.com
MIT License
161.63k stars 28.4k forks source link

open folder with vscode not work under kubuntu24.04LTS #221286

Open wyjBot opened 1 month ago

wyjBot commented 1 month ago

Does this issue occur when all extensions are disabled?: Yes

VSCodeTriageBot commented 1 month ago

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.91.0. Please try upgrading to the latest version and checking whether this issue remains.

Happy Coding!

wyjBot commented 1 month ago

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.91.0. Please try upgrading to the latest version and checking whether this issue remains.

Happy Coding!

I want to claim the latest version is remain unavailable. I have tried code_1.91.0-1719861592_amd64.deb.

alexr00 commented 1 month ago

/gifPlease

VSCodeTriageBot commented 1 month ago

Thanks for reporting this issue! Unfortunately, it's hard for us to understand what issue you're seeing. Please help us out by providing a screen recording showing exactly what isn't working as expected. While we can work with most standard formats, .gif files are preferred as they are displayed inline on GitHub. You may find https://gifcap.dev helpful as a browser-based gif recording tool.

If the issue depends on keyboard input, you can help us by enabling screencast mode for the recording (Developer: Toggle Screencast Mode in the command palette). Lastly, please attach this file via the GitHub web interface as emailed responses will strip files out from the issue.

Happy coding!

johnottone commented 1 month ago

This "Open with Code" issue has been raised multiple times in this forum, specifically for windows 11 and it keeps getting closed but it's not fixed. There are several things at play here. First when you right click a file, like an .md or .cs or .txt you should have an option to "Open w&ith Code" and likewise on ANY directory you should have the same option. Thats how it is in Windows 10. if you uninstall VSCode and do a clean user install the installer gives you some checkboxes to implement it into the shell...And it just works! OK...Now on Windows 11, you do the same thing, but it is not handled the same way. There is the default context menu (That has Show more Options at the bottom) and the classic context menu (the same one as in Windows 10) Everything is fine if you go to the bottom and click Show more Options, THEN click "Open With Code" but it gets really tiresome adding just ONE extra step, especially when you have a demanding workload and constantly opening up directories with customer data all day. The "Open with Code" is kind of there for files in the default context menu, but still not the same as in Windows 10. The only thing i hear is "Use this workaround".... or ...Hey just set the classic context menu as the default, If you want to get technical you can right click a directory and then click Open in a terminal, then type "code ." and it will open VSCode to that directory, but Noone should have to do all that And I must use what my customers use, which is windows 11, and we require all our support to become proficient with the Windows 11 defaults, so they can help customers more efficiently. We can't tell our customers to click on "Open with Code", when it's not available, because they are using the CORRECT context menu and I'm using some workaround with something different. And They couldn't use the workaround anyway because they are locked down with group policies and can't change such things as "setting their context menu to the classic". Now of course there are people who have implemented the windows API and windows shell ....they are on GitHub, but again, I am not using 3rd party software just to make my context menu show the hidden handlers and I can't very well have my customers change it either as I do not control their group policies but I'm sure they are not allowed to install 3rd party shell implementations or even modify their registry, and they shouldn't have to. But it seems like VSCode is putting the registry entries where they should go but, the windows API (windows shell, specifically) seems to be overriding that. Is there anything we can do to help with this issue to get it fixed once and for all?