Skip to content
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

[Quick Open Project] Conflicting keyboard shortcut #15598

Open
davidmondok opened this issue Nov 29, 2024 · 4 comments
Open

[Quick Open Project] Conflicting keyboard shortcut #15598

davidmondok opened this issue Nov 29, 2024 · 4 comments
Assignees
Labels
extension: quick-open-project Issues related to the quick-open-project extension extension Issues related to one of the extensions in the Store feature request New feature or improvement

Comments

@davidmondok
Copy link

davidmondok commented Nov 29, 2024

Extension

https://www.raycast.com/zerowidth/quick-open-project

Description

The keyboard shortcut for opening the default editor + terminal is Shift + CMD + E. If an alternate editor is configured, the same shortcut is now used for opening the alternate editor basically removing the option to open the default editor + terminal via a shortcut. It would be great to make these shortcuts either configurable or at least make them all unique.

Otherwise awesome shortcut, definitely in my top 3 👍

@davidmondok davidmondok added extension Issues related to one of the extensions in the Store feature request New feature or improvement labels Nov 29, 2024
@raycastbot raycastbot added the extension: quick-open-project Issues related to the quick-open-project extension label Nov 29, 2024
@raycastbot
Copy link
Collaborator

raycastbot commented Nov 29, 2024

Thank you for opening this issue!

🔔 @zerowidth @bjw-s @mattstein you might want to have a look.

💡 Author and Contributors commands

The author and contributors of zerowidth/quick-open-project can trigger bot actions by commenting:

  • @raycastbot close this issue Closes the issue.
  • @raycastbot close as not planned Closes the issue as not planned.
  • @raycastbot rename this issue to "Awesome new title" Renames the issue.
  • @raycastbot reopen this issue Reopens the issue.
  • @raycastbot assign me Assigns yourself to the issue.
  • @raycastbot good first issue Adds the "Good first issue" label to the issue.
  • @raycastbot keep this issue open Make sure the issue won't go stale and will be kept open by the bot.

@zerowidth
Copy link
Contributor

zerowidth commented Dec 2, 2024

Acknowledged, you can tell how little I use this specific keybind. What do you think about:

  • cmd-E for "open in editor", along with enter (current binding)
  • cmd-shift-E for "open in alternative editor" (current, conflicted)
  • cmd-o for "open with..." (current binding)
  • cmd-shift-o for "open in both editor and terminal" (new)

@zerowidth
Copy link
Contributor

@raycastbot assign me

@davidmondok
Copy link
Author

I agree that it's better to assign a new binding for "open in both editor and terminal" than "open in the alternate editor" as I'm sure more people use the latter.

I'd personally suggest cmd-b as b in both. But I would be absolute fine with cmd-shift-o. In the end it doesn't really matter as long is it works :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
extension: quick-open-project Issues related to the quick-open-project extension extension Issues related to one of the extensions in the Store feature request New feature or improvement
Projects
None yet
Development

No branches or pull requests

3 participants