<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto">Both are system, macOS, limitations for QuickLook. <div><br></div><div>For the second point, I believe, and I’m sure someone here will correct me, the images and videos that are supported formats (that is handled natively by macOS, don’t seems to have this issue. If the image or video format requires/relies on external app’s quicklook abilities then those will exhibit the same behavior.<div><br><div><div style="direction: inherit;">Best,</div><div style="direction: inherit;">Farhan</div></div><div><br>On Mar 25, 2018, at 4:08 PM, Christian Rosentreter <<a href="mailto:karibu@gmx.net">karibu@gmx.net</a>> wrote:<br><br></div><blockquote type="cite"><div><span>* It cuts off files at a certain amount of lines. This wouldn't be so bad by itself, but there</span><br><span> is zero visual indication that the displayed text is cut off (something like a special coloured</span><br><span> ellipsis symbol at the end, or something)</span><br><span></span><br><span>* if the system is under load (say something else, e.g. a raytracing application, is using 100%</span><br><span> CPU) I only get the spinning indicator in the QL window and it never manages to actual display</span><br><span> the text. It is as the TextMate QL generator runs with such low priority it doesn't get a share</span><br><span> of CPU by the OS. Other file types (images, even videos) don't seem to share the same problem.</span></div></blockquote></div></div></body></html>