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
Maybe this is by design, though I don't expect it to be; however, the norm as far as I have observed with all other markdown / markup editors is that the automatic wrapping behavior is contextual in nature.
Explanation:
(Note that wherever "|" appears below represents the location of the caret)
Scenario
Automatic Wrap Expected
Opening character inserted at beginning of a new line:
1 foo() 2 [|
YES: closing bracket inserted automatically
Opening character inserted after some text but at the end of a line:
1 foo(| 2
YES: closing parenthesis inserted automatically
Opening character inserted before some non-whitespace characters:
1 `|foo 2
NO: closing backtick is NOT inserted automatically
Note
In all cases, the type of symbol (backtick, parenthesis, bracket) does not affect the behavior. What matters is the position of the caret and whether there exists non-whitespace characters immediately after it.
Conversely, in MarkEdit, I notice that the third scenario above does not hold true. Even when the caret is positioned immediately preceding non-whitespace characters, inserting the backtick (`) still results in a closing backtick being inserted, e.g.
1 ``|foo 2
This tends to interrupt a typical workflow forcing the user to constantly backtrack and delete superfluous / unintended characters. Hopefully, this makes sense, as I feel I could have done a better job articulating the issue.
The text was updated successfully, but these errors were encountered:
After further testing, I observed some inconsistent behaviors. Let me know if your findings align with those described in this discussion on the CodeMirror forum.
Maybe this is by design, though I don't expect it to be; however, the norm as far as I have observed with all other markdown / markup editors is that the automatic wrapping behavior is contextual in nature.
Explanation:
(Note that wherever "
|
" appears below represents the location of the caret)Opening character inserted at beginning of a new line:
Opening character inserted after some text but at the end of a line:
Opening character inserted before some non-whitespace characters:
Note
In all cases, the type of symbol (backtick, parenthesis, bracket) does not affect the behavior. What matters is the position of the caret and whether there exists non-whitespace characters immediately after it.
Conversely, in MarkEdit, I notice that the third scenario above does not hold true. Even when the caret is positioned immediately preceding non-whitespace characters, inserting the backtick (
`
) still results in a closing backtick being inserted, e.g.This tends to interrupt a typical workflow forcing the user to constantly backtrack and delete superfluous / unintended characters. Hopefully, this makes sense, as I feel I could have done a better job articulating the issue.
The text was updated successfully, but these errors were encountered: