this action would mirror the action that happens when you are typing a word [[word… - which by default when you hit enter simply LINKS to an existing page, which is much more common, then the second option is to go to that page.
this is inverted when using the search command, where creating a new page with what you’ve typed is on top when you hit enter, and go to the page is second. this creates a bunch of friction when using search - it’s WAY more common to want to navigate to a page, therefor just type a few letters, hit enter, and go, like you do everywhere else, e.g. spotlight on a mac.
this is my biggest single issue with logseq, and seems like a no brainer.
to summarize - command k search box should default when you’re typing to NAVIGATE, NTO to create a new page, like it does when you type a page inline using [[.
see this example - obviously much more likely to want to go to the first search result vs create a new page for a half word!
I was thinking the same thing the other day. I don’t know how many times I’ve done command+K, type something, hit enter and end up with a new page instead of grabbing the first search result.
So the change would be that Logseq ⌘k has no “New page:” or “New whiteboard:” at the top of the search (these are infuriatingly in the way) and always opens a file unless you use a mod on your enter. So ⇧+enter would create a page and perhaps ⇧⌃+enter a new whiteboard with your search term.
These shortcuts should be customisable to fit everyone’s muscle memory requirements.
Having the create option second to the search results would turn up in several cursor-down actions when you have lots of pages and narrow down your search. Where would you put the „create“ option in the dialog?
Ah yea, that’s a great idea. This would also neatly solve the issue of “create whiteboard” as a 2nd option in that menu, which is likely too rarely used to take up the space there.
