Unexpected Sequential Numbering in Ordered Lists Without Separators

Support
1

When creating an ordered list, the numbering works as expected initially. However, if I add a new ordered list item after a line break (without any separator), the numbering doesn’t reset and instead continues from the previous list. For example, typing 1. after a previous ordered list results in it being rendered as 4. instead of 1. . This only happens when there’s no content (like a horizontal rule or text) separating the lists. If a separator is present, the numbering resets correctly.

Steps to Reproduce:

  1. Create an ordered list, such as:

    1. 111
2. 222
3. 333

  2. Add a line break to make the content look like this:

    1. 111
2. 222
3. 333

<cursor here>

  3. At the cursor position, type 1. to start a new ordered list item.

    • Observed Behavior: It renders as 4. (continuing the previous list).
    • Expected Behavior: It should render as 1. (starting a new list).

  4. Now, try this scenario with a separator:

    1. 111
2. 222
3. 333

--- or anything else

<cursor here>

  5. At the cursor position, type 1. .

    • Observed Behavior: It correctly renders as 1. (new list starts).

It seems like Bear treats the new list as a continuation of the previous one unless explicitly separated. Is this intended behavior, or is there a setting I can adjust to reset the numbering automatically after a line break? Any help would be appreciated!

2

Hello again!

I don’t think this is a Bear bug.
It’s probably how Markdown works.

If you want to start a new list, you need to add something in between – like --- or just a line of text.
Without that, Markdown continues the old list.

It’s the same in Obsidian and other Markdown apps too. :blush:

3

I have tested in Typora and vscode. It seems that a new list will be created.

Anyway, thanks for the guidance.

4

Yes, we follow the CommonMark standard, and this behavior is by design.