-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
Open recent project in new window is inconsistent #21245
Comments
I just realized that method 1 above has this text:
whereas methods 2 & 3 have this (the exact opposite):
This seems like #20176 or #17765 (see also #20201) were never really fixed. But the menu that opens otherwise looks the EXACT SAME. This is so confusing to the end-user... |
Yeah this is less than ideal. I believe the thought is that the title bar is a "Project Switcher" and File->Open Recent ( There a need for a design review to better differentiate/refine these. I think it might also be appropriate to support MacOS style For example, if there was real-time feedback when holding option (or command) which changed button labels it would be clearer which action you were about to do. Thanks for reporting. |
@notpeter Again, this is less about the "tooltip" text that appears and more about the fact that when you follow the tooltip instructions to open a project in a new window it does NOT open in a new window! The ability to consistently get projects to open in a new window (or not) is what I want, regardless of whether it matches the tooltip text. But at this time neither enter or cmd-enter result in consistent behavior for me :( |
I also have noticed the strange behavior of this functionality in Linux. For me there seems to be two different versions of those lists - the one appearing when I open zed from terminal and the other one when I open it from searching in Gnome shell. I would like this to give same list in Linux as well if possible. |
Again, my main concern is that the option for "opens a new one" (a new window) does not work consistently. That is, it opens in the SAME window most of the time for me! But as I stated, I can somehow get it into a "mode" where it finally does what I ask it to do (i.e. what it says it will do) and open the project in a new window. But I have no idea what I am doing to convince it to enter/exit this "mode" where it actually does what the help text says it will do... I just want the editor to work as it says it will work. If it says "enter to open in this window" and "cmd+enter to open a new one" then just do that. But if it's reversed then do that. I don't care so much that all of the ways to get to the recent projects window don't have the same help ("tooltip") text. I just want Zed to do what its own text says it will do! Just please do what you say you're gonna do, Zed!! Stop lying to me!!! |
Check for existing issues
Describe the bug / provide steps to reproduce it
I do not know how to reproduce this bug. But if you continue to attempt to open a recent project in a new window via the 3 means available to you (see below) you will inevitably run into it.
When I get into a "mode" where it will accept enter (#1) or cmd-enter (#2 & #3) as opening the project in a new window then it seems to work as I expect repeatedly, regardless of how I opened the "Open recent project" window (see the 3 methods above). But if I ever get it into a "mode" where it ignores the new window directive (i.e. it just opens the project in the current window anyway) then it seems to retain that behavior for repeated attempts 🤷♂️ Again, I have no idea what I am doing to switch between these "modes" of operation.
I also tried a workaround from issue #17765 in which I added the following keybind:
{ "context": "Workspace", "bindings": { "alt-ctrl-o": [ "projects::OpenRecent", { "create_new_window": false } ] } }
and it did not seem to help at all.
Environment
Zed: v0.162.4 (Zed)
OS: macOS 14.7.1
Memory: 16 GiB
Architecture: x86_64
If applicable, add mockups / screenshots to help explain present your vision of the feature
No response
If applicable, attach your Zed.log file to this issue.
Zed.log
The text was updated successfully, but these errors were encountered: