-
Notifications
You must be signed in to change notification settings - Fork 82
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
FR: Consistent List Markers dropdown #325
Comments
@codicem-ex-cinere , thanks for request. This is a partial duplicate of #32 which covers this rule as well. The rules are slowly being added, but this one is definitely one I look forward to having added as well. |
It would be a rule to let you specify which list marker you would like. I think it should not be difficult to implement, but it will take me some time to take a look and make sure it works correctly. |
Awesome, thanks for the acknowledgement, looking forward to its implementation when you have time! |
+1. Consistent list markers can also solve a pain point of mine as follows: Before: * item 1
- item 2 After: * item 1
- item 2 Expected: * item 1
* item 2 Or: - item 1
- item 2 I can imagine people using different list markers to separate lists, although I always add a brief description between lists to separate them. |
This has been added to master. Please let us know if there are any issues with this on master or in the next release. Thanks for putting in the request and putting in the feature request! |
Currently the existing option "Convert Bullet List Markers: Converts common bullet list marker symbols to markdown list markers." covers some of this but there is no option to insure that list markers are optionally all consistent.
My case, a large portion of my imported notes designate list with * (asterisk), Obsidian created lists are - (dash) designated, my preference.
Solution: Adding a dropdown option adjacent to the existing "Convert Bullet List Markers" to select either "markdown", "-" or "*", would solve this. Alternatively a child line with dropdown below current toggle could be used.
PS. Thanks for the awesome plug-in!
The text was updated successfully, but these errors were encountered: