public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "palves at redhat dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug cli/26180] tab completion needs whitespace escaping Date: Mon, 06 Jul 2020 14:23:28 +0000 [thread overview] Message-ID: <bug-26180-4717-DUfUZ87Adj@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-26180-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=26180 Pedro Alves <palves at redhat dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |palves at redhat dot com --- Comment #2 from Pedro Alves <palves at redhat dot com> --- I actually have a branch that implements that. https://github.com/palves/gdb/commits/palves/filename-options I ran into this while implementing support for filename options in the gdb::option framework, for "add-inferior -exec FILENAME". With that, this works: (gdb) shell touch a\ b (gdb) run a\ [TAB] (gdb) run a\ b As well as: (gdb) add-inferior -exec a\ [TAB] (gdb) add-inferior -exec a\ b The branch also makes GDB's single quoting behaves like Bash's. Currently single and double quoting behave the same in GDB. I need to find time to clean that up and submit it upstream. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2020-07-06 14:23 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-29 11:21 [Bug gdb/26180] New: " noelgrandin at gmail dot com 2020-06-29 11:21 ` [Bug cli/26180] " noelgrandin at gmail dot com 2020-07-04 17:23 ` tromey at sourceware dot org 2020-07-06 14:23 ` palves at redhat dot com [this message] 2020-08-24 16:19 ` noelgrandin 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-26180-4717-DUfUZ87Adj@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: linkBe 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).