Hello!

When text line in list is too long and part of it is moved on the next line, list number is placed on the last line. When I use <br>, list number is placed on the first line of multiline text.

Demo is below:

Demo text:

1. [ ] task 1
2. [ ] task 2 task 2 task 2

OS Version (操作系统): macOS

VNote Version (Help - About VNote - Version: )(VNote版本): 2.8.2

Symptoms (表现): when using the Advanced Search what is the difference between space-separated keywords and &&? According to the VNote documentation they both mean AND.

In fact, from what I find a space gap acts as an OR criterion, not as an AND criterion.
Please explain.

How to Repro (如何复现):

Our Getting Started page is nice but there are a variety of ways to install jrnl on various platforms, and sometimes there are "gotchas," common problems, or different methods that would be nice to address (perhaps in a more detailed installation page), such as:

• using pip vs pipx
• Windows installation issues
  • avoiding path issues
  • Windows Python vs W

Problem

1. I am unable to drag a note from trash to all notes. I feels like this should be allowed.
2. Also I think it's a little strange that 'All notes' doesn't actually mean 'all' (does not contain trashed notes and scratchpad).

Solution

1. Enable a note to be restored from trash by dragging it into 'All notes'
2. Perhaps 'All notes' should be renamed to 'Notes'?

Notes
I'

Describe your feature request
When you apply formatting it should be toggleable/undoable through an immediate second application

Additional context
This would need selected text to remain after formatting is applied

As requested in glushchenko/fsnotes#854 (comment)

Describe the bug
Text cut in the last line in no tags available message.

Context
Galaxy Nexus API 24

How to reproduce
Steps to reproduce the behavior:

1. Have no Tags.
2. Click on the Tags icon

Expected behavior
Text should not cut at the end.

Screenshots
If applicable, add screenshots to help explain your problem.
<img src="https://user-images.githubusercon

It should be great to have the "multiple files tag menu" when selecting multiples files and clicking the tag menu item on the contextual menu.

Right now, this show the tag window only for the file under the mouse when clicking mouse right button.

I use the default MacOS keyboard shortcut CMD+Backspace (clear text until start of line) to clear the search field. Problem: this also summons a dialog asking me to confirm if I want to delete the currently shown note.

When an input field has keyboard focus, I don't want such a dialog and I expect the OS's default behavior as described above.

As desired, this dialog is not shown when the no

It would be great if the data of notes.sqlite could be merged in case of a sync conflict (if it was changed on two computers).

A complete merge would be very difficult. Maybe starting on more easy parts first.

• Checking if conflicted database file differs at all
• Delete conflicted copies of the note folder database notes.sqlite immediately if tags and tag assignments are not d

⚠️主要Bug：Github中的MarkDown上下标等与一般通用性MD语法规范略有一点不同

上下标：

参考：GitHub中的上标MD规范 ^{GitHubMD语法}

⚠️标记：

• 标记 同样不适用于Github ==[5]==

⚠️添加链接

一般习惯这样的：

• 选中一段文字 --> 添加链接 --> 粘贴链接地址 --> 完成

• Bug：点击 添加链接 --> 填入

Current behavior

There is no button to see all notes from all storages combined. Currently this button only exists per storage.

Expected behavior

Old app:

Also add to https://github.com/zsh-users/zsh-completions

Currently we can disable the YAML Header for new notes, and for existing notes it will only be updated if it already exists. It would be good to have the reverse option as well - that the yaml header is only added for new notes, but for notes without it we don't add it.

Ideally, we should also provide the user some kind of feedback about why they cannot set the title, and an option for the YAML

Having clickable links in the node text would be very useful, so nodes can refer to external documentations, issues in an issue tracker, etc.

I don't think this need a rich text editor (I value the simplicity of the tool), just turning things that parse as links into clickable links would work fine.

This could be done as part of #82 (markdown support).

Another benefit of this option would