You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
This one was a doozy. Took me some time to understand what the hell was happening.
The latest Perplexity 3.1.1 has keyboard shortcuts that are enabled by default.
The issue is, that even if the app is closed, the shortcuts are still monitored.
So, for example, if you have shortcuts in other apps, such as Firefox, where CTRL+Shift+T opens the last closed tab, these will no longer work in Firefox, because they are reserved by Perplexity app. Another example is CTRL+1 in Spyder IDE, which comments a block of code. This will also be reserved by Perplexity app and will not operate within Spyder.
I believe the correct operation of the shortcuts would be enabling them only when Perplexity app is in focus. Or, at least, have an option to disable them altogether
I changed the shortcuts to longer combinations of buttons and this solved the issues I was having.
The text was updated successfully, but these errors were encountered:
Hello,
This one was a doozy. Took me some time to understand what the hell was happening.
The latest Perplexity 3.1.1 has keyboard shortcuts that are enabled by default.
The issue is, that even if the app is closed, the shortcuts are still monitored.
So, for example, if you have shortcuts in other apps, such as Firefox, where CTRL+Shift+T opens the last closed tab, these will no longer work in Firefox, because they are reserved by Perplexity app. Another example is CTRL+1 in Spyder IDE, which comments a block of code. This will also be reserved by Perplexity app and will not operate within Spyder.
I believe the correct operation of the shortcuts would be enabling them only when Perplexity app is in focus. Or, at least, have an option to disable them altogether
I changed the shortcuts to longer combinations of buttons and this solved the issues I was having.
The text was updated successfully, but these errors were encountered: