From: Michael Heerdegen <michael_heerdegen@web.de>
To: "Garreau\, Alexandre" <galex-713@galex-713.eu>
Cc: help-gnu-emacs@gnu.org
Subject: Re: el-search usage (doc, strings, pcase, etc.)
Date: Sun, 28 Oct 2018 02:11:26 +0100 [thread overview]
Message-ID: <87tvl6kh8h.fsf@web.de> (raw)
In-Reply-To: <875zxnkkgw.fsf@web.de> (Michael Heerdegen's message of "Sun, 28 Oct 2018 02:01:35 +0200")
Michael Heerdegen <michael_heerdegen@web.de> writes:
> Another reason was that el-search started as an experiment, and I just
> didn't know how and to what it would develop. Now I think it would be
> worth to get some ideas into isearch but I also still want to experiment
> with el-search's interface and see how it develops. I still get new
> ideas for what could be convenient and like that it's easy for me to try
> things out.
BTW, I first thought writing the basic features for efficient matching
would be complicated, and the user interface would be easy going. It
turned out the opposite was true: Implementing the matching routines was
fun, but maintaining the user interface is hard work. Mainly because
already the specification of the interface is really, much more than I
had expected. I guess it's similar for isearch.
Michael.
next prev parent reply other threads:[~2018-10-28 1:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-27 14:48 el-search usage (doc, strings, pcase, etc.) Garreau, Alexandre
2018-10-27 15:43 ` Michael Heerdegen
2018-10-27 16:37 ` Garreau, Alexandre
2018-10-27 20:19 ` Michael Heerdegen
2018-10-27 22:30 ` Garreau, Alexandre
2018-10-28 0:01 ` Michael Heerdegen
2018-10-28 1:11 ` Michael Heerdegen [this message]
2018-10-28 1:55 ` Garreau, Alexandre
2018-10-28 22:26 ` Michael Heerdegen
2018-10-28 22:59 ` Garreau, Alexandre
2018-10-28 23:39 ` Michael Heerdegen
2018-10-27 15:55 ` Michael Heerdegen
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=87tvl6kh8h.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=galex-713@galex-713.eu \
--cc=help-gnu-emacs@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.
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).