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

[Request] In-Note Search #861

Open
pshelly opened this issue Feb 6, 2020 · 3 comments
Open

[Request] In-Note Search #861

pshelly opened this issue Feb 6, 2020 · 3 comments

Comments

@pshelly
Copy link

@pshelly pshelly commented Feb 6, 2020

Global search is really good in SN but in-note search is lacking. I have some workflows that heavily depend on the in-note functionality. I tried using global search but found it very annoying because of the following:

  • I am using Plus Editor
  • Highlight all behavior (out of focus)
  • No next match behavior (dedicated button)
  • No dedicated shortcut

Something like firefox's would be ideal. Everything accessible through graphical interaction and through shortcuts.

image

I find the found one on Minimal markdown editor is good but missing the buttons.

Idealy every editor would support it.

@mobitar mobitar transferred this issue from standardnotes/desktop Feb 6, 2020
@mobitar

This comment has been minimized.

Copy link
Member

@mobitar mobitar commented Feb 6, 2020

This is very hard to do given our multi-editor approach. However, most likely the stance we will take in the future is that we will built out these features for 3 editors only: plain, 1 markdown, and 1 rich text. Which those would be is TBD. This is definitely something we want to build, and we realize it's important, but it's going to take time.

@bschlagel

This comment has been minimized.

Copy link

@bschlagel bschlagel commented Feb 12, 2020

Strong agree, this would be extremely useful. Even just for plaintext + one markdown editor for example, that would be awesome :)

Based on my experience I'd go so far as to say that if it's too hard to get this right for all editors, that's a very compelling reason to focus resources on a smaller # of editors, and perhaps even deprecate some of them going forward. Personally I would much much rather have one really great native-feeling markdown editor (long term, perhaps a custom base implementation that's easier for devs to extend / override) than the current situation of four different ones based on third party packages that all feel different and incomplete in random ways.

@adambyrtek

This comment has been minimized.

Copy link

@adambyrtek adambyrtek commented Feb 16, 2020

Agreed, as a new user I found the number of Markdown editors really confusing. In the end I settled on Markdown Pro and uninstalled all the others. I would much rather see one editor that integrates well and is officially supported for each use case (plain-text, HTML, Markdown, tasks etc.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants
You can’t perform that action at this time.