Re: Capture group question

[Fletcher Sandbeck]

There's a good discussion at the following URL but it occurs because the 
regular expression is evaluated as a state machine. Here the capturing group 
itself is repeated by the {2}. The first match is discarded when it sees the 
second match and that's what you see in the results.

https://www.regular-expressions.info/captureall.html 


[fletcher]


> On Mar 6, 2020, at 7:25 PM, Howard  wrote:
> 
> When using the Pattern Playground, in the search pattern's capture group #1 
> (see below), why is `847-` appearing rather than `717-`?
> 
> Search pattern: (\d{3}[.-]?){2}
> 
> Source text: 717-847-8015
> 
> Capture Groups:
> #0: 717-847-
> #1: 847-
> 
> -- 
> This is the BBEdit Talk public discussion group. If you have a feature 
> request or need technical support, please email "supp...@barebones.com" 
> rather than posting here. Follow @bbedit on Twitter: 
> >
> --- 
> You received this message because you are subscribed to the Google Groups 
> "BBEdit Talk" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to bbedit+unsubscr...@googlegroups.com 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/bbedit/32702e50-f03b-4a76-94a1-6974886c4f0b%40googlegroups.com
>  
> .

-- 
This is the BBEdit Talk public discussion group. If you have a feature request 
or need technical support, please email "supp...@barebones.com" rather than 
posting here. Follow @bbedit on Twitter: 
--- 
You received this message because you are subscribed to the Google Groups 
"BBEdit Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to bbedit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/bbedit/DC6CF50B-B3E8-452D-BC30-2B0033B0C79B%40cumuli.com.

Capture group question

[Howard]

When using the Pattern Playground, in the search pattern's capture group #1 
(see below), why is `847-` appearing rather than `717-`?

Search pattern: (\d{3}[.-]?){2}

Source text: 717-847-8015

Capture Groups:
#0: 717-847-
#1: 847-

-- 
This is the BBEdit Talk public discussion group. If you have a feature request 
or need technical support, please email "supp...@barebones.com" rather than 
posting here. Follow @bbedit on Twitter: 
--- 
You received this message because you are subscribed to the Google Groups 
"BBEdit Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to bbedit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/bbedit/32702e50-f03b-4a76-94a1-6974886c4f0b%40googlegroups.com.

Re: .htaccess extension mapping

[MediaMouth]

Wow, that's quite a quirk of a solution.

For whatever reason, the issue seems either to have resolved itself with the 
latest upgrade or... who knows what.
As of right now .htaccess files are being recognized per the preferences I set 
up.  ¯\_(ツ)_/¯

The interesting thing about your observation is that from what I can tell 
there's no metadata contained by the file created by text edit that BBEdit 
wouldn't be getting rid of when it's opened and emptied -- it's a 0 bite file.  
But maybe the OS 'knows' something about the file (i.e. external metadata).

Thanks for the insight!

> On Mar 6, 2020, at 12:54 PM, GP  wrote:
> 
> I tried this with BBEdit version 12.6.7 (I haven't upgraded yet) and the 
> custom filename extension mapping worked with one big caveat.  The file must 
> not have been saved by BBEdit before the custom filename extension mapping 
> preference setting was made. Whatever file typing metadata BBEdit saved 
> during the previous file save will override any newly added custom filename 
> extension mapping preference. (If you have previous BBEdit saved htaccess 
> extension files, I think you'll have to use the Language popup in an open 
> file's window to change the file language type metadata on the next file save 
> in order for the Apache Configuration File codeless language module to be 
> used the next time that specific file is opened.)
> 
> As a test, I created a test file using TextEdit and saved it. Changed the 
> default extension from rtf to htaccess and then opened it in BBEdit through a 
> Finder open using BBEdit as the opening app and through BBEdit's File Open 
> menu.  In both cases BBEdit used the htaccess file extension to mapping the 
> file Apache Configuration File and use the associated codeless language 
> module for syntax colorizing, etc..

-- 
This is the BBEdit Talk public discussion group. If you have a feature request 
or need technical support, please email "supp...@barebones.com" rather than 
posting here. Follow @bbedit on Twitter: 
--- 
You received this message because you are subscribed to the Google Groups 
"BBEdit Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to bbedit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/bbedit/AE06D9D1-0445-4FA8-8EAC-3BBCFB0A7F3F%40gmail.com.

Re: .htaccess extension mapping

[GP]

I tried this with BBEdit version 12.6.7 (I haven't upgraded yet) and the 
custom filename extension mapping worked with one big caveat.  The file 
must not have been saved by BBEdit before the custom filename extension 
mapping preference setting was made. Whatever file typing metadata BBEdit 
saved during the previous file save will override any newly added custom 
filename extension mapping preference. (If you have previous BBEdit 
saved htaccess extension files, I think you'll have to use the Language 
popup in an open file's window to change the file language type metadata on 
the next file save in order for the Apache Configuration File codeless 
language module to be used the next time that specific file is opened.)

As a test, I created a test file using TextEdit and saved it. Changed the 
default extension from rtf to htaccess and then opened it in BBEdit through 
a Finder open using BBEdit as the opening app and through BBEdit's File 
Open menu.  In both cases BBEdit used the htaccess file extension to 
mapping the file Apache Configuration File and use the associated codeless 
language module for syntax colorizing, etc..

On Thursday, March 5, 2020 at 1:55:26 PM UTC-8, Harvey Pikelberger wrote:
>
> I was hoping to set BBEdit to open .htaccess files under the custom 
> filename extension mapping for Apache Configuration File ( downloaded from 
> https://daringfireball.net/projects/apacheconfig/ )
>
> The language module works great, but I haven't been able to get BBEdit to 
> recognize the suffix "htacces" at *Preferences > Languages > Custom 
> filename extensions mapping*
>
>
>

-- 
This is the BBEdit Talk public discussion group. If you have a feature request 
or need technical support, please email "supp...@barebones.com" rather than 
posting here. Follow @bbedit on Twitter: 
--- 
You received this message because you are subscribed to the Google Groups 
"BBEdit Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to bbedit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/bbedit/55d0ef4d-45fb-46ae-ad57-e3078d5fc38b%40googlegroups.com.

Re: Shebang Line Woes

[Paul Gobble]

Sam, I'll buy you a beer next time I see ya. You figured it out.  I resaved 
as UTF-8 no BOM and it works!  Thank you.

On Friday, March 6, 2020 at 11:50:23 AM UTC-5, Sam Hathaway wrote:
>
> Yup, you’ve got a byte-order marker there. Try re-saving the file as 
> “Unicode (UTF-8)” rather than “Unicode (UTF-8, with BOM)”. And if BBEdit is 
> saving UTF-8 files with a BOM by default, you’ll probably want to change 
> the “Default text encoding for new documents” in Preferences > Text 
> Encodings. (There’s no good reason to have a BOM for UTF-8.)
>
> Hope this helps!
> -sam
>
> On 6 Mar 2020, at 11:46, Paul Gobble wrote:
>
> Sam,
>
> You might have hit something.  Below is the hexdump from the macOS system 
> (that doesn’t run)
>
> paul@Emonda Python-RFP-PDF-Scraper % hexdump -C ./python_test-01.py 
>   ef bb bf 23 21 2f 75 73  72 2f 62 69 6e 2f 70 79 
>  |...#!/usr/bin/py|
> 0010  74 68 6f 6e 33 0a 70 72  69 6e 74 28 27 48 65 6c 
>  |thon3.print('Hel|
> 0020  6c 6f 20 57 6f 72 6c 64  27 29 0a |lo World').|
> 002b
>
>
> And here is the hexdump for the Raspberry Pi (that does run)
>
>   23 21 2f 75 73 72 2f 62  69 6e 2f 65 6e 76 20 70 
>  |#!/usr/bin/env p|
> 0010  79 74 68 6f 6e 33 0a 70  72 69 6e 74 28 27 48 65 
>  |ython3.print('He|
> 0020  6c 6c 6f 20 57 6f 72 6c  64 27 29 0a  |llo World').|
> 002c 
>
>
> I notice the additional “...” as the start of the Shebang on the MacOS 
> hexdump. 
>
> What do you see, and what could that mean?
>
> Thanks!
>
> On Friday, March 6, 2020 at 11:30:30 AM UTC-5, Sam Hathaway wrote:
>>
>> This is very curious. I don’t recognize the formatting in the error 
>> message you’re getting when you run it directly. If the shell couldn’t find 
>> the interpreter in the shebang line, it should say something like “bad 
>> interpreter” and exit immediately. Instead, whatever is executing this file 
>> goes on to the second line of the script and chokes on the print() 
>> statement. What shell do you use? (You can use echo $SHELL to find out.)
>>
>> I wonder if there’s some kind of encoding problem or stray bytes at the 
>> beginning of the file. Can you send me the output of this command?
>>
>> hexdump -C /Users/.../Scripts/python_test-01.py
>>
>> Thanks!
>> -sam
>>
>> On 6 Mar 2020, at 11:12, Paul Gobble wrote:
>>
>> Sam,
>>
>> Thank you for your input. Yes, my Mac is running MacOS 10.15.3 Catalina. 
>> I tried the tests you suggested, see below.
>>
>> #!/usr/bin/python3
>> paul@Emonda Python-RFP-PDF-Scraper % ./python_test-01.py 
>> ./python_test-01.py: line 1: #!/usr/bin/python3: No such file or 
>> directory
>> ./python_test-01.py: line 2: syntax error near unexpected token `'Hello 
>> World''
>> ./python_test-01.py: line 2: `print('Hello World')'
>> paul@Emonda Python-RFP-PDF-Scraper % ls -le@ ./python_test-01.py 
>> -rwxr-xr-x@ 1 paul  staff  43 Mar  6 11:01 ./python_test-01.py
>> com.apple.lastuseddate#PS   16 
>> com.apple.macl  72 
>> paul@Emonda Python-RFP-PDF-Scraper % /usr/bin/python3 ./python_test-01.py 
>> Hello World
>> paul@Emonda Python-RFP-PDF-Scraper %
>>
>> So, no, nothing about quarantine was reported.  And yes, if I pass it to 
>> /usr/bin/python3 on the command line (the exact same path as in the 
>> Shebang) it runs fine. 
>>
>> On Friday, March 6, 2020 at 9:58:23 AM UTC-5, Sam Hathaway wrote:
>>>
>>> Paul,
>>>
>>> I take it you’re on macOS 10.15 Catalina, since /usr/bin/python3 exists.
>>>
>>> What do you get if you run this?
>>>
>>> ls -le@ /Users/.../Scripts/python_test-01.py
>>>
>>> My suspicion is that macOS might have quarantined your script. (I ran 
>>> into this once or twice after migrating my data to a fresh 10.15 install 
>>> but I don’t recall the exact error message.)
>>>
>>> If you see com.apple.quarantine in that output, you can run this to 
>>> remove the quarantine flag:
>>>
>>> xattr -d com.apple.quarantine /Users/.../Scripts/python_test-01.py
>>>
>>> If that isn’t it, I’d be curious to see if you can run the script by 
>>> passing it to the interpreter like this:
>>>
>>> /usr/bin/python3 /Users/.../Scripts/python_test-01.py
>>>
>>> Hope this helps.
>>> -sam
>>>
>>> On 4 Mar 2020, at 23:25, Paul Gobble wrote:
>>>
>>> I'm using BBedit 13.0.5 on Mac Os 10.15.3 as my editor while I try to 
>>> learn a bit of Python3.  
>>>
>>> #!/usr/bin/env python3
>>> print('Hello World')
>>>
>>> Baby steps.
>>>
>>> I try to execute this from the Run menu item in the #! menu and get
>>>
>>> /Users/.../Scripts/python_test-01.py: line 1: #!/usr/bin/env: No such 
>>> file or directory
>>>
>>> Then I try to use the direct path in the shebang line
>>>
>>> #!/usr/bin/python3
>>> print('Hello World')
>>>
>>> and get a very similar response
>>>
>>> /Users.../Scripts/python_test-01.py: line 1: #!/usr/bin/python3: No 
>>> such file or directory
>>>
>>> So I go investigate in the Terminal app and look around.
>>>
>>> Emonda:bin paul$ pwd
>>>
>>> /usr/local/bin
>>>
>>> Emonda:bin 

[ANN] BBEdit 13.0.6 (413083) pre-release

[Patrick Woolsey]

Good afternoon folks,

We are currently working on a maintenance update to address a 
few just-reported issues.


Note that this is a _pre-release_ version. The intent is to fix 
bugs and address areas of improvement based on what our 
customers have reported. However, since the software is at this 
point not fully tested, there _may_ be bugs and regressions.


If this prospect makes you nervous, then sticking with the 
public release versions is your best course of action. Nobody 
will be offended if you choose to do so; you're under no 
obligation to install and use anything but a public release. :-)


Complete change notes to date for all the pre-release builds in 
this cycle are available here:


  

The change notes are organized into additions, changes, and 
fixes, and are annotated where appropriate with case numbers. So 
if you recognize a number corresponding to a support case that 
was opened for you, you can now verify that it's been fixed 
correctly. Please take the time to review the changes before 
using the new build -- it'll be worth your time.


One final note: If you run into a bug in a pre-release version, 
PLEASE DO NOT REPORT THE BUG TO THE LIST. This includes asking 
about whether others have seen the same problem. Instead, please 
send a bug report to  and we will deal 
with it there. This will help us keep the list discussion on 
topic and productive for all list members.


Here is the list of changes made since the previous pre-release build:



version 13.0.6 (413083) (2020-03-06)

Additions
-

o   (none in this build)

Changes
---

o   (none in this build)

Fixes
-

*   [384710] Fixed a bug in which selecting a viewable file while
browsing a Zip or `tar` archive would not display the file's
contents when running on macOS 10.15.



The package can be downloaded from here:

  


Regards,

  Patrick Woolsey
==
Bare Bones Software, Inc. 


--
This is the BBEdit Talk public discussion group. If you have a feature request or need 
technical support, please email "supp...@barebones.com" rather than posting here. 
Follow @bbedit on Twitter: 
--- 
You received this message because you are subscribed to the Google Groups "BBEdit Talk" group.

To unsubscribe from this group and stop receiving emails from it, send an email 
to bbedit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/bbedit/r480Ps-10146i-B467C976025545368BC0E1E2311E400C%40Cylinder.local.

Re: Shebang Line Woes

[Rich Siegel]

> On Mar 6, 2020, at 11:46 AM, Paul Gobble  wrote:
> 
> I notice the additional “...” as the start of the Shebang on the MacOS 
> hexdump. 
> 
> What do you see, and what could that mean?
> 

It means that you saved your file as Unicode (UTF-8, with BOM) which includes a 
byte-order mark; Unix tools don't react well to such things. Saving it as 
Unicode (UTF-8) will save the file without a BOM, and this will probably solve 
the problem.

R.

-- 
This is the BBEdit Talk public discussion group. If you have a feature request 
or need technical support, please email "supp...@barebones.com" rather than 
posting here. Follow @bbedit on Twitter: 
--- 
You received this message because you are subscribed to the Google Groups 
"BBEdit Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to bbedit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/bbedit/E8BE4609-F81E-486A-9EE0-4282CF7E26B2%40barebones.com.

Re: Shebang Line Woes

[Sam Hathaway]

Yup, you’ve got a byte-order marker there. Try re-saving the file as 
“Unicode (UTF-8)” rather than “Unicode (UTF-8, with BOM)”. And 
if BBEdit is saving UTF-8 files with a BOM by default, you’ll probably 
want to change the “Default text encoding for new documents” in 
Preferences > Text Encodings. (There’s no good reason to have a BOM 
for UTF-8.)


Hope this helps!
-sam

On 6 Mar 2020, at 11:46, Paul Gobble wrote:


Sam,

You might have hit something.  Below is the hexdump from the macOS 
system

(that doesn’t run)

paul@Emonda Python-RFP-PDF-Scraper % hexdump -C ./python_test-01.py
  ef bb bf 23 21 2f 75 73  72 2f 62 69 6e 2f 70 79
 |...#!/usr/bin/py|
0010  74 68 6f 6e 33 0a 70 72  69 6e 74 28 27 48 65 6c
 |thon3.print('Hel|
0020  6c 6f 20 57 6f 72 6c 64  27 29 0a |lo 
World').|

002b


And here is the hexdump for the Raspberry Pi (that does run)

  23 21 2f 75 73 72 2f 62  69 6e 2f 65 6e 76 20 70  
|#!/usr/bin/env

p|
0010  79 74 68 6f 6e 33 0a 70  72 69 6e 74 28 27 48 65
 |ython3.print('He|
0020  6c 6c 6f 20 57 6f 72 6c  64 27 29 0a  |llo 
World').|

002c


I notice the additional “...” as the start of the Shebang on the 
MacOS

hexdump.

What do you see, and what could that mean?

Thanks!

On Friday, March 6, 2020 at 11:30:30 AM UTC-5, Sam Hathaway wrote:


This is very curious. I don’t recognize the formatting in the error
message you’re getting when you run it directly. If the shell 
couldn’t find
the interpreter in the shebang line, it should say something like 
“bad
interpreter” and exit immediately. Instead, whatever is executing 
this file

goes on to the second line of the script and chokes on the print()
statement. What shell do you use? (You can use echo $SHELL to find 
out.)


I wonder if there’s some kind of encoding problem or stray bytes at 
the

beginning of the file. Can you send me the output of this command?

hexdump -C /Users/.../Scripts/python_test-01.py

Thanks!
-sam

On 6 Mar 2020, at 11:12, Paul Gobble wrote:

Sam,

Thank you for your input. Yes, my Mac is running MacOS 10.15.3 
Catalina. I

tried the tests you suggested, see below.

#!/usr/bin/python3
paul@Emonda Python-RFP-PDF-Scraper % ./python_test-01.py
./python_test-01.py: line 1: #!/usr/bin/python3: No such file or
directory
./python_test-01.py: line 2: syntax error near unexpected token 
`'Hello

World''
./python_test-01.py: line 2: `print('Hello World')'
paul@Emonda Python-RFP-PDF-Scraper % ls -le@ ./python_test-01.py
-rwxr-xr-x@ 1 paul  staff  43 Mar  6 11:01 ./python_test-01.py
com.apple.lastuseddate#PS   16
com.apple.macl  72
paul@Emonda Python-RFP-PDF-Scraper % /usr/bin/python3 
./python_test-01.py

Hello World
paul@Emonda Python-RFP-PDF-Scraper %

So, no, nothing about quarantine was reported.  And yes, if I pass it 
to

/usr/bin/python3 on the command line (the exact same path as in the
Shebang) it runs fine.

On Friday, March 6, 2020 at 9:58:23 AM UTC-5, Sam Hathaway wrote:


Paul,

I take it you’re on macOS 10.15 Catalina, since /usr/bin/python3 
exists.


What do you get if you run this?

ls -le@ /Users/.../Scripts/python_test-01.py

My suspicion is that macOS might have quarantined your script. (I 
ran
into this once or twice after migrating my data to a fresh 10.15 
install

but I don’t recall the exact error message.)

If you see com.apple.quarantine in that output, you can run this to
remove the quarantine flag:

xattr -d com.apple.quarantine /Users/.../Scripts/python_test-01.py

If that isn’t it, I’d be curious to see if you can run the 
script by

passing it to the interpreter like this:

/usr/bin/python3 /Users/.../Scripts/python_test-01.py

Hope this helps.
-sam

On 4 Mar 2020, at 23:25, Paul Gobble wrote:

I'm using BBedit 13.0.5 on Mac Os 10.15.3 as my editor while I try 
to

learn a bit of Python3.

#!/usr/bin/env python3
print('Hello World')

Baby steps.

I try to execute this from the Run menu item in the #! menu and get

/Users/.../Scripts/python_test-01.py: line 1: #!/usr/bin/env: No 
such

file or directory

Then I try to use the direct path in the shebang line

#!/usr/bin/python3
print('Hello World')

and get a very similar response

/Users.../Scripts/python_test-01.py: line 1: #!/usr/bin/python3: 
No

such file or directory

So I go investigate in the Terminal app and look around.

Emonda:bin paul$ pwd

/usr/local/bin

Emonda:bin paul$ whereis python3

/usr/bin/python3

Emonda:bin paul$ whereis env

/usr/bin/env

Emonda:bin paul$

Both env and python3 are right where I said they were in the shebang
line, but interpreter can't find them!

Can anyone help me out here?  What am I missing?

Thanks,
Paul

--
This is the BBEdit Talk public discussion group. If you have a 
feature
request or need technical support, please email 
"sup...@barebones.com"

rather than posting here. Follow @bbedit on Twitter: <
https://twitter.com/bbedit>
---
You received this message because you are subscribed to the Google 

Re: Shebang Line Woes

[Paul Gobble]

Sam,

You might have hit something.  Below is the hexdump from the macOS system 
(that doesn’t run)

paul@Emonda Python-RFP-PDF-Scraper % hexdump -C ./python_test-01.py 
  ef bb bf 23 21 2f 75 73  72 2f 62 69 6e 2f 70 79 
 |...#!/usr/bin/py|
0010  74 68 6f 6e 33 0a 70 72  69 6e 74 28 27 48 65 6c 
 |thon3.print('Hel|
0020  6c 6f 20 57 6f 72 6c 64  27 29 0a |lo World').|
002b


And here is the hexdump for the Raspberry Pi (that does run)

  23 21 2f 75 73 72 2f 62  69 6e 2f 65 6e 76 20 70  |#!/usr/bin/env 
p|
0010  79 74 68 6f 6e 33 0a 70  72 69 6e 74 28 27 48 65 
 |ython3.print('He|
0020  6c 6c 6f 20 57 6f 72 6c  64 27 29 0a  |llo World').|
002c 


I notice the additional “...” as the start of the Shebang on the MacOS 
hexdump. 

What do you see, and what could that mean?

Thanks!

On Friday, March 6, 2020 at 11:30:30 AM UTC-5, Sam Hathaway wrote:
>
> This is very curious. I don’t recognize the formatting in the error 
> message you’re getting when you run it directly. If the shell couldn’t find 
> the interpreter in the shebang line, it should say something like “bad 
> interpreter” and exit immediately. Instead, whatever is executing this file 
> goes on to the second line of the script and chokes on the print() 
> statement. What shell do you use? (You can use echo $SHELL to find out.)
>
> I wonder if there’s some kind of encoding problem or stray bytes at the 
> beginning of the file. Can you send me the output of this command?
>
> hexdump -C /Users/.../Scripts/python_test-01.py
>
> Thanks!
> -sam
>
> On 6 Mar 2020, at 11:12, Paul Gobble wrote:
>
> Sam,
>
> Thank you for your input. Yes, my Mac is running MacOS 10.15.3 Catalina. I 
> tried the tests you suggested, see below.
>
> #!/usr/bin/python3
> paul@Emonda Python-RFP-PDF-Scraper % ./python_test-01.py 
> ./python_test-01.py: line 1: #!/usr/bin/python3: No such file or 
> directory
> ./python_test-01.py: line 2: syntax error near unexpected token `'Hello 
> World''
> ./python_test-01.py: line 2: `print('Hello World')'
> paul@Emonda Python-RFP-PDF-Scraper % ls -le@ ./python_test-01.py 
> -rwxr-xr-x@ 1 paul  staff  43 Mar  6 11:01 ./python_test-01.py
> com.apple.lastuseddate#PS   16 
> com.apple.macl  72 
> paul@Emonda Python-RFP-PDF-Scraper % /usr/bin/python3 ./python_test-01.py 
> Hello World
> paul@Emonda Python-RFP-PDF-Scraper %
>
> So, no, nothing about quarantine was reported.  And yes, if I pass it to 
> /usr/bin/python3 on the command line (the exact same path as in the 
> Shebang) it runs fine. 
>
> On Friday, March 6, 2020 at 9:58:23 AM UTC-5, Sam Hathaway wrote:
>>
>> Paul,
>>
>> I take it you’re on macOS 10.15 Catalina, since /usr/bin/python3 exists.
>>
>> What do you get if you run this?
>>
>> ls -le@ /Users/.../Scripts/python_test-01.py
>>
>> My suspicion is that macOS might have quarantined your script. (I ran 
>> into this once or twice after migrating my data to a fresh 10.15 install 
>> but I don’t recall the exact error message.)
>>
>> If you see com.apple.quarantine in that output, you can run this to 
>> remove the quarantine flag:
>>
>> xattr -d com.apple.quarantine /Users/.../Scripts/python_test-01.py
>>
>> If that isn’t it, I’d be curious to see if you can run the script by 
>> passing it to the interpreter like this:
>>
>> /usr/bin/python3 /Users/.../Scripts/python_test-01.py
>>
>> Hope this helps.
>> -sam
>>
>> On 4 Mar 2020, at 23:25, Paul Gobble wrote:
>>
>> I'm using BBedit 13.0.5 on Mac Os 10.15.3 as my editor while I try to 
>> learn a bit of Python3.  
>>
>> #!/usr/bin/env python3
>> print('Hello World')
>>
>> Baby steps.
>>
>> I try to execute this from the Run menu item in the #! menu and get
>>
>> /Users/.../Scripts/python_test-01.py: line 1: #!/usr/bin/env: No such 
>> file or directory
>>
>> Then I try to use the direct path in the shebang line
>>
>> #!/usr/bin/python3
>> print('Hello World')
>>
>> and get a very similar response
>>
>> /Users.../Scripts/python_test-01.py: line 1: #!/usr/bin/python3: No 
>> such file or directory
>>
>> So I go investigate in the Terminal app and look around.
>>
>> Emonda:bin paul$ pwd
>>
>> /usr/local/bin
>>
>> Emonda:bin paul$ whereis python3
>>
>> /usr/bin/python3
>>
>> Emonda:bin paul$ whereis env
>>
>> /usr/bin/env
>>
>> Emonda:bin paul$ 
>>
>> Both env and python3 are right where I said they were in the shebang 
>> line, but interpreter can't find them!  
>>
>> Can anyone help me out here?  What am I missing?
>>
>> Thanks,
>> Paul
>>
>> -- 
>> This is the BBEdit Talk public discussion group. If you have a feature 
>> request or need technical support, please email "sup...@barebones.com" 
>> rather than posting here. Follow @bbedit on Twitter: <
>> https://twitter.com/bbedit>
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "BBEdit Talk" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to 

Re: Shebang Line Woes

[Sam Hathaway]

This is very curious. I don’t recognize the formatting in the error 
message you’re getting when you run it directly. If the shell 
couldn’t find the interpreter in the shebang line, it should say 
something like “bad interpreter” and exit immediately. Instead, 
whatever is executing this file goes on to the second line of the script 
and chokes on the `print()` statement. What shell do you use? (You can 
use `echo $SHELL` to find out.)


I wonder if there’s some kind of encoding problem or stray bytes at 
the beginning of the file. Can you send me the output of this command?


```
hexdump -C /Users/.../Scripts/python_test-01.py
```

Thanks!
-sam

On 6 Mar 2020, at 11:12, Paul Gobble wrote:


Sam,

Thank you for your input. Yes, my Mac is running MacOS 10.15.3 
Catalina. I

tried the tests you suggested, see below.

#!/usr/bin/python3
paul@Emonda Python-RFP-PDF-Scraper % ./python_test-01.py
./python_test-01.py: line 1: #!/usr/bin/python3: No such file or 
directory
./python_test-01.py: line 2: syntax error near unexpected token 
`'Hello

World''
./python_test-01.py: line 2: `print('Hello World')'
paul@Emonda Python-RFP-PDF-Scraper % ls -le@ ./python_test-01.py
-rwxr-xr-x@ 1 paul  staff  43 Mar  6 11:01 ./python_test-01.py
com.apple.lastuseddate#PS   16
com.apple.macl  72
paul@Emonda Python-RFP-PDF-Scraper % /usr/bin/python3 
./python_test-01.py

Hello World
paul@Emonda Python-RFP-PDF-Scraper %

So, no, nothing about quarantine was reported.  And yes, if I pass it 
to

/usr/bin/python3 on the command line (the exact same path as in the
Shebang) it runs fine.

On Friday, March 6, 2020 at 9:58:23 AM UTC-5, Sam Hathaway wrote:


Paul,

I take it you’re on macOS 10.15 Catalina, since /usr/bin/python3 
exists.


What do you get if you run this?

ls -le@ /Users/.../Scripts/python_test-01.py

My suspicion is that macOS might have quarantined your script. (I ran 
into
this once or twice after migrating my data to a fresh 10.15 install 
but I

don’t recall the exact error message.)

If you see com.apple.quarantine in that output, you can run this to
remove the quarantine flag:

xattr -d com.apple.quarantine /Users/.../Scripts/python_test-01.py

If that isn’t it, I’d be curious to see if you can run the script 
by

passing it to the interpreter like this:

/usr/bin/python3 /Users/.../Scripts/python_test-01.py

Hope this helps.
-sam

On 4 Mar 2020, at 23:25, Paul Gobble wrote:

I'm using BBedit 13.0.5 on Mac Os 10.15.3 as my editor while I try to
learn a bit of Python3.

#!/usr/bin/env python3
print('Hello World')

Baby steps.

I try to execute this from the Run menu item in the #! menu and get

/Users/.../Scripts/python_test-01.py: line 1: #!/usr/bin/env: No 
such

file or directory

Then I try to use the direct path in the shebang line

#!/usr/bin/python3
print('Hello World')

and get a very similar response

/Users.../Scripts/python_test-01.py: line 1: #!/usr/bin/python3: 
No such

file or directory

So I go investigate in the Terminal app and look around.

Emonda:bin paul$ pwd

/usr/local/bin

Emonda:bin paul$ whereis python3

/usr/bin/python3

Emonda:bin paul$ whereis env

/usr/bin/env

Emonda:bin paul$

Both env and python3 are right where I said they were in the shebang 
line,

but interpreter can't find them!

Can anyone help me out here?  What am I missing?

Thanks,
Paul

--
This is the BBEdit Talk public discussion group. If you have a 
feature

request or need technical support, please email "sup...@barebones.com
" rather than posting here. Follow @bbedit on Twitter: <
https://twitter.com/bbedit>
---
You received this message because you are subscribed to the Google 
Groups

"BBEdit Talk" group.
To unsubscribe from this group and stop receiving emails from it, 
send an

email to bbe...@googlegroups.com .
To view this discussion on the web visit
https://groups.google.com/d/msgid/bbedit/e1aaa223-81f1-4c3d-96e6-dd0872e7d420%40googlegroups.com

.




--
This is the BBEdit Talk public discussion group. If you have a feature 
request or need technical support, please email 
"supp...@barebones.com" rather than posting here. Follow @bbedit on 
Twitter: 

---
You received this message because you are subscribed to the Google 
Groups "BBEdit Talk" group.
To unsubscribe from this group and stop receiving emails from it, send 
an email to bbedit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/bbedit/bea4b23d-760a-4e96-a121-93051736af6b%40googlegroups.com.



--
This is the BBEdit Talk public discussion group. If you have a feature request or need 
technical support, please email "supp...@barebones.com" rather than posting here. 
Follow @bbedit on Twitter: 
--- 
You received this message because you are subscribed to the Google Groups "BBEdit Talk" group.

Re: Shebang Line Woes

[Paul Gobble]

Steve,

Thanks for the tip about pyenv, I’ll take a look at that.

And yes, I understand that BBEdit is just the text editor.  I took it our 
of the debugging process at this point just to simplify and standardize the 
environments.  Until I can get this Hello World script to work on both the 
MacOs and the Raspberry Pi,  I’m working on both systems via ssh from my 
iPad using the Blink terminal and using the same, simple tools on both. As 
soon as I get a Hello World from the Mac, I’ll go back to BBEdit.

On Friday, March 6, 2020 at 10:13:40 AM UTC-5, Steve wrote:
>
> On Fri, Mar 6, 2020 at 3:53 AM Paul Gobble  > wrote: 
> > 
> > Steve, 
> > 
> > I took BBEdit out of the testing earlier this evening. I've been doing 
> all my editing with vim and attempting to run the script from the command 
> line.  I've made the two test cases as similar as possible. Both env and 
> Pyton3 reside in /usr/bin on both systems.  The PATH contains /usr/bin in 
> both systems.  the scripts on both systems have the same chmod 755 
> permissions.  The Raspberry Pi runs like you'd expect, the Mac just won't 
> comprehend or acknowledge the Shebang line. 
> > 
> > I'm at a loss. 
> > 
>
> Well, first off, you do realize you could still _edit_ with BBEdit and 
> run from the terminal, right?  BBEdit's an editor (a great and 
> powerful one), not an IDE. 
>
> In any case, the fact you can't run it from the command line tells me 
> there's nothing wrong with BBEdit, there's something wrong with your 
> python install. Sam's suggestion re: Catalina's quarantine is a good 
> one. Alternately, you might investigate how you have python installed. 
> I happen to prefer to utilize the project pyenv to setup my pythons on 
> both Mac and Linux so I can easily control my versions without 
> disturbing the system install and without system-dependant hacks: 
>
> https://github.com/pyenv/pyenv#readme 
>
> Good luck! 
> - Steve 
>

-- 
This is the BBEdit Talk public discussion group. If you have a feature request 
or need technical support, please email "supp...@barebones.com" rather than 
posting here. Follow @bbedit on Twitter: 
--- 
You received this message because you are subscribed to the Google Groups 
"BBEdit Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to bbedit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/bbedit/526a0fc1-3953-4fa2-8d39-0365ab6cd01d%40googlegroups.com.

Re: Shebang Line Woes

[Paul Gobble]

Sam,

Thank you for your input. Yes, my Mac is running MacOS 10.15.3 Catalina. I 
tried the tests you suggested, see below.

#!/usr/bin/python3
paul@Emonda Python-RFP-PDF-Scraper % ./python_test-01.py 
./python_test-01.py: line 1: #!/usr/bin/python3: No such file or directory
./python_test-01.py: line 2: syntax error near unexpected token `'Hello 
World''
./python_test-01.py: line 2: `print('Hello World')'
paul@Emonda Python-RFP-PDF-Scraper % ls -le@ ./python_test-01.py 
-rwxr-xr-x@ 1 paul  staff  43 Mar  6 11:01 ./python_test-01.py
com.apple.lastuseddate#PS   16 
com.apple.macl  72 
paul@Emonda Python-RFP-PDF-Scraper % /usr/bin/python3 ./python_test-01.py 
Hello World
paul@Emonda Python-RFP-PDF-Scraper %

So, no, nothing about quarantine was reported.  And yes, if I pass it to 
/usr/bin/python3 on the command line (the exact same path as in the 
Shebang) it runs fine. 

On Friday, March 6, 2020 at 9:58:23 AM UTC-5, Sam Hathaway wrote:
>
> Paul,
>
> I take it you’re on macOS 10.15 Catalina, since /usr/bin/python3 exists.
>
> What do you get if you run this?
>
> ls -le@ /Users/.../Scripts/python_test-01.py
>
> My suspicion is that macOS might have quarantined your script. (I ran into 
> this once or twice after migrating my data to a fresh 10.15 install but I 
> don’t recall the exact error message.)
>
> If you see com.apple.quarantine in that output, you can run this to 
> remove the quarantine flag:
>
> xattr -d com.apple.quarantine /Users/.../Scripts/python_test-01.py
>
> If that isn’t it, I’d be curious to see if you can run the script by 
> passing it to the interpreter like this:
>
> /usr/bin/python3 /Users/.../Scripts/python_test-01.py
>
> Hope this helps.
> -sam
>
> On 4 Mar 2020, at 23:25, Paul Gobble wrote:
>
> I'm using BBedit 13.0.5 on Mac Os 10.15.3 as my editor while I try to 
> learn a bit of Python3.  
>
> #!/usr/bin/env python3
> print('Hello World')
>
> Baby steps.
>
> I try to execute this from the Run menu item in the #! menu and get
>
> /Users/.../Scripts/python_test-01.py: line 1: #!/usr/bin/env: No such 
> file or directory
>
> Then I try to use the direct path in the shebang line
>
> #!/usr/bin/python3
> print('Hello World')
>
> and get a very similar response
>
> /Users.../Scripts/python_test-01.py: line 1: #!/usr/bin/python3: No such 
> file or directory
>
> So I go investigate in the Terminal app and look around.
>
> Emonda:bin paul$ pwd
>
> /usr/local/bin
>
> Emonda:bin paul$ whereis python3
>
> /usr/bin/python3
>
> Emonda:bin paul$ whereis env
>
> /usr/bin/env
>
> Emonda:bin paul$ 
>
> Both env and python3 are right where I said they were in the shebang line, 
> but interpreter can't find them!  
>
> Can anyone help me out here?  What am I missing?
>
> Thanks,
> Paul
>
> -- 
> This is the BBEdit Talk public discussion group. If you have a feature 
> request or need technical support, please email "sup...@barebones.com 
> " rather than posting here. Follow @bbedit on Twitter: <
> https://twitter.com/bbedit>
> --- 
> You received this message because you are subscribed to the Google Groups 
> "BBEdit Talk" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to bbe...@googlegroups.com .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/bbedit/e1aaa223-81f1-4c3d-96e6-dd0872e7d420%40googlegroups.com
>  
> 
> .
>
>

-- 
This is the BBEdit Talk public discussion group. If you have a feature request 
or need technical support, please email "supp...@barebones.com" rather than 
posting here. Follow @bbedit on Twitter: 
--- 
You received this message because you are subscribed to the Google Groups 
"BBEdit Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to bbedit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/bbedit/bea4b23d-760a-4e96-a121-93051736af6b%40googlegroups.com.

Re: Shebang Line Woes

[Steve deRosier]

On Fri, Mar 6, 2020 at 3:53 AM Paul Gobble  wrote:
>
> Steve,
>
> I took BBEdit out of the testing earlier this evening. I've been doing all my 
> editing with vim and attempting to run the script from the command line.  
> I've made the two test cases as similar as possible. Both env and Pyton3 
> reside in /usr/bin on both systems.  The PATH contains /usr/bin in both 
> systems.  the scripts on both systems have the same chmod 755 permissions.  
> The Raspberry Pi runs like you'd expect, the Mac just won't comprehend or 
> acknowledge the Shebang line.
>
> I'm at a loss.
>

Well, first off, you do realize you could still _edit_ with BBEdit and
run from the terminal, right?  BBEdit's an editor (a great and
powerful one), not an IDE.

In any case, the fact you can't run it from the command line tells me
there's nothing wrong with BBEdit, there's something wrong with your
python install. Sam's suggestion re: Catalina's quarantine is a good
one. Alternately, you might investigate how you have python installed.
I happen to prefer to utilize the project pyenv to setup my pythons on
both Mac and Linux so I can easily control my versions without
disturbing the system install and without system-dependant hacks:

https://github.com/pyenv/pyenv#readme

Good luck!
- Steve

-- 
This is the BBEdit Talk public discussion group. If you have a feature request 
or need technical support, please email "supp...@barebones.com" rather than 
posting here. Follow @bbedit on Twitter: 
--- 
You received this message because you are subscribed to the Google Groups 
"BBEdit Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to bbedit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/bbedit/CALLGbR%2Bnd5_hP8T_4mOcEHywCfp%3DK6USpaKjzKvBoRVLq%2Bf2JQ%40mail.gmail.com.

Re: Shebang Line Woes

[Sam Hathaway]

Paul,

I take it you’re on macOS 10.15 Catalina, since /usr/bin/python3 
exists.


What do you get if you run this?

```
ls -le@ /Users/.../Scripts/python_test-01.py
```

My suspicion is that macOS might have quarantined your script. (I ran 
into this once or twice after migrating my data to a fresh 10.15 install 
but I don’t recall the exact error message.)


If you see `com.apple.quarantine` in that output, you can run this to 
remove the quarantine flag:


```
xattr -d com.apple.quarantine /Users/.../Scripts/python_test-01.py
```

If that isn’t it, I’d be curious to see if you can run the script by 
passing it to the interpreter like this:


```
/usr/bin/python3 /Users/.../Scripts/python_test-01.py
```

Hope this helps.
-sam

On 4 Mar 2020, at 23:25, Paul Gobble wrote:

I'm using BBedit 13.0.5 on Mac Os 10.15.3 as my editor while I try to 
learn

a bit of Python3.

#!/usr/bin/env python3
print('Hello World')

Baby steps.

I try to execute this from the Run menu item in the #! menu and get

/Users/.../Scripts/python_test-01.py: line 1: #!/usr/bin/env: No 
such file

or directory

Then I try to use the direct path in the shebang line

#!/usr/bin/python3
print('Hello World')

and get a very similar response

/Users.../Scripts/python_test-01.py: line 1: #!/usr/bin/python3: No 
such

file or directory

So I go investigate in the Terminal app and look around.

Emonda:bin paul$ pwd

/usr/local/bin

Emonda:bin paul$ whereis python3

/usr/bin/python3

Emonda:bin paul$ whereis env

/usr/bin/env

Emonda:bin paul$

Both env and python3 are right where I said they were in the shebang 
line,

but interpreter can't find them!

Can anyone help me out here?  What am I missing?

Thanks,
Paul

--
This is the BBEdit Talk public discussion group. If you have a feature 
request or need technical support, please email 
"supp...@barebones.com" rather than posting here. Follow @bbedit on 
Twitter: 

---
You received this message because you are subscribed to the Google 
Groups "BBEdit Talk" group.
To unsubscribe from this group and stop receiving emails from it, send 
an email to bbedit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/bbedit/e1aaa223-81f1-4c3d-96e6-dd0872e7d420%40googlegroups.com.



--
This is the BBEdit Talk public discussion group. If you have a feature request or need 
technical support, please email "supp...@barebones.com" rather than posting here. 
Follow @bbedit on Twitter: 
--- 
You received this message because you are subscribed to the Google Groups "BBEdit Talk" group.

To unsubscribe from this group and stop receiving emails from it, send an email 
to bbedit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/bbedit/8B4C3A71-57F0-4CDE-839E-2D19948B50BB%40munkynet.org.

Re: Shebang Line Woes

[Jean-Christophe Helary]

> On Mar 6, 2020, at 13:45, Paul Gobble  wrote:
> 
> Steve,
> 
> I took BBEdit out of the testing earlier this evening. I've been doing all my 
> editing with vim and attempting to run the script from the command line.  
> I've made the two test cases as similar as possible. Both env and Pyton3 
> reside in /usr/bin on both systems.  The PATH contains /usr/bin in both 
> systems.  the scripts on both systems have the same chmod 755 permissions.  
> The Raspberry Pi runs like you'd expect, the Mac just won't comprehend or 
> acknowledge the Shebang line.
> 
> I'm at a loss.

How did you install python3 ?

Jean-Christophe 

-- 
This is the BBEdit Talk public discussion group. If you have a feature request 
or need technical support, please email "supp...@barebones.com" rather than 
posting here. Follow @bbedit on Twitter: 
--- 
You received this message because you are subscribed to the Google Groups 
"BBEdit Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to bbedit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/bbedit/A418D62E-7E8D-44A8-9C7B-E7052407B752%40traduction-libre.org.

Re: Shebang Line Woes

[Paul Gobble]

Steve,

I took BBEdit out of the testing earlier this evening. I've been doing all 
my editing with vim and attempting to run the script from the command line. 
 I've made the two test cases as similar as possible. Both env and Pyton3 
reside in /usr/bin on both systems.  The PATH contains /usr/bin in both 
systems.  the scripts on both systems have the same chmod 755 permissions. 
 The Raspberry Pi runs like you'd expect, the Mac just won't comprehend or 
acknowledge the Shebang line.

I'm at a loss.

On Thursday, March 5, 2020 at 11:23:02 PM UTC-5, Steve wrote:
>
> Did you try on your mac the exact same thing you did on Linux?  ie 
> chmod a+x and try to execute it from the command line?  My bet is it 
> works.  Personally, I don't think I've ever run a python script via 
> BBedit, I always use my terminal.  In any case, validate you can do it 
> from the terminal in a "normal" way first, and then I'd suggest 
> emailing support. 
>
> - Steve 
>
> On Thu, Mar 5, 2020 at 7:23 PM Paul Gobble  > wrote: 
> > 
> > I keep banging my head against this problem.  To try something 
> different, I ssh over to my Raspberry Pi.  I check, and its got Python 3 
> right there in /usr/bin/ . So I use vim to create same script on the 
> Rasperrry Pi, chmod 755, and I see "Hello World" the very first try. 
> > 
> > So to recap, both my PowerBook with macOS 10.15.3 and my Raspberry Pi 
> running Debian GNU/Linux have a version of Python3 installed in their 
> /usr/bin directories.  Both system have /usr/bin in their PATH.  They both 
> have the same two line script and both start with the same Shebang: 
> #!/usr/bin/python3.  The Raspberry Pi works perfect, the Mac can only 
> muster "#!/usr/bin/python3: No such file or directory". 
> > 
> > What is different between the two systems? Where should I look? 
> > 
> > 
> > On Thursday, March 5, 2020 at 7:06:11 AM UTC-5, Paul Gobble wrote: 
> >> 
> >> I'm using BBedit 13.0.5 on Mac Os 10.15.3 as my editor while I try to 
> learn a bit of Python3. 
> >> 
> >> #!/usr/bin/env python3 
> >> print('Hello World') 
> >> 
> >> Baby steps. 
> >> 
> >> I try to execute this from the Run menu item in the #! menu and get 
> >> 
> >> /Users/.../Scripts/python_test-01.py: line 1: #!/usr/bin/env: No such 
> file or directory 
> >> 
> >> Then I try to use the direct path in the shebang line 
> >> 
> >> #!/usr/bin/python3 
> >> print('Hello World') 
> >> 
> >> and get a very similar response 
> >> 
> >> /Users.../Scripts/python_test-01.py: line 1: #!/usr/bin/python3: No 
> such file or directory 
> >> 
> >> So I go investigate in the Terminal app and look around. 
> >> 
> >> Emonda:bin paul$ pwd 
> >> 
> >> /usr/local/bin 
> >> 
> >> Emonda:bin paul$ whereis python3 
> >> 
> >> /usr/bin/python3 
> >> 
> >> Emonda:bin paul$ whereis env 
> >> 
> >> /usr/bin/env 
> >> 
> >> Emonda:bin paul$ 
> >> 
> >> 
> >> Both env and python3 are right where I said they were in the shebang 
> line, but interpreter can't find them! 
> >> 
> >> Can anyone help me out here?  What am I missing? 
> >> 
> >> Thanks, 
> >> Paul 
> > 
> > -- 
> > This is the BBEdit Talk public discussion group. If you have a feature 
> request or need technical support, please email "sup...@barebones.com 
> " rather than posting here. Follow @bbedit on Twitter: <
> https://twitter.com/bbedit> 
> > --- 
> > You received this message because you are subscribed to the Google 
> Groups "BBEdit Talk" group. 
> > To unsubscribe from this group and stop receiving emails from it, send 
> an email to bbe...@googlegroups.com . 
> > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/bbedit/f3a60234-2b25-44bc-8200-58c528dc8bca%40googlegroups.com.
>  
>
>

-- 
This is the BBEdit Talk public discussion group. If you have a feature request 
or need technical support, please email "supp...@barebones.com" rather than 
posting here. Follow @bbedit on Twitter: 
--- 
You received this message because you are subscribed to the Google Groups 
"BBEdit Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to bbedit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/bbedit/e13ef645-c753-42d1-b36f-28b39eff515e%40googlegroups.com.