From: Chong Yidong <cyd@stupidchicken.com>
To: Dani Moncayo <dmoncayo@gmail.com>
Cc: 7470@debbugs.gnu.org
Subject: bug#7470: 24.0.50; Word Isearch lazy highlighting
Date: Sat, 04 Dec 2010 20:16:21 -0500 [thread overview]
Message-ID: <871v5xj9y2.fsf@stupidchicken.com> (raw)
In-Reply-To: <AANLkTimpfovaj-HXSxyuY3Q=V58uDM92TOfTG=cnt=40@mail.gmail.com> (Dani Moncayo's message of "Wed, 24 Nov 2010 08:49:45 +0100")
Dani Moncayo <dmoncayo@gmail.com> writes:
> I understand and agree with your reasoning, and I think would be good
> to include that idea in the section of the manual that I quoted
> before. The way it is worded now seems a bit misleading/incomplete to
> me.
I've changed the manual text to reflect this. Thanks.
prev parent reply other threads:[~2010-12-05 1:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-23 20:29 bug#7470: 24.0.50; Word Isearch lazy highlighting Dani Moncayo
2010-11-24 1:43 ` Juri Linkov
2010-11-24 7:49 ` Dani Moncayo
2010-12-05 1:16 ` Chong Yidong [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=871v5xj9y2.fsf@stupidchicken.com \
--to=cyd@stupidchicken.com \
--cc=7470@debbugs.gnu.org \
--cc=dmoncayo@gmail.com \
/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).