Hi there - apologies if this has been asked before, I couldn’t see it in the forum. But why when I start a new document in Bike 2 why do I have to then press ‘enter’ before typing? In Bike 1, as in all the other text editors I use (iA writer, BBEdit, Drafts, etc., not to mention TaskPaper) cmd-n brings up a new document and the cursor is there ready to start typing. Am I missing a setting here? If not, what is the thinking behind this? And I wonder if there could at least be an option to choose to open documents and have the cursor right there. At the moment I’ve configured the world’s simplest Keyboard Maestro macro to fix it, but it seems an unusual choice. Thanks.
I agree it’s a bit weird.
There was a discussion a few months back on why, but I can’t seem to find it. And I also can’t fully remember the details of the why! Ha!
I do know that in Bike’s editing model you need a row to type into. And you can also select rows and delete them. This means there’s always the possibility that a user selects-all, and then deletes. Leaving an empty document that you can’t type into, because there are no rows.
There are three ways to resolve this:
- Be “smart” and make sure that can’t happen, never delete the last row.
- Or be “smart” and when user starts typing, insert a new row.
- Or be simpler and just expect that empty state can happen
Bike chose option 3, and I want to stick with that design. It’s a little odd, but I also think it’s cleaner easier for extensions to reason about. So it should be that if you select all and delete. Then you’ll need to press enter to create a new row to type into.
But that doesn’t answer the question… why don’t I just insert a new row when creating a new document. So you’d get a cursor on new document creating. At this moment, it seems like I should do that.
I’ll add for next release, unless I somehow remember why I wasn’t doing that 
1 Like
If it helps, here’s the thread: Bike 2.0 (Preview 262) - #17 by Gorgonzola
+1 on empty row in new doc 
2 Likes