in reply to Re: open and read text file
in thread open and read text file

The OP’s experience is quite surprising to me, because, when out of curiosity I tried the same thing on my friendly neighborhood Linux box, I got this:

/user/bin/perl: bad interpreter: No such file or directory

Replies are listed 'Best First'.
Re^3: open and read text file
by stevieb (Canon) on Jul 22, 2017 at 01:08 UTC

    As do I actually, but it's the only obvious thing that is wrong in the post.

    Perhaps it's because it's a Mac, or some weird way OP is calling the script.

    I know nothing of Mac computers, but I do know they don't have /user/bin. Without further clarification, it's a guessing game (unless a mac person can test).

      "... (unless a mac person can test)."

      I don't think I'd really like "mac person" as an epithet; however, I do have one, and I did test.

      This sub-thread progressed somewhat since I started to prepare my post. I didn't see the replies until after I'd posted. I wholeheartedly agree with your:

      "A lot of squiggly lines and plain text butchery so it's hard to read."

      There also appears to be factual errors in what he wrote, but® «... maybe“(!?)” ‘am’ just™» gettinglost® [in the] pUnCtUaTiOn™.

      — Ken

        "...I don't think I'd really like "mac person" as an epithet...

        You are right. Some jesuit thoughts: A mac is a pimp. And hence a "mac person" seems to be a very strange construct. But perhaps the certain monk meant "Apple Fan Boy" which some people consider to be an insult as well. Not to talk about "Macpherson" (assuming it was bad typo) which is a "Scottish sex god, with balls of steel and nothing to lose" according to urban dict.

        Best regards, Karl

        «The Crux of the Biscuit is the Apostrophe»

        perl -MCrypt::CBC -E 'say Crypt::CBC->new(-key=>'kgb',-cipher=>"Blowfish")->decrypt_hex($ENV{KARL});'Help

    A reply falls below the community's threshold of quality. You may see it by logging in.