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.reg
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
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 i
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
save
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 “Unico
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 thi
> 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 t
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
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
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
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
MacO
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:
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
>
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 fre
> 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
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
16 matches
Mail list logo
