Quoting the "BBEdit 13.1 Release Notes" from
https://www.barebones.com/support/bbedit/notes-13.1.html

> BBEdit has built-in support for cmark as well as "classic" Markdown
(Gruber's original Markdown.pl script). In addition, if you have Discount,
MultiMarkdown, cmark-gfm, or Pandoc installed, BBEdit can use those as
well. If a particular tool is not installed, its corresponding option on
the menu is disabled.
>
> Finally, the "Custom" option provides the means to specify your own
rendering command and arguments. There are some rules that you must follow:
>
> The command name must be available in $PATH. You can specify a fully
qualified path, but this is discouraged.
>

1. Where is BBEdit getting its $PATH definition from?

2. Can it be edited?

The reason that I ask is that for the past several years, macOS has had no
good way to define the $PATH for GUI applications, and most do not even
include /usr/local/bin/.

Since BBEdit can put a tool into /usr/local/bin/ then I assume it also
includes /usr/local/bin/ in its $PATH but I also put scripts that I have
written into /usr/local/scripts/ however there is no easy way to tell most
GUI apps of that path except using a fully qualified path, so I'm wondering
what I should do in BBEdit's case.

Obviously this would be easily fixable if Apple would create a way to
define a $PATH for GUI apps, but since it took away the previous one and
hasn't come up with an alternative for many years, I'm not holding my
breath.

TJ

-- 
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/CADjGqHv2Vj0zr_jYrs%2BaL4p7pKRQcsvS2EdBHMhQBmpK3U52hQ%40mail.gmail.com.

Reply via email to