And yet, when you create an .sh or .zsh file, BBEdit colorizes it, so there 
must be definitions somewhere.

On Wednesday, December 30, 2020 at 5:45:53 AM UTC-8 [email protected] wrote:

> ... one addition: I also opened the Content of BBEdit.app and have found 
> *.txt files for Fortran , C ... etc - but not for shell keywords
>
> Peace Keeper schrieb am Mittwoch, 30. Dezember 2020 um 14:32:00 UTC+1:
>
>> Hi Greg,
>> sorry to say it's not :D There you could select the colors you would like 
>> to assign e.g. a comment or a string. But a) there is no folder for *sh* 
>> or shell languages and b) there are no keywords mentioned ( e.g. '#' is a 
>> keyword for a comment )
>> In the Languages section of the preference you could see that for the 
>> Unic Shell Script a 'sh' extension is used as default and the version of 
>> the language module. But you can't drill into the module itself.
>>
>>
>> Greg Raven schrieb am Mittwoch, 30. Dezember 2020 um 14:21:55 UTC+1:
>>
>>> My guess is that it would be under the Text Colors section of BBEdit 
>>> preferences.
>>>
>>> On Wednesday, December 30, 2020 at 2:20:18 AM UTC-8 [email protected] 
>>> wrote:
>>>
>>>> I am using zsh as my favourite shell. So I want to check how and which 
>>>> words are highlighted by bbedit. When I understand it right, the sh 
>>>> language is a build in language ?
>>>> So is there any possibility to see what keywords and syntax is 
>>>> supported by bbedit for sh ( to extend that later also to zsh )
>>>>
>>>> When I am correct then is the  Module documentation (of shebang menu) 
>>>> only for Perl ? Is it a possibility to extend that to other languages ( 
>>>> like zsh ) ?
>>>>
>>>

-- 
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/015f4816-bb54-4854-8922-b5c76886671an%40googlegroups.com.

Reply via email to