Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Pierre Muller" <muller@ics.u-strasbg.fr>
To: <gdb-patches@sourceware.org>
Subject: [RFA] use filename_completer for add_setshow_optional_filename_cmd
Date: Tue, 01 Jul 2008 21:38:00 -0000	[thread overview]
Message-ID: <000001c8dbc2$b1d7afe0$15870fa0$@u-strasbg.fr> (raw)


  I discovered that
set debug-file-directory does not use filename_completer.

  This is because add_setshow_optional_filename_cmd
does not set the set completer to filename completer,
contrary to add_setshow_filename_cmd.
  
  Is there any reason for this?
Or is it just a bug?

  The following small patch fixes this
by setting the set part completer to filename_completer
for  add_setshow_optional_filename_cmd
exactly as is done in add_setshow_filename_cmd.
  
  There are currently only three adffected commands:

"set debug-file-directory"
"set args"
"set solib-search-path"

  Only the second one might be questionable,
but I also find that it is reasonable to have filename
completion for "set args" as this is now done on
most shells.

  I ran the testsuite with that patch on cygwin,
and the only difference I got was in gdb.trace/packetlen.exp
but I can't see any relation with the patch, and this
problem is probably due to some instabilities on
the cygwin testsuite. 

Is this OK to commit?


Pierre Muller

Pascal language support maintainer for GDB

ChangeLog entry:

2008-07-01  Pierre Muller  <muller@ics.u-strasbg.fr>

	cli/cli-decode.c (add_setshow_optional_filename_cmd): Set
	completer for set to filename_completer.


Index: gdb/cli/cli-decode.c
===================================================================
RCS file: /cvs/src/src/gdb/cli/cli-decode.c,v
retrieving revision 1.65
diff -u -p -r1.65 cli-decode.c
--- gdb/cli/cli-decode.c        3 May 2008 23:24:17 -0000       1.65
+++ gdb/cli/cli-decode.c        1 Jul 2008 15:27:41 -0000
@@ -539,11 +539,16 @@ add_setshow_optional_filename_cmd (char
                                   struct cmd_list_element **set_list,
                                   struct cmd_list_element **show_list)
 {
+  struct cmd_list_element *set_result;
+
   add_setshow_cmd_full (name, class, var_optional_filename, var,
                        set_doc, show_doc, help_doc,
                        set_func, show_func,
                        set_list, show_list,
-                       NULL, NULL);
+                       &set_result, NULL);
+
+  set_cmd_completer (set_result, filename_completer);
+
 }

 /* Add element named NAME to both the set and show command LISTs (the



             reply	other threads:[~2008-07-01 21:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-01 21:38 Pierre Muller [this message]
2008-07-01 22:03 ` Pedro Alves
2008-07-04  6:17 ` Joel Brobecker
2008-07-04 14:56   ` Pierre Muller
2008-07-04 18:01     ` Eli Zaretskii
2008-07-04 22:56   ` Pierre Muller
2008-07-04 10:45 ` Eli Zaretskii

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='000001c8dbc2$b1d7afe0$15870fa0$@u-strasbg.fr' \
    --to=muller@ics.u-strasbg.fr \
    --cc=gdb-patches@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