• Kramer (7/7) Jan 28 2005 I'm running WinXP and DMD 0.111. I use spaces in my directories (i.e. "...
• Jarrett Billingsley (1/1) Jan 28 2005 Not to sound patronizing, but do you have double quotes around the pathn...
• Kramer (10/11) Jan 29 2005 Not at all, valid question. :) Yes. I've tried every combination I can...
• =?UTF-8?B?VGhvbWFzIEvDvGhuZQ==?= (27/27) Jan 29 2005 -----BEGIN PGP SIGNED MESSAGE-----
• Nick Sabalausky (4/24) Feb 01 2005 Just another shot in the dark: Did you try both variations "-IC:\path wi...

Kramer <Kramer_member pathlink.com> writes:

I'm running WinXP and DMD 0.111.  I use spaces in my directories (i.e. "c:\my
documents\my code\d") and have been noticing that when I try to use these paths
for the import flag, the compiler doesn't appear to like them; I get an error
saying the compiler can't read whatever file it's looking for.

It does however seem to work for source files...

Has anyone else run into this?

-Kramer

"Jarrett Billingsley" <kb3ctd2 yahoo.com> writes:

Not to sound patronizing, but do you have double quotes around the pathname? 

Kramer <Kramer_member pathlink.com> writes:

In article <ctesvp$16d0$1 digitaldaemon.com>, Jarrett Billingsley says...
Not to sound patronizing, but do you have double quotes around the pathname? 


Not at all, valid question. :)  Yes.  I've tried every combination I can think
of: double quotes, single quotes, storing the directories in environment
variables and quoting them... no luck.  I really hope I'm just missing something
here, because I would think it'd be important for the compiler to accept
directories with spaces in them.

If you or someone else has this working, /please/ let me know how you're doing
it and on what platform.  This isn't a show stopper to be sure, but it'd be
nice.

-Kramer

=?UTF-8?B?VGhvbWFzIEvDvGhuZQ==?= writes:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Kramer wrote:

| In article <ctesvp$16d0$1 digitaldaemon.com>, Jarrett Billingsley
| says...
|
|> Not to sound patronizing, but do you have double quotes around the
|> pathname?

| Not at all, valid question. :)  Yes.  I've tried every combination I
| can think of: double quotes, single quotes, storing the directories
| in environment variables and quoting them... no luck.  I really hope
| I'm just missing something here, because I would think it'd be
| important for the compiler to accept directories with spaces in them.
|
|
| If you or someone else has this working, /please/ let me know how
| you're doing it and on what platform.  This isn't a show stopper to
| be sure, but it'd be nice.

If you are on MSWindows you can use the "short DOS" name.
Try: dir /x

Thomas


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (MingW32)

iD8DBQFB+/nE3w+/yD4P9tIRAuz2AJ95JIcsW2Z1sxZjL0LujI2oZALW/wCdEi1T
ZrRseGFXN7V1BmG1JpjMxEg=
=QoaR
-----END PGP SIGNATURE-----

"Nick Sabalausky" <z a.a> writes:

Just another shot in the dark: Did you try both variations "-IC:\path with 
space" and  -I"C:\path with space"?

"Kramer" <Kramer_member pathlink.com> wrote in message 
news:ctgs9a$c8c$1 digitaldaemon.com...
 In article <ctesvp$16d0$1 digitaldaemon.com>, Jarrett Billingsley says...
Not to sound patronizing, but do you have double quotes around the 
pathname?


 Not at all, valid question. :)  Yes.  I've tried every combination I can 
 think
 of: double quotes, single quotes, storing the directories in environment
 variables and quoting them... no luck.  I really hope I'm just missing 
 something
 here, because I would think it'd be important for the compiler to accept
 directories with spaces in them.

 If you or someone else has this working, /please/ let me know how you're 
 doing
 it and on what platform.  This isn't a show stopper to be sure, but it'd 
 be
 nice.

 -Kramer