Autocorrect stripping delimiter in new release

Completed

Scott Fi

October 25, 2019 01:23

Like the subject says. In Version 1.0.0 (38) nvULTRA is stripping macOS autocorrect delimiters.

**CORRECTION.** I just realized all nvULTRA is doing is moving the caret back before the delimiter. The delimiter is still there. Still a bug though.

To replicate:

1. Type something that will trigger a macOS autocorrect and then type `-`
2. The autocorrect will happen and the caret will be moved before the dash

0

• 

  Fletcher Penney

  October 25, 2019 20:03

  Duplicate of https://multimarkdown.zendesk.com/hc/en-us/community/posts/360035411853-cursor-position-changes-after-punctuation

  0
• 

  Scott Fi

  October 25, 2019 20:23 Edited

  Interesting. Indeed it is a duplicate (not sure how i missed that in the search).

  No matter, one interesting thing to note is I’ve been using nvULTRA for all my basic daily text editing for about two months (I think) and haven’t come across this bug until two days ago (or whenever beta 38 dropped). I haven’t changed any pertinent os settings in that time and haven’t messed with nvULTRA settings recently either. I do not see this issue in multimarkdown composer, sublime, TextEdit, TheArchive, or any other text editor on my system.

  So for the past few releases I haven’t seen this issue in nvULTRA, but on (38) I am. Make of that what you will :)

  0

Please sign in to leave a comment.