[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: How the long-lines "optimisation" breaks font locking.
From: |
Ihor Radchenko |
Subject: |
Re: How the long-lines "optimisation" breaks font locking. |
Date: |
Fri, 05 Aug 2022 09:23:40 +0800 |
Gregory Heytings <gregory@heytings.org> writes:
>> No matter what criterion one deems "workable", there will be some size
>> of buffer, or line, which renders Emacs "unworkable".
>>
>
> Wrong. You can now edit files with 1 GB or 5 GB on a single line almost
> fine. The limit is now the amount of memory on your computer. I keep
> investigating to see if it's possible to overcome that limit. Stay tuned!
Mmm... https://elpa.gnu.org/packages/vlf.html ?
- How the long-lines "optimisation" breaks font locking., Alan Mackenzie, 2022/08/03
- Re: How the long-lines "optimisation" breaks font locking., Lars Ingebrigtsen, 2022/08/03
- Re: How the long-lines "optimisation" breaks font locking., Alan Mackenzie, 2022/08/05
- Re: How the long-lines "optimisation" breaks font locking., Eli Zaretskii, 2022/08/05
- Re: How the long-lines "optimisation" breaks font locking., Dmitry Gutov, 2022/08/05
- Re: How the long-lines "optimisation" breaks font locking., Eli Zaretskii, 2022/08/05
- Re: How the long-lines "optimisation" breaks font locking., Dmitry Gutov, 2022/08/05
- Re: How the long-lines "optimisation" breaks font locking., Eli Zaretskii, 2022/08/05
- Re: How the long-lines "optimisation" breaks font locking., Dmitry Gutov, 2022/08/05
- Re: How the long-lines "optimisation" breaks font locking., Eli Zaretskii, 2022/08/06
- Re: How the long-lines "optimisation" breaks font locking., Dmitry Gutov, 2022/08/06