[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: Thu, 04 Aug 2022 10:10:18 +0300

> From: Po Lu <luangruo@yahoo.com>
> Cc: Stefan Monnier <monnier@iro.umontreal.ca>,  acm@muc.de,
>   gregory@heytings.org,  mattiase@acm.org,  philipk@posteo.net,
>   silent2600@gmail.com,  emacs-devel@gnu.org
> Date: Thu, 04 Aug 2022 14:19:20 +0800
> Eli Zaretskii <eliz@gnu.org> writes:
> > What will we do with the "rare" exceptions, such as CC Mode, for
> > example?
> Fix them, individually?

Fine by me.  People are encouraged to work on that ASAP.  But we'd
like to have a reasonably performant Emacs 29 when editing long lines
without waiting for that pipe dream to come true.  If and when it does
come true, we can reset the long-line-threshold to nil by default,
even if it happens before Emacs 29 is released.

> > And what will we do with (I expect) the much larger group which
> > becomes broken when font-lock stops widening, and their assumptions
> > about being always able to access any buffer position become false?
> We don't have make font lock avoid widening -- what I was proposing was
> to ensure that font lock, CC Mode, and any other exceptions that might
> come up only widen to the "locked" restriction, without changing the
> behavior of narrow-to-region and friends.

We don't know how to do that, as was already explained and
demonstrated here.  Modes do what they want, and in some cases we have
hard time even convincing the mode developers that they should try to
avoid doing that.

reply via email to

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