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
[1Password] Can't get "Open in 1Password" secondary action to work #12177
Comments
Thank you for opening this issue! 🔔 @khasbilegt @thomaspaulmann @dteare @pernielsentikaer @cb372 @henrik-dmg @justspacedog @kjeldahl @superwhys @Luk4h you might want to have a look. 💡 Author and Contributors commandsThe author and contributors of
|
I can't reproduce it, What type of Item are you trying to use this action on? I was able to open in 1Password via the secondary action (⌘+↩) and on the action panel (⌘+K). |
Does that mean your ⌘+K menu has an item for "Open in 1Password"? That's
interesting! I will poke around a bit to see why mine doesn't.
…On Sat, May 4, 2024 at 5:07 PM Luiz Gustavo Marcondes < ***@***.***> wrote:
I can't reproduce it, What type of Item are you trying to use this action
on? I was able to open in 1Password via the secondary action (⌘+↩) and on
the action panel (⌘+K).
—
Reply to this email directly, view it on GitHub
<#12177 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAE5FV3A2PIF2DHGHRIAFQ3ZAVZ23AVCNFSM6AAAAABHHF4XXOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJUGUYDOMRQGQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Extension
https://www.raycast.com/khasbilegt/1password
Description
I have "Open in 1Password" set as my secondary action, as seen here:
However, I can't seem to find any way to trigger this secondary action. The actions menu doesn't show it:
Pressing Cmd-Enter just opens the website in the browser.
I expected Cmd-Enter to trigger "open in 1Password", or for it to be otherwise available somewhere on the Cmd-K menu.
Thanks!
Steps To Reproduce
See above.
Current Behaviour
No response
Expected Behaviour
No response
The text was updated successfully, but these errors were encountered: