Beefy Boxes and Bandwidth Generously Provided by pair Networks
Think about Loose Coupling
 
PerlMonks  

Re^2: Mac Space in Path

by bettis (Initiate)
on May 23, 2013 at 03:27 UTC ( #1034853=note: print w/ replies, xml ) Need Help??


in reply to Re: Mac Space in Path
in thread Mac Space in Path

Thank you so much for your responses. I implemented and tested different permutations of the suggestions listed here. I also added a line to print the path $metadata_file, so I could keep track of what the script was opening if it was able to open the file and not die:

print "\n\nPlease drop the metadata file [vendor instructions/isbn13.x +ml]:\n\n\t\t>>>"; chomp (my $metadata_file = <>); print $metadata_file; #$metadata_file =~ s/\s$//; open (FILE, "<", "$metadata_file") or die "Could not open '$metadata_f +ile': $!\n"; $metadata = join '', <FILE>;

First, I commented out the line that deletes the trailing space from the user input. I noticed that the chomp() was not working the same after OSX 10.4, so I had to implement the line (We're a small Mac typehouse and all of our machines have slightly different implementations of perl. The trailing space works on some machines and not on others, but no trailing space works on all.):

$metadata_file =~ s/\s$//;

When I comment it out, you'll see that the trailing space is still there and the space between "vendor" and "instructions" has been escaped:

Please drop the metadata file [vendor instructions/isbn13.xml]: >>>/Users/jefe/Desktop/vendor\ instructions/9781118172773.xml Could not open '/Users/jefe/Desktop/vendor\ instructions/9781118172773 +.xml ': No such file or directory

The script opens the file and reads it in perfectly if I simply delete the space in the path:

Please drop the metadata file [vendor instructions/isbn13.xml]: >>>/Users/jefe/Desktop/vendorinstructions/9781118172773.xml /Users/jefe/Desktop/vendorinstructions/9781118172773.xml

I also tried not using quotes around $metadata_file in the open command and it successfully commented out the space:

Please drop the metadata file [vendor instructions/isbn13.xml]: >>>/Users/jefe/Desktop/vendor\ instructions/9781118172773.xml Could not open '/Users/jefe/Desktop/vendor\ instructions/9781118172773 +.xml': No such file or directory

To answer your question, fishmonger, the metadata_file is simply being inserted at the top of every document the script produces, so I open it, join it, format it and insert it when I need to in the script.

This particular piece of code is my test to get it to work, then I can rewrite the other parts of the script that read and write files with space bands. Previously, I simply admonished all our comps to not use space bands in their paths. Unfortunately, the client's CMS inserts space bands at every level, so I need to figure this out. It seems so simple, but it's not working.

Again, thank you for your help.


Comment on Re^2: Mac Space in Path
Select or Download Code
Re^3: Mac Space in Path
by bettis (Initiate) on May 23, 2013 at 04:40 UTC

    Solution:

    $metadata_file =~ s/\\//;

    Apparently, Mac OSX Perl doesn't want the space band escaped. It likes a bare space in the path.

    Again, thank you for your help.

      No Perl wants the space band escaped, and I'm not sure where you got the idea that there's escaping that needs to be done.

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://1034853]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others browsing the Monastery: (7)
As of 2014-12-27 22:22 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    Is guessing a good strategy for surviving in the IT business?





    Results (177 votes), past polls