Change default `Appliation.QuitKey` to `Esc` from `Ctrl-Q` about terminal.gui HOT 6 CLOSED

I absolutely agree changing the current Ctrl+Q to Esc or any other program that does not interact with any other program, especially VS2022 or VSCode, where Ctrl+Q is intercepted by any of the aforementioned, instead of the developed application, if we are using an integrated terminal. I know it is possible to change the shortcut for these applications but it would be better to change the Terminal.Gui shortcut.

from terminal.gui.

Escape is also not exactly a hard standard, and is in fact used by some software as what it is - the escape key¹, not a "quit application" key.

Even in Unixy systems, it's all over the place.

Three of the most commonly used utilities, emacs (ctrl-x, ctrl-c, or esc-x depending on distro defaults), vi (esc if in any other mode and then :q), and nano (ctrl-x), all have different means of exiting. In fact, vi is a big case for esc NOT meaning quit.

As such, I think it's fine we default to ctrl+Q, as it's unlikely to be otherwise bound beyond the scope of the application using TG.

from terminal.gui.

OCGV has used esc for 4 years with tons of Mac and Linux users. None have complained.

I think the default quit key should be esc on all platforms. With CM it is trivial for users to change this if they don't like it.

from terminal.gui.

It would be nice if everyone would just adopt one.

My main opinion on it is basically it ain't broke, so don't fix it.

But it's also unimportant for exactly this reason, so it's not worth more back and forth if you want to change it regardless 🤷‍♂️ :

it is trivial for users to change this if they don't like it.

Just wanted to point out an alternative viewpoint based on what TG is and the environments it is most likely to exist in, basically. If it weren't configurable, then it would register on the ol' care-o-meter a lot more and warrant polling or some sort of actual statistical research. But it is, so it doesn't move the needle as far as I'm concerned.

Definitely warrants a high-visibility bullet point in migration docs though, for any change to that.

from terminal.gui.

Yeah I think we're all aligned on this, more or less.

I did run into am interesting one a few days ago that made me think about it again.

But the fact that it is trivially configurable both in code and configuration files really just solves the problem entirely, so it's cool whatever it ends up being, within reason . 👍

Still needs to be loudly documented of course.

I'd even suggest that, in samples and "getting started" type documentation, we repeat what the default quit key is, perhaps in a short bulleted list of important concepts for the given doc/sample, plus a simple link to the config docs, so it's dead simple for a consumer, and any potential "how do I exit‽" issues posted can be closed with a well-deserved "RTFM" linked to any one of those. Plus that would boost their ranking in search engines. 👌

from terminal.gui.

Besides, it's already one of the oldest jokes in terminal-land that there are users out there who have been stuck inside vi for years, because they can't figure out how to exit. That'd be a fun little easter egg kind of reference to subtly make somewhere in docs or code comments. 😅

from terminal.gui.