[ANN] BBEdit 13.5 (415037) pre-release

[Rich Siegel]

Good afternoon folks,

We're currently working on a feature update to BBEdit 13, which includes 
a number of new features, as well as fixes for previously reported 
issues.


Testing is currently underway, and we have a stable pre-release version 
ready for use.


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 this point not fully tested, there 
_may_ be bugs and regressions.


If this prospect makes you nervous, then sticking with the public 
release versions is your best course of action. Nobody will be offended 
if you choose to do so; you're under no obligation to install and use 
anything but a public release. :-)


Complete change notes to date for all the pre-release builds in this 
cycle are available here:


  

The change notes are organized into additions, changes, and fixes, and 
are annotated where appropriate with case numbers. So if you recognize a 
number corresponding to a support case that was opened for you, you can 
now verify that it's been fixed correctly. Please take the time to 
review the changes before using the new build -- it'll be worth your 
time.




Here is a list of changes since the previous pre-release version:

version 13.5 (415037)   (2020-10-01)

Additions
-

*   Added an expert preference, so that project documents are
allowed to remount volumes when reloading the list of documents
that were open when the project was last closed. This is off by
default, but if for some reason you need to:

	`defaults write com.barebones.bbedit 
ProjectsAllowVolumeMountWhenReopening -bool YES`



Changes
---

+   [DOC] The button in the file panel for adding items to project
documents says "Add to Project" rather than "Open".

*   Change the title of the Preferences window to reflect the
sidebar selection, because apparently that's a thing the HI
guidelines say to do.

Fixes
-

*   [NFR] [DOC] [407854] Harmonized the behavior of the commands on
the "+" sidebar menu for projects vs. non-project windows.

*   [NFR] [407749] Fixed bug in which using "New Text Document" in
the contextual menu when right-clicking on a folder would not
correctly pre-select the desired location in the save panel.

*   [NFR] [407772] Fixed bug in which the "document may have been
modified on the server" warning would appear in situations where
it shouldn't have.

*   [NFR] [407773] Fixed regression in which batch markup tool
operations (Update Site/Folder, etc) didn't process items in
nested folders.

*   [NFR] Fixed bug in which "New Folder" from the sidebar "+"
action menu would present the save panel for creating a new text
file, with a default "untitled.txt" name.

*   [NFR] Limited the amount of text used when generating the
summary line for items in the Rescued Documents window, so that
very large rescued documents don't slow the process down.

*   [400782] Made a change to guard against a logged ctags-related
crash.

*   Made the `DisableScriptAttachments` expert preference work
correctly. (It's not documented for a reason, but should at least
not break the application when turned on.)

*   Fixed a crash which could occur in the ctags support internals
when quitting the application quickly after startup.

*   [407812, 407815] When rewrapping text with quoted lines (or with
lines that look like they might be quoted, like Markdown
headings), the wrapper will no longer put quote markers on blank
lines if the preceding line has quote markers. Thus, blank lines
will stay blank.

*   [393065] When using a project with a local preview server
configured, and live previewing a document in the configured
site, BBEdit will refer asset requests for the previewed page to
the preview server, in the event that it's not able to resolve
those requests relative to the project's configured site root.
(This allows such asset requests to succeed where they would
previously have failed.)

*   [393065] Fixed a bug in which page-relative links (to other
pages) were not constructed correctly when a preview server was
in use for Preview in BBEdit. This in turn meant that the browser
would show a 404 when clicking on such a link in a live preview
window.

*   Corrected the color space used for converting color
representations from external forms (such as the value strings in
color schemes).

*fin*

One final note: If you run into a bug in a pre-release version, PLEASE 
DO NOT REPORT THE BUG 

Re: Color scheme vs. color space question

[François Schiettecatte]

Watts

I took a deeper look at this, I set my background to 2E3440, took a screen 
snapshot, opened that up in Acorn and zoomed in as far as it would go, the 
background is not flat, the pixels are not the same color so there is a texture 
there. 

I also get an issue if I set the background color to the current background 
color using the droplet tool, the background color becomes lighter.

Not sure what is going on here, maybe someone from BB can chime in, or you 
could file a bug report with them.

Cheers

François

> On Oct 1, 2020, at 1:53 PM, Watts Martin  wrote:
> 
> On Thu, Oct 1, 2020 at 9:31 AM François Schiettecatte 
>  wrote:
> 
> Sorry if these are obvious questions:
> 
> They're totally reasonable ones. :)
> 
> - Did you check your color calibration in the Display System Preferences?
> 
> I did; changing my calibration profile doesn't seem to affect the hex codes 
> the Digital Color Meter app picks up, though. I suspect the profile changes 
> the way color #2E3440 looks on your display, but programmatically the color  
> still #2E3440. (But to get the same color between profiles you'd need a 
> different code.)
> 
> - Did you check Night Shift settings in the Display System Preferences?
> 
> I have the same experience and get the same numbers with Night Shift on and 
> with it off, so I suspect it's the same here, too.
> 
> - Finally did you check Display settings in the Accessibility Preferences 
> (specifically Display Contrast, happened to a client of mine)?
> 
> I hadn't, but I did just go check now and "Display Contrast" is set at normal 
> (and "Increase Contrast" is not checked).
> 
> -- Watts
> 
> -- 
> This is the BBEdit Talk public discussion group. If you have a feature 
> request or need technical support, please email "supp...@barebones.com" 
> rather than posting here. Follow @bbedit on Twitter: 
> 
> --- 
> 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 bbedit+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/bbedit/CA%2BGozv0X0RvU9aQdE-%3DDz6xhMuZQ9Rr4cn43DLhOwJCVH3-Ztw%40mail.gmail.com.

-- 
This is the BBEdit Talk public discussion group. If you have a feature request 
or need technical support, please email "supp...@barebones.com" rather than 
posting here. Follow @bbedit on Twitter: 
--- 
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 bbedit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/bbedit/379B4030-04F9-4C1E-B555-84B097B4904C%40gmail.com.

Re: Color scheme vs. color space question

[Watts Martin]

>
> On Thu, Oct 1, 2020 at 9:31 AM François Schiettecatte <
fschietteca...@gmail.com> wrote:

>
Sorry if these are obvious questions:


They're totally reasonable ones. :)

>
- Did you check your color calibration in the Display System Preferences?


I did; changing my calibration profile doesn't seem to affect the hex codes
the Digital Color Meter app picks up, though. I suspect the profile changes
the way color #2E3440 looks on your display, but programmatically the color
 still #2E3440. (But to get the same color between profiles you'd need a
different code.)

>
- Did you check Night Shift settings in the Display System Preferences?


I have the same experience and get the same numbers with Night Shift on and
with it off, so I suspect it's the same here, too.

>
- Finally did you check Display settings in the Accessibility Preferences
> (specifically Display Contrast, happened to a client of mine)?


I hadn't, but I did just go check now and "Display Contrast" is set at
normal (and "Increase Contrast" is not checked).

>
-- Watts

-- 
This is the BBEdit Talk public discussion group. If you have a feature request 
or need technical support, please email "supp...@barebones.com" rather than 
posting here. Follow @bbedit on Twitter: 
--- 
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 bbedit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/bbedit/CA%2BGozv0X0RvU9aQdE-%3DDz6xhMuZQ9Rr4cn43DLhOwJCVH3-Ztw%40mail.gmail.com.

Re: QuickLook in Finder for files associated with BBEdit

['Gregory Shenaut' via BBEdit Talk]

The only thing that has worked for me is to avoid idiosyncratic dot-style (.) 
extensions in favor of dash-style ones (-). For example, in your case, use 
foobar-semkey instead of foobar.semkey. IMHO this dependence on dot extensions 
to determine file type is one of the most embarrassing things about macOS.

The change they made not long ago to a generalized method dealing with them 
killed off the idea of a universal default, which used to be a way of working 
around it for quicklooking text files.
Greg

> On Oct 1, 2020, at 10:18 , Alfredo  wrote:
> 
> Any news/updates on this? 
> 
> Thanks.
> 
> Alfredo
> 
> On Friday, January 10, 2020 at 9:13:35 PM UTC-7 Matthew Dahlman wrote:
> I'd like to be able to preview all text files using QuickLook in Finder. 
> Functionally, this means I could hit  and get a useful preview of a 
> file in the popup window that appears. Likewise, the same preview behavior is 
> visible when you bring up file info by right-clicking in the Finder and 
> selecting "Get Info".
> 
> Does anyone know if there is a way to force all files associated with BBEdit 
> to have a useful text preview?
> 
> Here's the current behavior that I see.
> Notice that both files are associated with BBEdit. This is good.
> But the file on the left, with the extension "semkey", has what I call a 
> non-useful preview.
> The file on the right, with the extension "yaml", has a useful preview.
> 
> Previously I had a non-useful preview for both filetypes. I installed 
> QLStephen 
> 
>  to attempt to solve this. It seems that later MacOS releases like Catalina 
> have tightened security such that QLStephen doesn't work "out of the box" as 
> easily as it did in the past. Installing it was not sufficient. But manually 
> adding public.yaml in the relevant place in the Info.plist 
> file solves the problem for .yaml files. Hooray!
> 
> But manually adding public.semkey in the relevant place does 
> nothing to help with my non-standard .semkey extension. Presumably this is 
> because "semkey" is not a thing in the way that "yaml" is registered as a 
> thing. There's an important lack of precision in that last sentence... but I 
> lack the relevant knowledge to make it better. 
> 
> So getting back to the initial question, are other BBEdit users able to 
> preview all of their text files in a useful way?
> Because the file "Kind" is "BBEdit.app Document", it seems reasonable that 
> perhaps BBEdit can facilitate the preview. No?
> 
> Thanks for any advice,
> Matt
> 
> 
> 
> 
> 
> 
> 
> 
> -- 
> This is the BBEdit Talk public discussion group. If you have a feature 
> request or need technical support, please email "supp...@barebones.com" 
> rather than posting here. Follow @bbedit on Twitter: 
> >
> --- 
> 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 bbedit+unsubscr...@googlegroups.com 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/bbedit/197507e1-d344-48ec-896f-227d1c08c6e6n%40googlegroups.com
>  
> .

-- 
This is the BBEdit Talk public discussion group. If you have a feature request 
or need technical support, please email "supp...@barebones.com" rather than 
posting here. Follow @bbedit on Twitter: 
--- 
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 bbedit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/bbedit/A8534739-C28A-4E29-9E5A-9C1B31118219%40me.com.

Re: QuickLook in Finder for files associated with BBEdit

[Gerald Davenport]

I would also like to know as css does not have a preview when doing a
quicklook on it as well as get info.

- gerald

On Thu, Oct 1, 2020 at 10:18 AM Alfredo  wrote:

> Any news/updates on this?
>
> Thanks.
>
> Alfredo
>
> On Friday, January 10, 2020 at 9:13:35 PM UTC-7 Matthew Dahlman wrote:
>
>> I'd like to be able to preview all text files using QuickLook in Finder.
>> Functionally, this means I could hit  and get a useful preview of a
>> file in the popup window that appears. Likewise, the same preview behavior
>> is visible when you bring up file info by right-clicking in the Finder and
>> selecting "Get Info".
>>
>> Does anyone know if there is a way to force all files associated with
>> BBEdit to have a useful text preview?
>>
>> Here's the current behavior that I see.
>> Notice that both files are associated with BBEdit. This is good.
>> But the file on the left, with the extension "semkey", has what I call a
>> non-useful preview.
>> The file on the right, with the extension "yaml", has a useful preview.
>>
>> Previously I had a non-useful preview for *both* filetypes. I installed
>> QLStephen
>> 
>> to attempt to solve this. It seems that later MacOS releases like Catalina
>> have tightened security such that QLStephen doesn't work "out of the box"
>> as easily as it did in the past. Installing it was not sufficient. But
>> manually adding public.yaml in the relevant place in
>> the Info.plist file solves the problem for .yaml files. Hooray!
>>
>> But manually adding public.semkey in the relevant place
>> does nothing to help with my non-standard .semkey extension. Presumably
>> this is because "semkey" is not a thing in the way that "yaml" is
>> registered as a thing. There's an important lack of precision in that last
>> sentence... but I lack the relevant knowledge to make it better.
>>
>> So getting back to the initial question, are other BBEdit users able to
>> preview all of their text files in a useful way?
>> Because the file "Kind" is "BBEdit.app Document", it seems reasonable
>> that perhaps BBEdit can facilitate the preview. No?
>>
>> Thanks for any advice,
>> Matt
>>
>>
>> [image: Screen Shot 2020-01-10 at 3.59.23 PM.png]
>>
>>
>>
>> --
> This is the BBEdit Talk public discussion group. If you have a feature
> request or need technical support, please email "supp...@barebones.com"
> 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 bbedit+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/bbedit/197507e1-d344-48ec-896f-227d1c08c6e6n%40googlegroups.com
> 
> .
>

-- 
 




Byers is committed to protecting your health and safety with a Virtual 
Consultation. 

Reviews on 
Google 

 
• Give Us Feedback 



We are here to help you Stay Safe! 


-- 
This is the BBEdit Talk public discussion group. If you have a feature request 
or need technical support, please email "supp...@barebones.com" rather than 
posting here. Follow @bbedit on Twitter: 
--- 
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 bbedit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/bbedit/CAJMCtK34e1gKYi%3DpnM3p5pLk-S%3DbRyk2Uo%2BB6_Gt7z4aObg%2B9Q%40mail.gmail.com.

Re: QuickLook in Finder for files associated with BBEdit

[Alfredo]

Any news/updates on this? 

Thanks.

Alfredo

On Friday, January 10, 2020 at 9:13:35 PM UTC-7 Matthew Dahlman wrote:

> I'd like to be able to preview all text files using QuickLook in Finder. 
> Functionally, this means I could hit  and get a useful preview of a 
> file in the popup window that appears. Likewise, the same preview behavior 
> is visible when you bring up file info by right-clicking in the Finder and 
> selecting "Get Info".
>
> Does anyone know if there is a way to force all files associated with 
> BBEdit to have a useful text preview?
>
> Here's the current behavior that I see.
> Notice that both files are associated with BBEdit. This is good.
> But the file on the left, with the extension "semkey", has what I call a 
> non-useful preview.
> The file on the right, with the extension "yaml", has a useful preview.
>
> Previously I had a non-useful preview for *both* filetypes. I installed 
> QLStephen 
> 
>  
> to attempt to solve this. It seems that later MacOS releases like Catalina 
> have tightened security such that QLStephen doesn't work "out of the box" 
> as easily as it did in the past. Installing it was not sufficient. But 
> manually adding public.yaml in the relevant place in 
> the Info.plist file solves the problem for .yaml files. Hooray!
>
> But manually adding public.semkey in the relevant place 
> does nothing to help with my non-standard .semkey extension. Presumably 
> this is because "semkey" is not a thing in the way that "yaml" is 
> registered as a thing. There's an important lack of precision in that last 
> sentence... but I lack the relevant knowledge to make it better. 
>
> So getting back to the initial question, are other BBEdit users able to 
> preview all of their text files in a useful way?
> Because the file "Kind" is "BBEdit.app Document", it seems reasonable that 
> perhaps BBEdit can facilitate the preview. No?
>
> Thanks for any advice,
> Matt
>
>
> [image: Screen Shot 2020-01-10 at 3.59.23 PM.png]
>
>
>
>

-- 
This is the BBEdit Talk public discussion group. If you have a feature request 
or need technical support, please email "supp...@barebones.com" rather than 
posting here. Follow @bbedit on Twitter: 
--- 
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 bbedit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/bbedit/197507e1-d344-48ec-896f-227d1c08c6e6n%40googlegroups.com.

Re: Color scheme vs. color space question

[François Schiettecatte]

Sorry if these are obvious questions:

- Did you check your color calibration in the Display System Preferences?

- Did you check Night Shift settings in the Display System Preferences?

- Finally did you check Display settings in the Accessibility Preferences 
(specifically Display Contrast, happened to a client of mine)?

Cheers

François

> On Oct 1, 2020, at 9:22 AM, Watts Martin  wrote:
> 
> After Greg's question yesterday about color schemes, I thought about trying 
> to make a BBEdit version of Nord. And I did... except the background color is 
> really, really light compared to what it should be.
> 
> So, I double-checked: I'd entered the proper background color, #2E3440, and 
> BBEdit indeed says that's what it is. So I used the Digital Color Meter app 
> and set it to sRGB -- double-checking that now it measured the background 
> color of this swatch on the Nord web page as #2E3440 -- and BBEdit's 
> background measured as #3D4451. It seems like all of BBEdit's color swatches 
> are being changed to colors that don't match. However, if I change the color 
> meter to "Generic RGB," then BBEdit's background measures as #2E3440... but 
> the web page color swatches no longer match the hex codes they're supposed to 
> be.
> 
> So: is BBEdit operating in a different color space that I'm going to have to 
> convert these color hex codes to, or is something else going on here? (I'm 
> hesitant to report this as a "bug," although a cursory check of a couple 
> other popular color scheme web sites -- Dracula and Solarized -- suggests 
> they're mapping their hex codes to sRGB, too, so this could make porting 
> schemes to BBEdit extra fiddly.)
> 
> -- 
> This is the BBEdit Talk public discussion group. If you have a feature 
> request or need technical support, please email "supp...@barebones.com" 
> rather than posting here. Follow @bbedit on Twitter: 
> 
> --- 
> 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 bbedit+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/bbedit/CA%2BGozv32mAXnc1dXTA8j4tpG-HRVANQtP%2BNr%3DoPTx-EBxGmzuQ%40mail.gmail.com.


-- 
This is the BBEdit Talk public discussion group. If you have a feature request 
or need technical support, please email "supp...@barebones.com" rather than 
posting here. Follow @bbedit on Twitter: 
--- 
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 bbedit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/bbedit/66F908AA-4805-4809-8948-90161C4C6D0D%40gmail.com.

Color scheme vs. color space question

[Watts Martin]

After Greg's question yesterday about color schemes, I thought about trying
to make a BBEdit version of Nord. And I did... except the background color
is really, really light compared to what it should be.

So, I double-checked: I'd entered the proper background color, #2E3440, and
BBEdit indeed says that's what it is. So I used the Digital Color Meter app
and set it to sRGB -- double-checking that now it measured the background
color of this swatch on the Nord web page
 as #2E3440 -- and
BBEdit's background measured as #3D4451. It seems like all of BBEdit's
color swatches are being changed to colors that don't match. However, if I
change the color meter to "Generic RGB," then BBEdit's background measures
as #2E3440... but the web page color swatches no longer match the hex codes
they're supposed to be.

So: is BBEdit operating in a different color space that I'm going to have
to convert these color hex codes to, or is something else going on here?
(I'm hesitant to report this as a "bug," although a cursory check of a
couple other popular color scheme web sites -- Dracula and Solarized --
suggests they're mapping their hex codes to sRGB, too, so this could make
porting schemes to BBEdit extra fiddly.)

-- 
This is the BBEdit Talk public discussion group. If you have a feature request 
or need technical support, please email "supp...@barebones.com" rather than 
posting here. Follow @bbedit on Twitter: 
--- 
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 bbedit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/bbedit/CA%2BGozv32mAXnc1dXTA8j4tpG-HRVANQtP%2BNr%3DoPTx-EBxGmzuQ%40mail.gmail.com.

Re: Cobalt2 color scheme

[Greg Raven]

If you think it will help, I'd be happy to share my Color Scheme file. Just 
let me know.

On Thursday, October 1, 2020 at 6:25:34 AM UTC-7 ryen...@gmail.com wrote:

> I've converted a couple of themes over the years, but it's been a long 
> time. I would be interested in porting some themes over though. I use One 
> Dark in PyCharm quite a bit. I'm familiar with Cobalt 2 also. When I get 
> some free time, I'll try to make one. I would like to see the Wiki updated 
> with some current theme offerings. Perhaps I need to look into that as 
> well. :)
>
> On Thursday, October 1, 2020 at 7:49:25 AM UTC-4 Greg Raven wrote:
>
>> Good suggestion. I hadn't looked at the built-in themes for awhile. 
>> Toothpaste is close to Cobalt2, which gives me a good starting point for 
>> creating my own version. The biggest obstacle I'm facing now is that Visual 
>> Studio Code and BBEdit use different nomenclature to refer to various GUI 
>> elements, which makes it tough to transfer color specifications from one to 
>> the other easily.
>>
>> On Wednesday, September 30, 2020 at 9:17:53 AM UTC-7 Watts Martin wrote:
>>
>>> You could try some of the other included schemes and see what you think; 
>>> I'm not usually a dark scheme person, but I like "Toothpaste" (it's 
>>> reminiscent of Zenburn, one of the few dark color schemes I like for other 
>>> editors when it's done right).
>>>
>>> There are a few color schemes on the BBEdit Extras wiki, although 
>>> they're mostly using the old, more limited schema from before BBEdit 11, 
>>> and there's a good chance many of the links are broken. It'd be kind of 
>>> neat to try and come up with a system for converting TextMate themes to 
>>> BBEdit color schemes, but it might be a fairly significant undertaking, as 
>>> their formats are very different.
>>>
>>> On Wed, Sep 30, 2020 at 7:13 AM Greg Raven  wrote:
>>>
 I just watched a coding video on YouTube where the presenter said he 
 was using the Cobalt2 theme for VS Code. Maybe it's because I've been 
 using 
 the default BBEdit color scheme for almost 30 years, but it looked pretty 
 good.

 Does anyone have a similar Color Scheme for BBEdit?

 I took a look at making my own CLM, but I'm not certain I could ever 
 get to that level of hacktivism.

 -- 
 This is the BBEdit Talk public discussion group. If you have a feature 
 request or need technical support, please email "sup...@barebones.com" 
 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 bbedit+un...@googlegroups.com.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/bbedit/e33b839d-d3d1-4ca2-8584-6d85d0e65f84n%40googlegroups.com
  
 
 .

>>>

-- 
This is the BBEdit Talk public discussion group. If you have a feature request 
or need technical support, please email "supp...@barebones.com" rather than 
posting here. Follow @bbedit on Twitter: 
--- 
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 bbedit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/bbedit/3246ab0b-cf0b-4bb9-99d1-0ac73f61c36dn%40googlegroups.com.

Re: Cobalt2 color scheme

[Rick Yentzer]

I've converted a couple of themes over the years, but it's been a long 
time. I would be interested in porting some themes over though. I use One 
Dark in PyCharm quite a bit. I'm familiar with Cobalt 2 also. When I get 
some free time, I'll try to make one. I would like to see the Wiki updated 
with some current theme offerings. Perhaps I need to look into that as 
well. :)

On Thursday, October 1, 2020 at 7:49:25 AM UTC-4 Greg Raven wrote:

> Good suggestion. I hadn't looked at the built-in themes for awhile. 
> Toothpaste is close to Cobalt2, which gives me a good starting point for 
> creating my own version. The biggest obstacle I'm facing now is that Visual 
> Studio Code and BBEdit use different nomenclature to refer to various GUI 
> elements, which makes it tough to transfer color specifications from one to 
> the other easily.
>
> On Wednesday, September 30, 2020 at 9:17:53 AM UTC-7 Watts Martin wrote:
>
>> You could try some of the other included schemes and see what you think; 
>> I'm not usually a dark scheme person, but I like "Toothpaste" (it's 
>> reminiscent of Zenburn, one of the few dark color schemes I like for other 
>> editors when it's done right).
>>
>> There are a few color schemes on the BBEdit Extras wiki, although they're 
>> mostly using the old, more limited schema from before BBEdit 11, and 
>> there's a good chance many of the links are broken. It'd be kind of neat to 
>> try and come up with a system for converting TextMate themes to BBEdit 
>> color schemes, but it might be a fairly significant undertaking, as their 
>> formats are very different.
>>
>> On Wed, Sep 30, 2020 at 7:13 AM Greg Raven  wrote:
>>
>>> I just watched a coding video on YouTube where the presenter said he was 
>>> using the Cobalt2 theme for VS Code. Maybe it's because I've been using the 
>>> default BBEdit color scheme for almost 30 years, but it looked pretty good.
>>>
>>> Does anyone have a similar Color Scheme for BBEdit?
>>>
>>> I took a look at making my own CLM, but I'm not certain I could ever get 
>>> to that level of hacktivism.
>>>
>>> -- 
>>> This is the BBEdit Talk public discussion group. If you have a feature 
>>> request or need technical support, please email "sup...@barebones.com" 
>>> 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 bbedit+un...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/bbedit/e33b839d-d3d1-4ca2-8584-6d85d0e65f84n%40googlegroups.com
>>>  
>>> 
>>> .
>>>
>>

-- 
This is the BBEdit Talk public discussion group. If you have a feature request 
or need technical support, please email "supp...@barebones.com" rather than 
posting here. Follow @bbedit on Twitter: 
--- 
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 bbedit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/bbedit/5a5784ff-e74c-4472-8299-a401a6304b13n%40googlegroups.com.

Re: Cobalt2 color scheme

[Greg Raven]

Good suggestion. I hadn't looked at the built-in themes for awhile. 
Toothpaste is close to Cobalt2, which gives me a good starting point for 
creating my own version. The biggest obstacle I'm facing now is that Visual 
Studio Code and BBEdit use different nomenclature to refer to various GUI 
elements, which makes it tough to transfer color specifications from one to 
the other easily.

On Wednesday, September 30, 2020 at 9:17:53 AM UTC-7 Watts Martin wrote:

> You could try some of the other included schemes and see what you think; 
> I'm not usually a dark scheme person, but I like "Toothpaste" (it's 
> reminiscent of Zenburn, one of the few dark color schemes I like for other 
> editors when it's done right).
>
> There are a few color schemes on the BBEdit Extras wiki, although they're 
> mostly using the old, more limited schema from before BBEdit 11, and 
> there's a good chance many of the links are broken. It'd be kind of neat to 
> try and come up with a system for converting TextMate themes to BBEdit 
> color schemes, but it might be a fairly significant undertaking, as their 
> formats are very different.
>
> On Wed, Sep 30, 2020 at 7:13 AM Greg Raven  wrote:
>
>> I just watched a coding video on YouTube where the presenter said he was 
>> using the Cobalt2 theme for VS Code. Maybe it's because I've been using the 
>> default BBEdit color scheme for almost 30 years, but it looked pretty good.
>>
>> Does anyone have a similar Color Scheme for BBEdit?
>>
>> I took a look at making my own CLM, but I'm not certain I could ever get 
>> to that level of hacktivism.
>>
>> -- 
>> This is the BBEdit Talk public discussion group. If you have a feature 
>> request or need technical support, please email "sup...@barebones.com" 
>> 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 bbedit+un...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/bbedit/e33b839d-d3d1-4ca2-8584-6d85d0e65f84n%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
This is the BBEdit Talk public discussion group. If you have a feature request 
or need technical support, please email "supp...@barebones.com" rather than 
posting here. Follow @bbedit on Twitter: 
--- 
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 bbedit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/bbedit/595eeaa3-b330-4f0e-8b72-3d9ea6b7d14en%40googlegroups.com.