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
Describe your feature request
In bullet lists, text that overflows the line length configured in Preferences > Line width and wraps to the next line is aligned flush with the left margin instead of aligning with the first line of the bullet item.
I've highlighted the problem areas here:
This breaks the visual flow and can make it difficult for me to differentiate list items. Especially in longer lists, the margin-aligned second lines appear to be new list items rather than continuations of the current item. As illustrated in the examples, it is even more "jarring" in todo lists.
I would prefer an option to align n+1 lines of a list item with the first line of that item, like so:
Additional context
This issue is most problematic on macOS as the line width is longer.
I realize that this is a very picky and personal request, and it may be difficult to implement. It is a "nice to have" feature :)
The text was updated successfully, but these errors were encountered:
Describe your feature request
In bullet lists, text that overflows the line length configured in Preferences > Line width and wraps to the next line is aligned flush with the left margin instead of aligning with the first line of the bullet item.
I've highlighted the problem areas here:
This breaks the visual flow and can make it difficult for me to differentiate list items. Especially in longer lists, the margin-aligned second lines appear to be new list items rather than continuations of the current item. As illustrated in the examples, it is even more "jarring" in todo lists.
I would prefer an option to align n+1 lines of a list item with the first line of that item, like so:
Additional context
This issue is most problematic on macOS as the line width is longer.
I realize that this is a very picky and personal request, and it may be difficult to implement. It is a "nice to have" feature :)
The text was updated successfully, but these errors were encountered: