From: "Jérôme Marant" <jerome.marant@free.fr>
Subject: Re: lazy-lock is obsolete?
Date: Sat, 02 Apr 2005 19:41:02 +0200 [thread overview]
Message-ID: <87u0mpvzyp.fsf@marant.org> (raw)
In-Reply-To: <E1DH4IN-00048R-J0@fencepost.gnu.org> (Richard Stallman's message of "Thu, 31 Mar 2005 13:21:31 -0500")
Richard Stallman <rms@gnu.org> writes:
> I recalled that I switched from jit to lazy because it seemed to me
> that lazy was faster (with 21.3)
>
> Could you try them again now, and let's see if lazy-lock is really
> faster now? If it is, it would be nice to know why.
I can't really see any difference. I don't object for it to be obsoleted.
Cheers,
--
Jérôme Marant
prev parent reply other threads:[~2005-04-02 17:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-29 18:34 lazy-lock is obsolete? Stefan Monnier
2005-03-29 20:16 ` Jérôme Marant
2005-03-29 22:26 ` Jason Rumney
2005-03-30 6:45 ` Jérôme Marant
2005-03-31 18:21 ` Richard Stallman
2005-04-02 17:41 ` Jérôme Marant [this message]
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=87u0mpvzyp.fsf@marant.org \
--to=jerome.marant@free.fr \
/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).