From: DJ Delorie <dj@redhat.com>
To: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
Cc: eliz@gnu.org, tromey@redhat.com, gdb-patches@sourceware.org
Subject: Re: [RFC] Fix problems related to Mingw/DJGPP file names containing colons
Date: Sat, 13 Aug 2011 20:51:00 -0000 [thread overview]
Message-ID: <201108132050.p7DKoxCp014076@greed.delorie.com> (raw)
In-Reply-To: <005101cc59f9$7e87a790$7b96f6b0$@muller@ics-cnrs.unistra.fr> (pierre.muller@ics-cnrs.unistra.fr)
> But there might be some 'exotic' file systems that allow
> both double-quotes and colons as valid characters in their
> filenames.
Any unix-like OS supports that:
$ touch 'foo"bar:grill'
-rw-r--r-- 1 dj games 0 Aug 13 16:46 foo"bar:grill
The only two characters you *can't* put in a file name or subdirectory
name are the NUL character and possibly '/' (I've seen ways to make
filenames with / in them). Every other character is 100% legal.
> I am wondering how spaces within filenames are handled
> inside GDB on mingw32...
> I just tested... No very well :(
Any unix-like OS also supports spaces in filenames!
$ touch 'foo bar'
-rw-r--r-- 1 dj games 0 Aug 13 16:47 foo bar
These are not new problems, nor are they dos/windows specific.
next prev parent reply other threads:[~2011-08-13 20:51 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 [this message]
2011-08-13 21:26 ` Mark Kettenis
2011-08-15 19:29 ` Tom Tromey
[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=201108132050.p7DKoxCp014076@greed.delorie.com \
--to=dj@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=pierre.muller@ics-cnrs.unistra.fr \
--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