Hello! When I select 'Read-Only' from the context menu and and scrolls above to start reading something, a keystroke (though not visible on terminal) scrolls the screen to command line. 'Read-Only' should not only not print the characters on the terminal but should ignore the keystrokes altogether in true read-only spirit. A primitive version of this can be achieved by disabling 'Scroll on keystroke' when 'Read-Only' is selected so that the screen doesn't scroll in read-only mode on keystroke. Not sure how to completely ignore the keystroke. Thanks!
Hello! I'm unsure about this request... the "read-only" mode does prevent a user from inputting anything into the terminal; but "scroll on keystroke" sounds like a totally different issue to me - for example, shift+ctrl+up/down arrow combination still works for scrolling (as I believe it should). Besides, both gnome-terminal and tilix do not suppress "scroll on keystroke" while in the "read-only" mode.
My use case is this: 1. I have run some commands and so now the screen has been scrolled 2. Now, I scroll above to analyze some previous o/p 3. While analyzing the o/p I select 'Read-Only' from the context menu as I just want to analyze that previous o/p and don't want anything (keystroke etc.) to interfere with this 4. But now while I'm reading/analyzing that previous o/p some key gets pressed by mistake and now though I'm in Read-Only mode the terminal immediately scrolls down to the command-line replacing what I was analyzing from the screen. I set "Read-Only" mode specifically to make Terminal ignore any keystroke (be read-only) but instead when a key gets pressed the terminal scrolls to the command line destroying what was on the screen. Regarding gnome-terminal also doing the same, I'll file the report there too. (Let me first install and reproduce it on my end)
Issue for gnome-terminal filed here: https://gitlab.gnome.org/GNOME/gnome-terminal/issues/159
It's all in VTE, a common component used by xfce4-terminal, gnome-terminal, tilix and many others. Once fixed there, all these apps will have it fixed.
Okay, since the requested change is gonna be made in vte, I'm closing this bug as "invalid".