apropos of Rich's observations above, I posted the following on the Joplin
Discourse page:
This may be a bug. If it isn't, it's jut not very intuitive. I had a
similar problem: if I had the external editor set to
/Applications/BBedit.app in Joplin's Preferences, then every time I tried
to use
Thanks Rich! That did the trick. The glob identified files are now opened
together in their own window. ```bbedit --new-window *.py```
Neat!
J.
On Saturday, February 26, 2022 at 2:11:42 PM UTC-8 sie...@barebones.com
wrote:
> On 25 Feb 2022, at 15:01, jjon wrote:
>
> > `bbedit *.p
>
> On 2022-02-25, at 21:01, jjon wrote:
>
> `bbedit *.py` opens all the ".py" files in the current directory in the
> front window. That's great.
>
> `bbedit *.py --new-window` opens each ".py" file in its own new separate
> window
>
> But, what
`bbedit *.py` opens all the ".py" files in the current directory in the
front window. That's great.
`bbedit *.py --new-window` opens each ".py" file in its own new separate
window
But, what if I want to open all the ".py" files in the current directory
_together_ in their own new window?
--
I'm missing something obvious: Running python scripts from within BBedit
12.6.4 doesn't seem to respect anything I put in the shebang line. BBedit
runs python3.7 no matter what. The entire contents of p3test.py is
help()
if I run it with command R the log file I get reads:
Welcome to Python
Scot,
Good of you to take a shot at this. Sorry I didn't notice your
response until recently. I provide below the response from the BBedit
support folks in case anybody else has ever been bothered by this.
The specific problem, it appears, is caused by a runtime condition in
bbedit that they
The subversion menu does not offer this. So I set the env variable
SVN_EDITOR (I first tried it in the shell, and then edited ~/.MacOSX/
environment.plist: same behavior in both cases.) but when I try
svn propedit -r 45 --revprop svn:log
from the command line, bbedit is launched but with no
