[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: emacs master + org Wrong type argument: number-or-marker-p

From: Eli Zaretskii
Subject: Re: emacs master + org Wrong type argument: number-or-marker-p
Date: Wed, 03 Aug 2022 15:34:27 +0300

> From: Po Lu <luangruo@yahoo.com>
> Cc: acm@muc.de,  gregory@heytings.org,  mattiase@acm.org,
>   philipk@posteo.net,  silent2600@gmail.com,  emacs-devel@gnu.org
> Date: Wed, 03 Aug 2022 20:07:16 +0800
> Eli Zaretskii <eliz@gnu.org> writes:
> > How would that work in practice?  Font-locking code uses functions and
> > regexps provided by the major modes, so it cannot by itself prevent
> > widening.  Many major modes want their fontification to start from the
> > beginning of the line, which can be very far in a buffer with long
> > lines; and quite a few major modes use code that widens to BOB.
> >
> > What can font-lock do to prevent that?
> But not every piece of code widens and scans from BOB to EOL.

Many do.

> The idea is to change all problematic code in Emacs to only widen to
> limits placed by redisplay, instead of changing widen and
> narrow-to-region themselves.

There's no reason to "widen to limits placed by redisplay", they should
just not change the existing restriction.

And when (and if!) your idea is implemented for the relevant modes in
Emacs, we can flip the default value of long-line-threshold to nil.
So dazzle me!

reply via email to

[Prev in Thread] Current Thread [Next in Thread]