From: "Maciej W. Rozycki" <macro@mips.com>
To: gdb-patches@sourceware.org
Cc: Chris Dearman <chris@mips.com>,
"Maciej W. Rozycki" <macro@linux-mips.org>
Subject: Remove a trailing space resulting from file name completion
Date: Thu, 10 May 2007 13:07:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.61.0705101326150.29962@perivale.mips.com> (raw)
Hi,
There is an annoying problem with file name completion when it comes to
internal variables. When a command like:
(gdb) set logging file log.txt<Tab>
is issued (<Tab> here denoting a stroke of the named key) and "log.txt"
already exists, then a space is appended (of course it may not make too
much sense to use completion at the very end of the "log.txt" string, but
it may earlier). After issuing the command as is, this space is included
in the variable holding the log file name and consequently, if the log
file is subsequently written, it is created with the trailing space, i.e.
as "log.txt ". The space has to be explicitly deleted if this is not
desired.
As a file with a trailing space is indeed not desired in about any case,
I propose the following change to be included.
2007-05-10 Chris Dearman <chris@mips.com>
Maciej W. Rozycki <macro@mips.com>
* cli/cli-setshow.c (do_setshow_command): Remove trailing
whitespace when setting a var_filename.
This change was tested natively for mips-unknown-linux-gnu and
remotely for mipsisa32-sde-elf, using mips-sim-sde32/-EB and
mips-sim-sde32/-EL as the targets, with no regressions.
OK to apply?
Maciej
12227.diff
Index: gdb/src/gdb/cli/cli-setshow.c
===================================================================
--- gdb.orig/src/gdb/cli/cli-setshow.c 2007-02-13 13:51:14.000000000 +0000
+++ gdb/src/gdb/cli/cli-setshow.c 2007-02-13 13:51:29.000000000 +0000
@@ -192,6 +192,13 @@
error_no_arg (_("filename to set it to."));
if (*(char **) c->var != NULL)
xfree (*(char **) c->var);
+ {
+ /* Clear trailing whitespace of filename. */
+ char *ptr = arg + strlen (arg) - 1;
+ while (ptr >= arg && (*ptr == ' ' || *ptr == '\t'))
+ ptr--;
+ *(ptr + 1) = '\0';
+ }
*(char **) c->var = tilde_expand (arg);
break;
case var_boolean:
next reply other threads:[~2007-05-10 13:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-10 13:07 Maciej W. Rozycki [this message]
2007-05-10 13:17 ` Daniel Jacobowitz
2007-05-11 8:12 ` Eli Zaretskii
2007-05-14 12:40 ` Maciej W. Rozycki
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=Pine.LNX.4.61.0705101326150.29962@perivale.mips.com \
--to=macro@mips.com \
--cc=chris@mips.com \
--cc=gdb-patches@sourceware.org \
--cc=macro@linux-mips.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