[GH-ISSUE #849] Disabling/ignoring external keyboard shortcuts #618

New issue

Closed

opened 2026-03-04 01:06:29 +03:00 by kerem · 1 comment

kerem commented

2026-03-04 01:06:29 +03:00

Owner

Originally created by @alessandrodetta on GitHub (May 11, 2023).
Original GitHub issue: https://github.com/rivo/tview/issues/849

Is there a way to disable/ignore external keyboard shortcuts of other programs (i.e keeping only the ones implemented in tview itself) while running so that e.g pasted selected text in Windows Terminal doesn't gets replaced/overriden by Windows Terminal keyboard shortcut ctrl+v itself ? The same happens while running the app in Visual Studio Code terminal, but for the copy operation, which conflicts with ctrl+q.

or is it just normal behavior that the user/developer should take care of?

Originally created by @alessandrodetta on GitHub (May 11, 2023). Original GitHub issue: https://github.com/rivo/tview/issues/849 Is there a way to disable/ignore external keyboard shortcuts of other programs (i.e keeping only the ones implemented in tview itself) while running so that e.g pasted selected text in Windows Terminal doesn't gets replaced/overriden by Windows Terminal keyboard shortcut ctrl+v itself ? The same happens while running the app in Visual Studio Code terminal, but for the copy operation, which conflicts with ctrl+q. or is it just normal behavior that the user/developer should take care of?

kerem closed this issue

2026-03-04 01:06:29 +03:00

kerem commented

2026-03-04 01:06:30 +03:00

Author

Owner

@rivo commented on GitHub (Jun 18, 2023):

That's not a question for tview to answer but rather an issue with the terminal you're using. I don't know if it's possible to block certain keys from being captured by Windows Terminal or VS Code. You'll have to check out the respective documentation.

I don't believe any application running inside a terminal can break out of its sandbox and modify external shortcuts, unless that's a specific feature provided by the terminal. This would probably be a security issue. A program running inside VS Code could then keep you from closing VS Code, for example.

I think you can change the Ctrl-Q key in VS Code to something else. But that might not be what you want.

@rivo commented on GitHub (Jun 18, 2023): That's not a question for `tview` to answer but rather an issue with the terminal you're using. I don't know if it's possible to block certain keys from being captured by Windows Terminal or VS Code. You'll have to check out the respective documentation. I don't believe any application running inside a terminal can break out of its sandbox and modify external shortcuts, unless that's a specific feature provided by the terminal. This would probably be a security issue. A program running inside VS Code could then keep you from closing VS Code, for example. I think you can change the <kbd>Ctrl</kbd>-<kbd>Q</kbd> key in VS Code to something else. But that might not be what you want.

kerem referenced this issue

2026-03-04 01:08:58 +03:00

[PR #634] [MERGED] Rewrote Table to accommodate virtual tables. #1002