mirror of
https://github.com/BoostIO/BoostNote-App.git
synced 2026-04-26 21:05:55 +03:00
[GH-ISSUE #929] Global search can't be activated by keyboard OR menu #435
Labels
No labels
android 🤖
assigned to core 🦹
bug 🐛
documentation 📚
documentation 📚
duplicate 🚫
external issue 🔼
external issue 🔼
feature request 🌟
funded on issuehunt 💵
help wanted 🆘
improvement request 🔨
improvement request 🔨
ios 🍎
mobile 📱
needs investigation 🔬
needs more info ℹ️
needs specs 📐
plugin idea 🔌
plugin idea 🔌
poll 🗳️
pull-request
question ❓
rewarded on issuehunt 🎁
security issue 🔑
won’t fix ❌
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/BoostNote-App#435
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @myicq on GitHub (Apr 29, 2021).
Original GitHub issue: https://github.com/BoostIO/BoostNote-App/issues/929
Originally assigned to: @Komediruzecki on GitHub.
Current behavior
In version 0.16.1 for Windows, the keyboard binding for global search (lupe icon in left-hand bar) is no longer working. This means that only way to activate search is using a mouse.
A note taking application should be possible to use with keyboard only.
Nothing happens on CTRL-P or other key bindings.
Expected behavior
CTRL-P was previously used to activate global search.
Steps to reproduce
Try keyboard binding.
Even the MENU "search (CTRL-P)" does nothing.
Environment
Windows 10 64bit, da-DK, Boostnote 0.16.1.
Desktop/Web
Mobile
@Komediruzecki commented on GitHub (Apr 29, 2021):
Hi, myicq,
A known issue, a fix is already in place, currently, we are working on providing great local search as well, and a keymap feature so you can assign your custom keymaps for global and local search.
The fix and these features will probably be included in the next release, I hope next week.
@Komediruzecki commented on GitHub (May 28, 2021):
Hi,
This is fixed in v0.17.1.
Please update the application and it should work.