help-gnu-emacs
[Top][All Lists]
Advanced

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

Re: cl-loop - do you understand it well?


From: Akib Azmain Turja
Subject: Re: cl-loop - do you understand it well?
Date: Mon, 12 Dec 2022 12:03:46 +0600

Just yet another spam.  ;b

Stefan Monnier via Users list for the GNU Emacs text editor
<help-gnu-emacs@gnu.org> writes:

[...]

>> Is it something new?
>
> "new" is relative.  It depends on what you have set (current-time).
>
>> How this will be useful?
>
> It will be useful for example to correct past mistakes.

Then I must quote etc/future-bug:

--8<---------------cut here---------------start------------->8---
Date: Tue, 23 Feb 2199 21:03:50 -0600
From: Karl Fogel <kfogel@floss.cyclic.com>
To: bug-gnu-emacs@prep.ai.mit.edu
Subject: M-x search-backward-in-time broken...
X-Windows: you'll envy the dead.

In GNU Emacs 51.70.4 (i9986-unknown-linux-gnu, X toolkit) of Sat Feb  20 2199 
on floss
configured using `configure  --with-x-toolkit=yes'

        The `search-backward-in-time' function appears to be broken in
Emacs 51.70.

        Unfortunately, I can never seem to start the debugger early
enough to catch the error as it happens.  However I have traced the
problem through source by eye, and it looks like `time-forward' can't
handle negative arguments anymore.  This is consistent with other
symptoms: for example, `undo' (which since 51.25 has worked by passing
a negative arg to `time-forward') is also broken.  However, `do' still
works -- it seems that `time-forward' continues to handle positive
arguments just fine.

        No one here-and-now can figure out how to fix the problem,
because the code for `time-forward' is so hairy.  We're using M-x
report-future-emacs-bug to request that you folks include more
comments when you write it (sometime in 2198 as I recall).

        Thanks!

-Karl Fogel   <kfogel@red-bean.com>


P.S. You'll be pleased to know that since (time-forward N) still works
     for N >= 0, we've used it to pre-emptively update configure.ac.
     Emacs now configures and builds on every platform that will ever
     be made.  It wasn't easy, but at least that's one problem out of
     the way for good.  If you'd like the patch, just ask.

--8<---------------cut here---------------end--------------->8---

I really wonder that English won't change it next 200 years.  :)
But the language model in my head broke while writing about something
that'll happen in time.  >D

The only problem is that observing the current rapid development speed,
I can say that we'll get Emacs 51 well before 2050, and it's unlikely to
ever have version 51.70.4 (we'll have 51.0.50, 51.1, 51.2, 51.3 and then
we'll jump to 52.0.50).  :)

And I'm really sad that we'll still have Intel processors, X Toolkit and
domain names in 22nd century.  :/

Oh and yes, I want the configure.ac patch.  How can I contact Karl Fogel
who is 177 years in future?  ;)

-- 
Akib Azmain Turja, GPG key: 70018CE5819F17A3BBA666AFE74F0EFA922AE7F5
Fediverse: akib@hostux.social
Codeberg: akib
emailselfdefense.fsf.org | "Nothing can be secure without encryption."

Attachment: signature.asc
Description: PGP signature


reply via email to

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