Keybind / option for read-only / protected mode

[whisperity]

Abstract

A new keybind action, perhaps not bound to anything by default, should be added that, when pressed, disable passing input to the underlying programs.

Motivation

Sometimes I have long-running applications, output I would like to monitor, but I'm scared that pressing ^C will kill potentially hours' worth of computation. Idea taken from KiTTY that has a "Protected" mode: if enabled, you can't interact with the shell (no mouse events or keys are forwarded), and you can't even close the window -- but output is still being refreshed on your side.

[christianparpart]

That's a very interesting idea and should be trivial to implement. It should be shown to the user in some way or the other, such that the user won't be disappointed why nothing is happening.

[whisperity]

That's a very interesting idea and should be trivial to implement. It should be shown to the user in some way or the other, such that the user won't be disappointed why nothing is happening.

All KiTTY does is put a (PROTECTED) into the title of the window, which is not quite enough. My first idea would be to change the running window's icon (I guess that is possible?) to a contour logo with a lock on it? (Get one of the nice coloured lock icons from Wikipedia! 😉 )

But I guess a lock could also be drawn somewhere in the viewport of the window, where it is expected to be unobtrusive. Top right corner?

Actually, how about all three of this?

Maybe the lock icon could be somehow justapoxed with the background image? We already have a solution for showing a background even if there is text above it! We can just put a lock in the right location, and render it as a "middleground". So on top of the background, but behind the text, and preferably not blurred, even if the background is.

[uspasojevic96]

While I agree that changing some sort of window decoration is nice, but keep in mind that some of us have decorations disabled

[christianparpart]

What about changing color scheme when in readonly-mode?

[whisperity]

What about changing color scheme when in readonly-mode?

@christianparpart The problem with that is that the underlying buffer could change in readonly mode, it's just the user that should be prevented from entering things... And changing the colours could be disruptive of that.

[christianparpart]

While the logic itself is trivial to implement, it's probably best to simply wait for #687 to be implemented, such that the visual feedback is easy, too. :)