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

Unexpected lists formatting override on document save #390

Closed
ovk opened this issue Oct 27, 2019 · 1 comment
Closed

Unexpected lists formatting override on document save #390

ovk opened this issue Oct 27, 2019 · 1 comment
Labels
bug Something isn't working

Comments

@ovk
Copy link

ovk commented Oct 27, 2019

Describe the bug

Markdown list formatting is changed unexpectedly on document save.

To Reproduce

  1. Create markdown file with the following content (not using Nextcloud Text editor):
- One
- Two
  + Three
    * Four
  1. Open this file in the Nextcloud Text editor. The formatting is correct and list properly indented.
  2. Add new item to the list in the Nextcloud Text editor.
  3. Open the file outside of the Nextcloud Text editor. Now list have been changed to:
* One

* Two

  * Three

    * Four

    * Five

Notice two unexpected (and possibly unwanted) changes to the list formatting:

  1. Every list item prefix has been replaced with * character.
  2. List items are now separated with an empty line.

Expected behavior

The original formatting is preserved and not altered for existing list items.

Details

While this bug report may at first seem like nitpicking, the described behaviour can be really annoying in some cases:

  1. In my case, markdown files live outside of the Nextcloud and are mounted into Nextcloud via external folders. Thus the files are also viewed/edited using other tools, and for some of them having all lists formatting changed may be undesirable.
  2. If markdown files are under version control (popular for personal notetaking) then having unexpected changes to list formatting on document save makes VCS history not very useful.
@jancborchardt
Copy link
Member

Closing in favor of #593 where we have more info

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants