git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Pratyush Yadav <me@yadavpratyush.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] git-gui: allow closing console window with Escape
Date: Mon, 9 Dec 2019 01:10:46 +0530	[thread overview]
Message-ID: <20191208194046.csf35b7rgycst2vc@yadavpratyush.com> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.1912071723010.31080@tvgsbejvaqbjf.bet>

On 07/12/19 05:24PM, Johannes Schindelin wrote:
> Hi,
> 
> On Sat, 7 Dec 2019, Pratyush Yadav wrote:
> 
> > It is often expected that popup windows like the console window be
> > close-able with Esc.
> 
> Seeing as the console windows is not your regular popup window with an
> "OK" button, I could see how it would be all too easy to close the window
> via the Esc button all too easily, annoying users.

I'm not sure why it is "too easy" to hit Escape. If you're hitting Esc 
(which for most people is pretty far from other more frequently used 
keys) you expect _something_ to happen. People don't just spam Esc for 
no reason, do they?
 
> For windows like the console one, I would expect Ctrl+W a much more
> natural keyboard shortcut to close it.

But, that "something" the user expects to happen could also be "stop the 
command". AFAIK, Esc is often expected to stop commands. But closing the 
console window won't actually stop the command. It will keep running in 
the background, and when the command is done, the window will open again 
showing the final output.

So all in all, I do think Ctrl-W would be a better idea. Will re-roll.
 
> Ciao,
> Dscho

-- 
Regards,
Pratyush Yadav

  reply	other threads:[~2019-12-08 19:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-06 22:20 [PATCH] git-gui: allow closing console window with Escape Pratyush Yadav
2019-12-07 16:24 ` Johannes Schindelin
2019-12-08 19:40   ` Pratyush Yadav [this message]
2019-12-09  9:18     ` Johannes Schindelin
2019-12-09 15:53       ` Vasili Novikov
2019-12-10 12:02         ` Pratyush Yadav
2019-12-10 12:11           ` Vasili Novikov
2019-12-10 13:31             ` Pratyush Yadav
2019-12-13 13:29               ` Johannes Schindelin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20191208194046.csf35b7rgycst2vc@yadavpratyush.com \
    --to=me@yadavpratyush.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).