5 ms·

There was a recent (a couple of weeks ago) commit that claims to rectify the long lines performance issue, for what it's worth.

• jhoechtl 4y ago
  That is really interesting. May you take the effort and identify the commit? EDIT: Nevermind, search to the rescue This might be the discussion: https://lists.gnu.org/archive/html/emacs-devel/2022-08/msg00483.html https://lists.gnu.org/archive/html/emacs-devel/2022-08/msg00... These might be the commits: https://git.savannah.gnu.org/cgit/emacs.git/commit/etc/NEWS?id=a71c05b44de74fe16691f680df34c4534992e472 https://git.savannah.gnu.org/cgit/emacs.git/commit/etc/NEWS?... https://git.savannah.gnu.org/cgit/emacs.git/commit/etc/NEWS?id=94c10c426e305037126cf75cc5cf23c9f8df4664 https://git.savannah.gnu.org/cgit/emacs.git/commit/etc/NEWS?...
  • mark_h 4y ago
    Also this one I think: https://git.savannah.gnu.org/cgit/emacs.git/commit/?id=616da8fa8efa9023f56fa731072d877e2150afbc https://git.savannah.gnu.org/cgit/emacs.git/commit/?id=616da...
    • jhoechtl 4y ago
      Just tried it out. For my personal workflow when working on overlong lines, the performance gain is HUGE! From unusable to actually decent. Not using find-file-literally and even syntax highlighting enabled.
      • mark_h 4y ago
        That's great to hear, thanks! I haven't tested it in anger yet, and I'm not going to pretend to understand the display-code changes.