Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro_alves@portugalmail.pt>
To: Jan Holesovsky <kendy@suse.cz>
Cc: gdb-patches@sourceware.org
Subject: Re: Patches to improve the gdbtui user experience
Date: Sat, 15 Sep 2007 21:08:00 -0000	[thread overview]
Message-ID: <46EC49B5.8090901@portugalmail.pt> (raw)
In-Reply-To: <46EC0FC8.3020704@portugalmail.pt>

Pedro Alves wrote:
> Jan Holesovsky wrote:
>> don't quit
>>       SingleKey by 'q' when it's activated by a nontrivial ctrl+x
>  >       combination - the user is smart enough to exit this mode.
> 
> If the only command gdb knows starting with 'q' is "quit", what
> is the use?  What is it preventing you to type?  Maybe
> a target/host specific command?  At least on cygwin 'q' is not
> ambiguous.  On the other hand, if you're in in single key mode, and
> want to type "quit", you have to type "qquit", since the first 'q' is
> eaten, else you'll end up typing "uit" :)  I guess it's a matter of
> personal taste either way.
> 

Let me just add a note to say that in my opinion, entering
'one command mode' with any other key (that is, a key that
has no binding in 'single key mode'), is broken.  One has to
remember which keys are bound, and which aren't - that makes
it too easy to accidently issue some command you didn't
want to.  Something like pressing <space> to enter 'one
command mode' would make much more sense to me - principle of
least surprise.

eg:
I want to type 'info something', and I currently can because
'i' is not bound to anything.  With your patch, 'i' would
stepi.  There ya go, I just stepped accidently, possibly over a
jmp, when I didn't want to.  I might have wanted to 'return 0',
for example.

Cheers,
Pedro Alves



      reply	other threads:[~2007-09-15 21:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-14 11:57 Jan Holesovsky
2007-09-14 14:25 ` Daniel Jacobowitz
2007-09-15 17:01 ` Pedro Alves
2007-09-15 21:08   ` Pedro Alves [this message]

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

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

  git send-email \
    --in-reply-to=46EC49B5.8090901@portugalmail.pt \
    --to=pedro_alves@portugalmail.pt \
    --cc=gdb-patches@sourceware.org \
    --cc=kendy@suse.cz \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox