Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

(Feature request) Option to disable the ability to create new child note with @ #2428

Closed
1 task done
FoodFighters opened this issue Dec 9, 2021 · 3 comments
Closed
1 task done

Comments

@FoodFighters
Copy link

Preflight Checklist

  • I have searched the issue tracker for a feature request that matches the one I want to file, without success.

Describe feature

Right now, the 1st option after you try to link a note with @ or ctrl + L, is create a new child note. This results in an extra key press (the down button is far away enough to require you to move your arm) every time you want to link to an existing note. The option to turn off the feature of creating a new note with @ can save hundreds of key presses, not to mention the time and energy of having to move to said key. I know this might not sound like much, but it makes for a drastically less efficient workflow for those that don't need to create a new linked note with @.

Additional Information

No response

@zadam
Copy link
Owner

zadam commented Dec 9, 2021

I understand the problem, but creating config options is usually not a great solution for such problems.

One idea is that the feature stays where it is, but the second item in the list will be auto-selected, thus in your case you don't need to press down and if you want to create a note, you press up.

I'm now trying to figure out if this is possible with the autocomplete component.

@FoodFighters
Copy link
Author

Oh, yeah, that is better. I think a combination of the two ideas can be better for everyone involved though, where you can have the option to toggle which of the two items will be auto-selected, because I'm sure there are those that prefer the way it is now.

@meichthys
Copy link
Collaborator

Trilium has entered maintenance mode. Future enhancements will be addressed in TrilumNext: TriliumNext#139

@meichthys meichthys closed this as not planned Won't fix, can't repro, duplicate, stale May 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants