You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am converting a series of notes that make heavy use of indentation for organization. For example, I might have a note in the following format:
Topic A
Point 1 about Topic A
Point 2 about Topic A
Topic B
Point 1 about Topic B
Point 1 about Topic B Point 1
Point 2 about Topic B
When I convert these files, I see the indents in edit mode, but not in reading mode, so it's clear that they are present in the .enex file, and preserved in the converted file.
I now understand that Markdown doesn't really support indentation as such, but also understand I can use something like $\qquad$ to create indent-like formatting.
Can Yarle take a configuration option to change any indents to a sequence of my choosing, similar to how problematic filename characters are converted to "_"?
Alternatively, can Yarle auto-convert indented text to unordered lists?
The text was updated successfully, but these errors were encountered:
I am converting a series of notes that make heavy use of indentation for organization. For example, I might have a note in the following format:
Topic A
Point 1 about Topic A
Point 2 about Topic A
Topic B
Point 1 about Topic B
Point 1 about Topic B Point 1
Point 2 about Topic B
When I convert these files, I see the indents in edit mode, but not in reading mode, so it's clear that they are present in the .enex file, and preserved in the converted file.
I now understand that Markdown doesn't really support indentation as such, but also understand I can use something like$\qquad$ to create indent-like formatting.
Can Yarle take a configuration option to change any indents to a sequence of my choosing, similar to how problematic filename characters are converted to "_"?
Alternatively, can Yarle auto-convert indented text to unordered lists?
The text was updated successfully, but these errors were encountered: