Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Andrew STUBBS <andrew.stubbs@st.com>,
		GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Allow spaces in pathnames to directory command
Date: Tue, 21 Feb 2006 18:55:00 -0000	[thread overview]
Message-ID: <20060221182750.GA26373@nevyn.them.org> (raw)
In-Reply-To: <20060220191937.GA23330@nevyn.them.org>

On Mon, Feb 20, 2006 at 02:19:37PM -0500, Daniel Jacobowitz wrote:
> On Mon, Feb 20, 2006 at 06:06:51PM +0000, Andrew STUBBS wrote:
> > Daniel Jacobowitz wrote:
> > >On Tue, Dec 06, 2005 at 03:17:07PM +0000, Andrew STUBBS wrote:
> > >>Andrew Stubbs wrote:
> > >>>The directory command and the -d switch do not support pathnames that 
> > >>>contain spaces.
> > >>It looks like my patch ought to fix PR gdb/1832, PR gdb/956, and perhaps 
> > >>PR gdb/535.
> > >
> > >Does Andrew's comment about filename_completer in gdb/535 still apply?
> > 
> > Yeah, I suppose it does. Certainly the auto-completer completes names 
> > with spaces in (provided that the spaces are not in the part already 
> > typed), but does not add any form of quoting.
> > 
> > It doesn't quote quotes or spaces. Nor does it complete filenames that 
> > have quoted elements already in them.
> > 
> > This doesn't change the correctness of the patches in question though. 
> > The bug report gdb/535 complains about the behaviour of generic_load(), 
> > not the auto-completer - that's a separate issue raised by Andrew Cagney.
> > 
> > I do agree that the completer ought to be fixed at some point.
> 
> Except that previously, the filename completer produced things that
> were valid for this command, and now it doesn't.  Sounds pretty
> inconvenient to me.
> 
> I bumped up against this separately this morning.  I may see about
> unifying the completion to handle quoting.

Meanwhile, I think that this is a sensible change, so go ahead and
commit it.

The story for quoting arguments passed to MI is very, very confused
right now.  I've just discovered that Eclipse doesn't quote at all,
and doesn't escape backslashes; I'm going to have to dig more, but
I'm going to try to give us a unified picture on this today.

I think that the CLI commands should expect buildargv-style quoting,
and the MI commands should take a more C-style quoting (since that's
how they are documented), but right now I fear they take both.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2006-02-21 18:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-06 21:39 Andrew STUBBS
2005-12-06 22:08 ` Andrew STUBBS
2006-02-20 17:19   ` Daniel Jacobowitz
2006-02-20 18:09     ` Andrew STUBBS
2006-02-20 19:19       ` Daniel Jacobowitz
2006-02-21 18:55         ` Daniel Jacobowitz [this message]
2006-02-21 20:15           ` Andrew STUBBS

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=20060221182750.GA26373@nevyn.them.org \
    --to=drow@false.org \
    --cc=andrew.stubbs@st.com \
    --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