Bug Sur and Textedit

[macdos]

With Bug Sur 11.4 comes – of course – brand new bugs to Textedit (and presumably also other apps).

Now when pasting something into a plain text document, it will sometimes display the line above as two or more lines.

As before, selecting with cmd-shift+arrow up is buggy, but now it also sometimes scrolls the text in the document…

This on top of at least ten other Textedit bugs that were introduced with Bug Sur, and that were never fixed.

Textedit is a very simple app that has always worked like a charm, but which has been completely broken with Bug Sur. What's happening at Apple?

 

[DWHH1]

TextEdit is almost completely un-usable under Big Sur. I have complained in these forums about this problem before - as have many others - and Apple just isn't responding with a fix.

The problem?? Open a text file - doesn't have to be that big, a 124MB one is more than plenty to trigger the behaviour. Then try and scroll or move to somewhere perhaps near to the end of the file. Spinning Beach ball and the App is locked up permanently.

This behaviour did NOT arise prior to Big Sur even when opening text files of as big as 7GB with TextEdit.

I can only assume the underlying code was re-written for Apple Silicon and the lack of a fix perhaps reveals a limitation in Apple Silicon because, as I said, it WAS NOT a problem before when Intel was the Apple engine and, as macdos points out, it then worked like a charm.

 

[Slartibart]

The problem?? Open a text file - doesn't have to be that big, a 124MB one is more than plenty to trigger the behaviour.

This behaviour did NOT arise prior to Big Sur even when opening text files of as big as 7GB with TextEdit.

In no relation to the bug/problem, just out of curiosity: what are these text files? Why not use BBEdit, Alpha or any other more suited editor for such file sizes? Actually sed might be a much better option than Textedit, right?

 

[Ritsuka]

TextEdit in Big Sur uses the new TextKit2 framework, which will be publicly available in Monterey. I guess it was a bit buggy in Big Sur, and probably will always be in this macOS version.