public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "maayan at maayank dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug cli/11920] tab completion might stall cli without any feedback
Date: Sun, 21 Sep 2014 08:54:00 -0000 [thread overview]
Message-ID: <bug-11920-4717-YUvxmPUuua@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-11920-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=11920
Maayan Keshet <maayan at maayank dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |maayan at maayank dot com
--- Comment #2 from Maayan Keshet <maayan at maayank dot com> ---
Maybe it's difficult to resolve thoroughly, as the problem is the amount of
symbol tables and not amount of symbols (so it can happen with vastly varying
amount of symbols).
But for the meantime, can we have an option to disable the tab completion when
the inputted prefix is < $SOME_NUM? e.g. if I enter the command "noshorttab"
and do "b foo<tab>" nothing will happen.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2014-09-21 8:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-11920-4717@http.sourceware.org/bugzilla/>
2013-11-04 13:02 ` gbenson at redhat dot com
2013-11-04 16:29 ` gbenson at redhat dot com
2014-02-12 11:40 ` gbenson at redhat dot com
2014-02-14 17:22 ` dmalcolm at redhat dot com
2014-05-14 13:02 ` gbenson at redhat dot com
2014-09-21 8:54 ` maayan at maayank dot com [this message]
2015-01-31 23:15 ` cvs-commit at gcc dot gnu.org
2015-01-31 23:27 ` cvs-commit at gcc dot gnu.org
2015-03-28 22:13 ` xdje42 at gmail dot com
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=bug-11920-4717-YUvxmPUuua@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@sourceware.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.
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).