Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Keith Seitz <keiths@redhat.com>
To: tromey@redhat.com
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] More linespec quoting "fixes"
Date: Wed, 03 Mar 2010 18:00:00 -0000	[thread overview]
Message-ID: <4B8EA3B5.6080504@redhat.com> (raw)
In-Reply-To: <m3hbp3mwh2.fsf@fleche.redhat.com>

On 02/26/2010 03:02 PM, Tom Tromey wrote:
> My real question is whether we want to do this.  We've talked a little
> bit about rewriting linespec to be less horrible... will supporting more
> syntax make this too hard?  I'm open to breaking compatibility a bit --
> but I think there is a limit to what we can do there, based on what is
> documented.

I don't really have an answer for this. This is one of those areas where 
the documentation doesn't explain everything in detail.

In an ideal world, I would get rid of quoting entirely (or at least 
try), but that's a debate for another time. With this patch, I was 
simply attempting to address the issue that single quotes are not 
handled in the filename/"first half" of the linespec, and I could find 
no reason why they should not. [And if we keep quoting in linespecs, I 
cannot think why we would not allow any part of them to be quoted -- 
consider filenames with spaces (yich).]

In the end, I was attempting to rectify this behavior with CVS HEAD:

(gdb) list 'foo.c':1
No source file named foo.c'.

Keith


  reply	other threads:[~2010-03-03 18:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-24 22:10 Keith Seitz
2010-02-24 22:49 ` Keith Seitz
2010-02-26 23:02 ` Tom Tromey
2010-03-03 18:00   ` Keith Seitz [this message]
2010-03-04 13:51     ` Daniel Jacobowitz
2010-03-04 18:39       ` Keith Seitz

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=4B8EA3B5.6080504@redhat.com \
    --to=keiths@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tromey@redhat.com \
    /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