public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "jan.kratochvil at redhat dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug guile/18382] New: "guile" command still completes --without-guile Date: Wed, 06 May 2015 08:04:00 -0000 [thread overview] Message-ID: <bug-18382-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=18382 Bug ID: 18382 Summary: "guile" command still completes --without-guile Product: gdb Version: 7.9 Status: NEW Severity: normal Priority: P2 Component: guile Assignee: unassigned at sourceware dot org Reporter: jan.kratochvil at redhat dot com Target Milestone: --- Host: xdje42 at gmail dot com Tom Tromey 2015-05-04: The "guile" and "guile-repl" commands are disabled in the Fedora gdb, but they still show up in the CLI. This messes up completion for me sometimes, as I have a "gui" command I use. I think that since these commands can't work in Fedora gdb, they should not appear in the CLI at all. I hacked around this using maint deprecate guile maint deprecate guile-repl ... but unfortunately these don't work: maint deprecate set guile maint deprecate show guile (Which is maybe another bug of its own) https://bugzilla.redhat.com/show_bug.cgi?id=1218357 -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2015-05-06 8:04 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-05-06 8:04 jan.kratochvil at redhat dot com [this message] 2015-05-06 8:05 ` [Bug guile/18382] " jan.kratochvil at redhat dot com 2015-05-08 5:38 ` xdje42 at gmail dot com 2022-04-15 13:39 ` tromey at sourceware dot org
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-18382-4717@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).