From: Ulrich Mueller <ulm@gentoo.org>
To: emacs-pretest-bug@gnu.org
Subject: bug#4583: 23.1.50; bug in etc/future-bug ;-)
Date: Tue, 29 Sep 2009 11:29:18 +0200 [thread overview]
Message-ID: <19137.54126.181976.908701@a1i15.kph.uni-mainz.de> (raw)
etc/future-bug was "fixed" at some time, probably to shift the dates
into the future again. The joke loses much of its subtlety by this.
The patch below restores Karl Fogel's original version, adding a note
about when it first appeared. The original is also hilarious for its
implicit assumptions about the Emacs 22 release date. ;-)
(Besides, the weekdays in 2199 are wrong. 23 Feb 2199 will be a
Saturday, and 20 Feb 2199 a Wednesday.)
Ulrich
--- emacs-orig/etc/future-bug 2007-02-28 05:12:39.000000000 +0100
+++ emacs/etc/future-bug 2009-09-29 11:11:12.000000000 +0200
@@ -1,20 +1,22 @@
-Date: Tue, 23 Feb 2199 21:03:50 -0600
+[This first appeared with Emacs 19.31 in 1996.]
+
+Date: Tue, 23 Feb 1999 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
+In GNU Emacs 22.70.4 (i586-unknown-linuxoldld, X toolkit) of Sat Feb 20 1999 on floss
configured using `configure --with-x-toolkit=yes'
The `search-backward-in-time' function appears to be broken in
-Emacs 51.70.
+Emacs 22.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
+symptoms: for example, `undo' (which since 22.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.
@@ -22,7 +24,7 @@
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).
+comments when you write it (sometime in 1998 as I recall).
Thanks!
reply other threads:[~2009-09-29 9:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=19137.54126.181976.908701@a1i15.kph.uni-mainz.de \
--to=ulm@gentoo.org \
--cc=4583@emacsbugs.donarmstrong.com \
--cc=emacs-pretest-bug@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.