A thought:
If a package is installed into one of these environments, is Terminal.app
"aware" of this and able to execute the commands? In such a scenario, I'm
thinking it might be necessary to utilize a Worksheet...
Can anyone confirm this for me?
On Monday, July 26, 2021 at 11:00:16 AM UTC-4 Christopher Finazzo wrote:
> Ugh, false alarm.
>
> Restart BBEdit and there it is. As I get a new SE project going I will
> continue to test.
>
> On Monday, July 26, 2021 at 10:52:23 AM UTC-4 Christopher Finazzo wrote:
>
>> Although I haven't used Python extensively before, I was glad to see
>> support for conda in BBEdit 14. The Standard Ebooks project uses Python
>> extensively for their toolset and having an isolated environment within
>> BBEdit should make using it much easier.
>>
>> Yet, after installing miniconda, running the init, and and creating an
>> environment, I cannot get it to appear in the `#!` menu.
>>
>>
>> 1. `brew install --cask miniconda`
>> 2. `conda init "$(basename "${SHELL}")"`
>> 3. `conda config --add channels conda-forge`
>> 4. `conda create -n standardebooks`
>> 5. `conda activate standardebooks`
>> 6. `conda install -c conda-forge standardebooks`
>>
>> Did I miss a step?
>>
>>
>
--
This is the BBEdit Talk public discussion group. If you have a feature request
or need technical support, please email "[email protected]" 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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/bbedit/584331d3-33fb-4ca5-921d-d83ed0f90748n%40googlegroups.com.
