On Sun, 11 Jan 2004, Oliver Schnarchendorf wrote:
Okay... I think the problem here is that BBEdit doesn't use your
Environmental variables.
You can print them with the following one liner
perl -e 'use Data::Dumper; print Dumper (\%ENV);'
Do yourself a favor and put the above perl
On Mon, 12 Jan 2004 09:38:09 -0500 (EST), Chris Devers wrote:
On Sun, 11 Jan 2004, Oliver Schnarchendorf wrote:
perl -e 'use Data::Dumper; print Dumper (\%ENV);'
Maybe I'm being naive, but in what way is this better than just using
plain old /usr/bin/env?
It was a perl question... not a
I'm sorry for all the confusion. Let me try one last time.
I have a perl file with a single chunk of data produced by typing
option-8 after __DATA__. So the end of the file looks like this:
__DATA__
option-8
When I look at this file with HexEdit, option-8 appears as A5.
My actual
On Sun, 11 Jan 2004 21:02:14 -0500, Vic Norton wrote:
My actual script looks for the pattern m/\xa5/ in the data. If I
make the script executable and run it from the terminal, it finds
A5. If I execute the script from BBEdit, either directly or Run in
Terminal, no A5 is found.
Okay... I
At 9:02 PM -0500 11/1/04, Vic Norton wrote:
When I write another script to print out the bytes under __DATA__, I see
A5 if I execute the script from Terminal, and I see E2 80 A2 if
I run the script fom BBEdit, either directly or Run in Terminal.
But BBEdit can see A5. It just can't see it as
On Jan 11, 2004, at 9:55 PM, Peter N Lewis wrote:
When you 'run the script from BBEdit, either directly or Run in
Terminal.', what actually happens is BBEdit saves the file in a
temporary file and then executes it.
Not always. If the editing window is unsaved, or has non-native line
endings,
