Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: pierre.muller@ics-cnrs.unistra.fr, eliz@gnu.org,
	       gdb-patches@sourceware.org
Subject: Re: [RFC] Fix problems related to Mingw/DJGPP file names containing colons
Date: Mon, 15 Aug 2011 19:29:00 -0000	[thread overview]
Message-ID: <m339h2eaod.fsf@fleche.redhat.com> (raw)
In-Reply-To: <201108132125.p7DLPhb6010148@glazunov.sibelius.xs4all.nl> (Mark	Kettenis's message of "Sat, 13 Aug 2011 23:25:43 +0200 (CEST)")

>>>>> "Mark" == Mark Kettenis <mark.kettenis@xs4all.nl> writes:

Mark> Perhaps that's the solution here?  If you use "quotation" as well as
Mark> "escaping" you should be able to express anything you want on a
Mark> command line.

One funny thing about linespecs is that the quoting syntax isn't
actually documented -- at least, I couldn't find it in the manual.

I tend to think this gives us some freedom to change it a little, on the
theory that probably not many people are already using both quotes and
backslashes.

That theory may run aground on the unfortunate fact that MI's
-break-insert exposes linespecs to the MI clients.  I wonder what they
do for Windows-style paths right now.


I have been contemplating changing linespec to pre-tokenize.  Right now
if you read linespec.c, code to pull out the next relevant token is
spread out all over the file.  I think it would simplify and strengthen
the implementation if this were done in a single pass up-front.

Tom


  reply	other threads:[~2011-08-15 19:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <004901cc5907$85006320$8f012960$%muller@ics-cnrs.unistra.fr>
2011-08-12 17:17 ` Eli Zaretskii
2011-08-12 17:25   ` Tom Tromey
2011-08-12 17:47     ` Eli Zaretskii
2011-08-13 10:11       ` Pierre Muller
     [not found]       ` <003c01cc59a1$49cc1520$dd643f60$%muller@ics-cnrs.unistra.fr>
2011-08-13 10:50         ` Eli Zaretskii
2011-08-13 20:42           ` Pierre Muller
2011-08-13 20:51             ` DJ Delorie
2011-08-13 21:26             ` Mark Kettenis
2011-08-15 19:29               ` Tom Tromey [this message]
     [not found]           ` <28604.9419818029$1313268187@news.gmane.org>
2011-08-15 19:21             ` Tom Tromey
     [not found] <7973.24406817115$1313164244@news.gmane.org>
2011-08-13  1:20 ` asmwarrior
2011-08-12 15:50 Pierre Muller
2011-08-12 17:00 ` 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=m339h2eaod.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=mark.kettenis@xs4all.nl \
    --cc=pierre.muller@ics-cnrs.unistra.fr \
    /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