Put the keyboard at the forefront of UX

[SamirHafez]

@tiensonqin as an eMacs Org guy, you'll sympathise with this.

There are a lot of situations in Logseq where using the mouse is either necessary, or easier to use compared to the keyboard. IMO, this shouldn't be the case. The fastest way to perform actions on a tool primarily dedicated to manipulating text is to ensure the user doesn't need to move their hands away from the keyboard. Here are some examples:

Date Pickers

/scheduled is one example. Currently, it opens a date picker, but why not allow the user either:

1. type /scheduled next tuesday
2. type /scheduled and then allowing the user to type the property value

Here's how Tana does it:

Templates

I can't find a way to set that tag with the keyboard, I had to click it.

Queries

Typing /query should allow me to follow up like /query (tags [[Task]]). But even if it didn't do that, today, typing /query lifts me from editing mode. Now I have to do a combination of shifts and enters to edit the query.

It's great that putting the cursor on the +Filter line gives me the opportunity to type the query, but the cursor should be there from the moment I type /query ENTER.

Tags

I can add a tag whilst typing in a node, but there are problems here too:

1. The tag dropdown only shows up if the # has no text before it. This means typing something like my new task#t won't show me tag options starting with a t. I should be able to type # anywhere in edit mode and get the option to apply a tag. What if I actually wanted to insert the # char? Then I just press ESC when the popup shows.
2. I can't remove the tag with the keyboard

Again, Tana for comparison:

Sidebar

"Open in sidebar" can't be done without clicking things. At least I couldn't find a way.

Commands

There are a lot of actions that we can take with a mouse that aren't listed as commands, and therefore cannot be triggered from the command line or an assigned shortcut.

There are more paper cuts, these are the one I found most difficult to deal with. The overall theme here seems to be this (and apologies if I'm mistaken): There's a lot of cool new stuff coming to Logseq, but the user experience is suffering because too many actions require a mouse.

[logseq-cldwalker]

Hi. Some of these sound like enhancements and have already been discussed there. We prefer to have those in the discord #alpha-db-feedback channel. I've updated the issues menu so it's clear to all users in the future

I can't find a way to set that tag with the keyboard, I had to click it.

Try Cmd-j as described in https://github.com/logseq/docs/blob/feat/db/db-version.md#property-shortcuts

Typing /query should allow me to follow up like /query (tags [[Task]])

You can achieve this workflow by first typing the query in a block and then typing /Query to execute as described in 2nd bullet point in https://github.com/logseq/docs/blob/feat/db/db-version.md#queries

[SamirHafez]

@logseq-cldwalker

Some of these sound like enhancements and have already been discussed there. We prefer to have those in the discord #alpha-db-feedback channel

Bah, I was told to put it here 🤦🏽 . Sorry.

Try Cmd-j as described in https://github.com/logseq/docs/blob/feat/db/db-version.md#property-shortcuts

Ooooooooooh 🙇🏽

You can achieve this workflow by first typing the query in a block and then typing /Query to execute as described in 2nd bullet point in https://github.com/logseq/docs/blob/feat/db/db-version.md#queries

That's also very helpful 🙇🏽