-
-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
Inconsistent intendation behavior or use of "enter" with first list item #11854
Comments
I'm linking to a related upstream CodeMirror discussion: https://discuss.codemirror.net/t/markdown-customizing-list-tightness/9003 |
I tried reproducing the bug but it works as expected, can you help me reproduce this?
|
@rabbabansh: You probably reproduced the case 1, which is the expected behavior. So you did not start with a first item in a list with those steps? Can you do this again with the word Ant, Charlie or Earn by setting the coursor at the end of the word and then do your steps? |
Yeah similar behavior but in this example its the last item, in joplin its the first list item with this behavior. |
@Julrob199 oh right, thank you! |
Operating system
Linux
Joplin version
3.3.1
Desktop version info
Joplin 3.3.1 (prod, linux)
ID do cliente: <>
Versão Sync: 3
Versão do Perfil: 47
Keychain Suportada: Não
Revisão: da59aef
Backup: 1.4.2
Freehand Drawing: 2.15.0
Markdown Table: Sortable: 1.2.2
Menu items, Shortcuts, Toolbar icons: 1.1.0
Note Tabs: 1.4.0
Quick Links: 1.3.2
Rich Markdown: 0.15.1
Victor: 1.0.3
Current behaviour
There is a weird and inconsistent behavior of intendation. It started to behave differently since version <3.1.x
...
How to reproduce:
Case 1: Expected behaviour
Case 2: Unexpected behaviour
First I was wondering if it has something to do with the intendation. But it happens also with "Heading 2". Case 1 applies for "Fargo", "Good" or "Hola"... so where the button enter works as expected. But case 2 happens with "Ant" or "Hola" or even "Charlie"... so always when its the first item in the list.
Use this as an example (do not use code formatting, when testing it in joplin)
Expected behaviour
This behaviour affect ordered, unordered and checklist items.
Having different behaviours is really confusing. It disturbs the workflow imho. Sometimes I want to split a list and by one empty line. When I start doing it with the first list item I always have to clean up the left over list item, which looks then like this:
Expected behaviour would be:
So case 1 and 3 are expected, case 2 not.
Logs
No response
The text was updated successfully, but these errors were encountered: