emacs-devel
[Top][All Lists]
Advanced

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

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


From: Po Lu
Subject: Re: emacs master + org Wrong type argument: number-or-marker-p
Date: Wed, 03 Aug 2022 09:21:00 +0800
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.91 (gnu/linux)

Alan Mackenzie <acm@muc.de> writes:

> A rigorous program MUST now test these.  This is such a horrible
> artifact that it won't get done most of the time.

[...]

> There are no safety fences of any sort.  The meaning of a program using
> w and n-t-r is no longer determinate.

[...]

> That's a month in which the discussion was open only to somebody who
> reads every post in the bug list, such as yourself, or who came upon the
> discussion by chance.  Others, such as me, were unaware of it.  It looks
> like the decision to change the byte code interpreter has already been
> taken, and I had no chance to participate in that process.
>
> Is it really right that fundamental changes to Emacs get discussed only
> on the bug list, or in secret[*] on emacs-devel?  [*]I.e. when the
> subject line is not explicit.
>
> Anyhow, I wanted to protest and I have done so.  The arguments between
> the two of us here about widen and n-t-r are clearly not going anywhere,
> so I don't intend to continue them.  I won't feel put out if you don't
> want to answer them.

I agree with Alan.

Is there really a slowdown associated with allowing code to widen
outside the bounds specified by redisplay long-line "optimizations"?  Or
are we speculating about a hypothetical problem that doesn't exist
again?


reply via email to

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