Bike 2.0 (Preview 263-265)

[jessegrosjean]

265:

• Added get() method to color themes (for custom theme colors)
• Derive default caret and active line colors from system selection color
• Fixed crash when pasting hierarchical (indented) text
• Fixed markdown escaping to avoid unnecessary escapes (still more to do)

264:

• Fixed cut/paste sometimes cutting more than selected

263:

• Added Settings > Keybindings
• Added Show keybindings in “Show Commands” lists
• Added “Include in new documents” option filter queries
• Changed open URL to activate app and prompt user

Fixes

• Fixed caret up/down movement getting stuck on same row
• Fixed autocorrect duplicate apostrophe when smart quotes is off
• Fixed sidebar disclosure button not clickable after item gains children
• Fixed sidebar query selection not updating on back navigation
• Fixed preserve other text styles when setting font weight
• Fixed word marked as misspelled while still typing it
• Fixed sidebar drag-and-drop ordering
• Fixed Copy as Bike Markdown excludes front matter
• Fixed some BikeMarkdown encoder/decoder bugs
• Fixed crash when creating heading after joining rows
• Fixed occasional crash on extension reload
• Benchmarking and optimization

I got a bit derailed this release, that took longer than expected :\ And I didn’t quite get to status bar. So focus for next release is again status bar + bugs.

Big new feature to try is Settings > Keybindings… so now you can change keybindings without having to create an extension!

---

Oh, forgot to mention in release notes, but I’ve also removed most of the default themes. I think I better get just a few like I want, then can add others. If you loved one of the prev themes they are still available here.

Download:

• Downloads
• Extensions API
• Known Bugs

[jessegrosjean]

Just noticed this release has serious bug when cut/paste. Sometimes cuts more then requested, and then messes up cursor positioning… Will get a fix out soon, but likely not today.

[jessegrosjean]

I’ve just posted 264 which should fix the cut, then bad state issue.

[complexpoint]

In 264 the default style specifies gray (rather than blue) links ?

(e.g. see the link below to a measuredTree function)

[jessegrosjean]

@complexpoint

In 264 the default style specifies gray (rather than blue) links ?

In the default theme it should be based on accent color… maybe you changed system appearance color? (also, at moment you will need to restart Bike to pickup changes in that system setting)

[Erlend]

I’ve added different heading colours to my theme:

"heading1": "$red", 
"heading2": "$orange",
"heading3": "$yellow",
"heading4": "$green",
"heading5": "$blue",
"heading6": "$purple",

How can I then reference these in an editor style?

First I tried row.text.color = context.theme.colors.heading2, but I got a TypeScript error. Then I tried to add heading2 (etc.) to api/style/editor-theme.d.ts:

interface ColorTheme {
  // Core colors
  readonly text: Color
  readonly accent: Color
  readonly background: Color

  // Caret and selection
  readonly caret: Color
  readonly caretLine: Color
  readonly caretMessage: Color
  readonly textBackgroundSelected: Color
  readonly blockBackgroundSelected: Color
  readonly findMatch: Color
  readonly findMatchCurrent: Color

  // UI elements
  readonly handle: Color
  readonly handleUnloaded: Color
  readonly guideLine: Color
  readonly focusArrow: Color

  // Annotations
  readonly grammar: Color
  readonly spelling: Color
  readonly replacement: Color

  // Custom heading colors
  readonly heading1: Color
  readonly heading2: Color
  readonly heading3: Color
  readonly heading4: Color
  readonly heading5: Color
  readonly heading6: Color
}

But that didn’t work either. I also tried to add them to theme-schema.json. Is this not possible?

I haven’t tried to add the colours straight into the bike-style.ts — but I thought they belonged in the theme. (Claude suggested adding something to util.ts.)

[jessegrosjean]

@Erlend

But that didn’t work either. I also tried to add them to theme-schema.json. Is this not possible?

Hum… no looks like not possible yet. I had intended to do that, but fell off my radar. My plan had been to allow array style access for custom defined colors. Assuming that’s possible, I’ll add for next release.

[complexpoint]

@jessegrosjean

In the default theme it should be based on accent color

Thanks !

( Yes it, adapts, very neatly, after closing and reopening, to the setting in
System > Appearance > Theme > Colour )

[Erlend]

Assuming that’s possible, I’ll add for next release.

Cool! Then I’ll wait a bit more to get my editor style up and running again. (Much of the most important bits depend on heading colours…)

[jessegrosjean]

@Erlend

Cool! Then I’ll wait a bit more to get my editor style up and running again. (Much of the most important bits depend on heading colours…)

You should now be able to use colors.get("customName") in 265.

[jessegrosjean]

Just posted 265, using this thread since not any big new features, just some fixes.

[mitchellm]

Thanks for this update! I am not a coder or even a novice one! One request earlier in the thread was to do this sort of custom coloring:

“heading1”: “$red”,
“heading2”: “$orange”,
“heading3”: “$yellow”,
“heading4”: “$green”,
“heading5”: “$blue”,
“heading6”: “$purple”,

So how would I get at this coloring with the new changes? I was able to customize my favorite theme to color headings in general and also make some other color changes, but having no luck with adding content to color specific levels of headings. Then again, I’m a complete dummy at all this!

[Erlend]

I have a way of doing this — but it is with an editor style. So not zero coding.

I can paste what I’m doing later — but don’t have the time today! When I’m done moving the editor style to this new version, you could of course install it. (And also edit it to suit your needs.) But it’s not super simple yet.

[jessegrosjean]

@mitchellm

Thanks for this update! I am not a coder or even a novice one! One request earlier in the thread was to do this sort of custom coloring:

Alas, for that you’ll need to dig into the style (coding) side of things.

The amount of code that you would need is quite minimal. For example this is all you will need to make level 1 headings red and level 2 green. But it does mean you’ll have to setup the bike-extension-kit env to build this code into an extension.

import { Color, defineEditorStyleModifier } from 'bike/style'

let modifier = defineEditorStyleModifier('headinglevels', 'Heading Levels')

modifier.layer('row-formatting', (row) => {
  row(`.heading level() = 1`, (context, row) => {
    row.text.color = Color.systemRed()
  })
  row(`.heading level() = 2`, (context, row) => {
    row.text.color = Color.systemGreen()
  })
})

I’ll include a more complete example extension in the next Bike release.

[mitchellm]

Sounds good. Many thanks.

[mitchellm]

Thanks for sharing when your style when done. I’m sure I’ll learn a lot from the way to constructed your style!

[jessegrosjean]

Here’s the heading levels example. Needs latest preview (266) to work I think.

bike-extension-kit/src/headinglevels.bkext at main ·...