Hello everybody, we have a mini update to release 9916.
The autocomplete panels are now wider to accommodate more of the note titles. To facilitate the insertion of aliases, the wiki link panel now handles the alias separator character |. This, when the panel is displayed, generates a link to a note or a header ending with | (e.g. [[notetitle|]] ) with the caret placed before ]].
This update also fixes a couple of migration issues concerning lists and some parsing errors.
As usual, you can check the update via Bear > Check for Updates
Can’t seem to get the alias to work like how you did it in the video.
When I select the note title in the panel, it closes the wiki link with ] ].
I also tried typing [ [Partial note title and use the arrow key to select the note to link to, then I tried to press | but that gives me [ [ Partial note title|
After typing “/” i can choose some heading. But after typing"|" no header is taken over: i end up with “/|”. Am i doing something wrong or does it not work with my german keyboard like intended? The video confuses me. I only can type in alias by going back into already existing wiki link
Although US keyboard layout does not work, Norwegian keyboard layout works with / (shift 7),
but | (option 7) does NOT auto complete with Norwegian either.
Your video demo looks great, but I think we need another mini update to make it work for all international keyboard layouts.
Yeah same with Finnish/Swedish layout: [[notetitle then press / and you can pick a heading like in the video, but pressing | just ends up with [[notetitle/heading| and no wikilink is created. The keyboard shortcuts are the same as in Norwegian.
I think it was Andy Matuschak who asked for double lines. While i believe that double lines as standard are not a good idea in terms of ui, i also think that a key modifier for switching to double lines in special scenarios may be a good solution. You only see double lines while using the modifier
The wider autocomplete dialog is a real improvement; thanks. I do still find myself wishing it were wider in practice—it still feels needlessly difficult (though less so!) to discriminate my notes here.
Just riffing, in case it’s helpful: my impulse would be to make the autocomplete dialog match the editor’s line width, perhaps minus some padding. No need for double lines, I think!
Double line is something we want to avoid as much as possible, but we have other solutions in mind!
I was thinking about that, but having a huge empty bar (like for tags/emoji/languages) doesn’t looks good. I think we’ll spend some more time on that making the width dynamic depending on the content
Thanks for all the feedback, having people engaging with us during the design/develop phase really help in polishing the app!
Please check the last update (9969). / and | should now work with every keyboard layout and the autocomplete panels’ width expands more if necessary.
Also, love the dynamic width changes for the autocomplete panel. You made it feel elegant and unobtrusive.
EDIT: while testing it, I discovered something that bothers me, though. I selected a wikilink (say: [[wikilink]], and wanted to erase it and start writing a new wikilink, so I typed an opening square bracket. What I expected to happen was for the previous text to disappear in favor of a single bracket. What happened instead is that double brackets got changed to single brackets. That’s how I learned Bear had bracket autocompletion.
For the record, this is inconsistent with how all other apps do it: repeatedly pressing a bracket in other apps like iA Writer or Logseq keeps adding brackets instead of a cycle of adding/removing a single bracket. It makes adding WikiLinks easy and is more intuitive to me. Would you consider changing that behavior to be more in line with other apps?
Here another point which perhaps just me feel inconvenient: after reaching the end of title inside of the wiki link i have to escape out of the brackets either by mouse/trackpad or by hitting two times right arrow on keyboard. It feels so natural for me just to hit enter to escape out of the brackets
keyboard)
I’ve updated it to keep adding brackets, it should be working as you want in the next version.