I’ve marked Bike 1.7 (96) as public release and updated this post to include full 1.7 release notes. Thanks to everyone who tried all the 1.7 preview releases. Now onto the next version!
Text checking is the big focus of this release. For an overview and some demos please see: Bike: Improved macOS text checking.
- Consistently applies autocorrect as you type
- Consistently shows correction popup at end of word
- Consistently shows correction marks and spelling errors
- Use Delete as a shortcut to undo the previous autocorrect
- Undo autocorrect only. Don’t undo text that you typed
- Bounces caret when about to show the correction popup
- Text checking is disabled in code formatted text
- Text checking panel shows all options for easy access
- Text checking panel finds spelling, smart quotes, capitalization
- Text checking panel can be used to check text without mouse
New settings and options
- Added setting to “Use delete to revert autocorrect”
- Added setting to for expand level when open document
- Added setting to close documents when quitting
- Added new text checking panel options and descriptions
Diacritics and combining characters
- Added Control-Delete to decompose characters
- Fixed drawing to stop clipping diacritics
- Fixed crash when inserting combining characters
- Fixed backspace to match system delete/decompose behavior
Improved rich text pasteboard support
- Added support for strikethrough when copy/paste .rtf
- Changed .rtf encoding to use tab indentation instead of lists
- Fixed .rtf decoding to better support diacritical characters
Improved text editing actions
Added Control-T to transpose characters
Added yank: and yankAndSelect: and kill buffer support
Added setMark:, deleteToMark:, selectToMark:, swapWithMark:
More features and bug fixes
- Added key modifiers for opening links in tabs and windows
- Fixed view update when learning and ignoring spelling errors
- Fixed animations used when splitting and joining rows
- Fixed unindent to properly handled collapsed rows
- Fixed AppleScript api to use non-dynamic colors
Oops This link does’nt exist or is private.
Oops! That page doesn’t exist or is private.
@dddo @ludwigschubert Opps, I copied and pasted from my blog markdown, but there the urls are relative and here they needed to be absolute. I’ve fixed the link.
Confused - I copied a link from higher up in a Bike doc and pasted it, then tried to remove the “link” aspect of the copy (akin to removing the wrapping
a tags in HTML) and found I could not do that. The video shows me trying to use Remove link, and later I am trying to delete the contents of the URL field.
I could only click Remove after I had clicked Save link, and clicking Remove had no effect, also I could not change the content of URL – it was “read only” as it were.
Here’s the vid – confused, happy to share file if helpful.
It is a confusing case. The issue is that that are two kinds of links in Bike.
“Normal” rich text links, where you assign a URL to a range of text. These you can remove.
“Detected” links are found and highlighted based on the text content in your document. If the text content contains something that looks like a URL then a link is automatically created.
This second kind of link can’t be removed because it would just get added back next time link detection ran. This second kind of link can be Edited, because maybe you want to change the title to be some text that’s different from the URL.
This is a confusing case, but at the moment I don’t have a great solution in mind.
For a little more info on the implementation. When you edit a link the “Remove” button will only be enabled if there is an existing saved link… This link will show up as a
<a> link in Bike’s file format. On the other hand the remove will not show if the links is just recognized, but not saved in the document model. If you open a Bike file you will see that there are no
<a> created automatically for URLs… those recognized links are only something that Bike shows in the editor view.
Totally understand. I’m familiar with an option like that in most of the JS Markdown libraries – “linkification” or similar. Now I know it’s not “broken” or me I am 100% Ok with this model of operation – it was only disconcerting as I assumed I’d sorta broken Bike somehow : ’ ( delighted to know it’s all good
Thanks for the super-fast reply!