Confirmation before executing a shell command #27
Replies: 3 comments 1 reply
-
I think its a great idea @Taitava ! One more feature to the |
Beta Was this translation helpful? Give feedback.
-
Nice. Btw does it need a description field too? For describing how the command can be dangerous. But maybe it's better to start without a description field, as that would fill the UI space in the cog modal/alias modal/whatever we should call the popup window. |
Beta Was this translation helpful? Give feedback.
-
I created now issue #35 for this. I'm leaving out:
These can be implemented later, in separate issues, but they can still be discussed here. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Some commands can be quite dangerous, especially if they involve deleting files, writing to files, or use unpredictable variables such as
{{selection}}
or{{clipboard}}
(there is no way to escape/encode variable values at the moment).I'd like to add a simple toggle for each shell command. If the toggle is on, then every time the user tries to execute the shell command, they are prompted like this:
Later I could add an option to only confirm if the command is executed via a certain way. E.g. executing via command palette does not require confirmation (because a user can see variables in the command palette), but executing via a hotkey requires a confirmation. This could decided on a per command basis.
Beta Was this translation helpful? Give feedback.
All reactions