From: Drew Adams <drew.adams@oracle.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>, Juri Linkov <juri@jurta.org>
Cc: 14714@debbugs.gnu.org
Subject: bug#14714: 24.3.50; `isearch-filter-predicate(s)'
Date: Wed, 26 Jun 2013 07:19:34 -0700 (PDT) [thread overview]
Message-ID: <571658f2-b490-4705-ac56-a332535d0eb7@default> (raw)
In-Reply-To: <jwvbo6t81gf.fsf-monnier+emacs@gnu.org>
> > Can you please say why you think so?
> > Do you imagine it is obvious? It is not, to me at least.
>
> Please don't hijack this discussion.
I am not hijacking anything. I am the one who filed this bug report.
And I proposed a simple fix for it from the outset - a minor correction of what Juri had already coded and along the lines of what has been done in the past.
You proposed a different fix. Fine. But you gave no reason - nothing about any problems with the more usual approach or any advantages of your new approach.
I asked about that. I am interested in learning the advantages of your novel approach of (IIUC) advising a single hook function as a substitute for allowing for a sequence of hook functions.
I did not say that your solution is not a good one. I assume the contrary, in fact. I am asking to understand why you think it is a better one. That's all.
Understanding this can help with other code as well, presumably. Is there a reason why you do not want to share your understanding?
next prev parent reply other threads:[~2013-06-26 14:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-25 17:26 bug#14714: 24.3.50; `isearch-filter-predicate(s)' Drew Adams
2013-06-25 18:46 ` Stefan Monnier
2013-06-25 20:18 ` Drew Adams
2013-06-26 0:20 ` Stefan Monnier
2013-06-26 2:34 ` Drew Adams
2013-06-26 13:08 ` Stefan Monnier
2013-06-26 14:19 ` Drew Adams [this message]
2013-06-26 14:36 ` Stefan Monnier
2013-06-26 21:31 ` Juri Linkov
2013-06-27 1:32 ` Stefan Monnier
2013-06-27 23:39 ` Juri Linkov
2013-07-04 0:26 ` Stefan Monnier
2013-08-04 7:45 ` Stefan Monnier
2013-08-05 18:07 ` Stefan Monnier
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=571658f2-b490-4705-ac56-a332535d0eb7@default \
--to=drew.adams@oracle.com \
--cc=14714@debbugs.gnu.org \
--cc=juri@jurta.org \
--cc=monnier@iro.umontreal.ca \
/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).