Currently, when you search with F6 the current note changes to whatever is the top search result, which will usually not be the note you were editing. Could this be changed so that the current note doesn’t change until you actually click one of the search results, or perform some other explicit action?
User story — I’m editing a note, and I want to add links to several existing notes. I want to keep the current note in the editor but make one or more searches so that I can bring up those existing notes in the note list and drag them into the note I’m editing.
Currently, I have to collect those links one at a time, each time going back to the page I am editing, then repeating the search (because going back clears the search, and going forward doesn’t restore it).
3 Likes
I have similar behaviour. Not sure if it's quite editing a note found by search bar and chancel search switches to another note - bug? · Issue #3904 · laurent22/joplin · GitHub
Process: On desktop v3.0.2, search using the search box above the notes list, click on a result, edit a word within that note.
Result: Said note disappears from both editor and search results.
And possibly related:
Process: In Android 3.0.2, open a note, click the name if its current notebook at the top of the screen, select a different notebook to move it to.
Result: Note closes and you're taken back to the notebook that the note was moved from.
Actually this is getting quite annoying. On Windows, if I open All Notes at the left, click on one to edit and edit a single character of its content, the note disappears from the editor and is replaced by e.g. the most-recently edited other note. The only fix I've found is to manually navigate at the left to the notebook that the note to edit is actually stored in (rather than searching). I guess All Notes might have underlying code similar to F6 search?
I had that issue as well but found a plugin called "DDDot" that allows me to drag notes to a shortcut panel. This then allows me to click back and forth between different notes without having to locate them again. Doesn't solve the issue but works well for me as a workaround.
1 Like