-
-
Notifications
You must be signed in to change notification settings - Fork 136
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
in-note search #106
Comments
Yeah, definitely. Simply a search icon in the top right next to the »more« icon just as in the main view would be good. :) Then it’s search-as-you-type and the first result is directly focused. And the results placement could be highlighted in the scrollbar area (like Chrome does for example) to have a sense of placement. |
Or even inside the menu if you want a simple aesthetic, I don't mind. I don't use Chrome (or anything from Google) but I think I get what you say; the top bar became something like this:
Right? |
Yup, that as well. |
What is the status of this feature request? |
It has low priority for me but Pull Requests are welcome of course :-) I provide 20,-€ for a working PR if someone is willing to take this. |
@stefan-niedermann how many pancakes is that? :D |
(i will hate myself for this, but:) |
I will give you one chance to edit your answer :D
…On Tue, 15 May 2018 at 09:37, Niedermann IT-Dienstleistungen < ***@***.***> wrote:
(i will hate myself for this, but:) how many can you eat at the conf?
:laugh:
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#106 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAAWsvbNmiqjmGZ0k3Sc1MxUymsl6YLFks5tyoXPgaJpZM4H8gUV>
.
|
Your turn :) |
Replace with wine and done! :D |
Awaiting your PR ;-) |
Would be adding a searcher inside the note (for long notes) a good idea?
Eg: I have a huge Markdown note for activism with links and descriptions.
This would be very useful but I also understand that might be not a very used feature for other people.
Note: commented on #19
The text was updated successfully, but these errors were encountered: