From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: jit-lock.el
Date: Thu, 01 Jul 2004 13:14:07 -0400 [thread overview]
Message-ID: <E1Bg58R-0000kt-Hz@fencepost.gnu.org> (raw)
In-Reply-To: <m1pt7h87h7.fsf-monnier+emacs@gnu.org> (message from Stefan on 30 Jun 2004 10:08:34 -0400)
I have just put it in my growing list of "bugs to investigate".
I'm still trying to catch up from my 3-weeks trip.
You didn't fix bugs during your trip?
next prev parent reply other threads:[~2004-07-01 17:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-25 23:57 jit-lock.el Richard Stallman
2004-06-30 14:08 ` jit-lock.el Stefan
2004-07-01 17:14 ` Richard Stallman [this message]
2004-07-01 17:51 ` jit-lock.el Stefan
2004-07-01 20:59 ` jit-lock.el David Kastrup
2004-10-10 5:32 ` jit-lock.el Stefan
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1Bg58R-0000kt-Hz@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).