unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@linkov.net>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 37417@debbugs.gnu.org
Subject: bug#37417: 26.3; [PATCH] Isearch yank text at point improvements
Date: Tue, 11 Aug 2020 02:45:19 +0300	[thread overview]
Message-ID: <87k0y6kqfo.fsf@mail.linkov.net> (raw)
In-Reply-To: <878sem93pv.fsf@gnus.org> (Lars Ingebrigtsen's message of "Mon, 10 Aug 2020 12:48:12 +0200")

>> Actually there are several diverse features mingled in the same patch.
>> Do you think all of them might be useful to add to isearch.el?
>> I doubt that many users might want to use them.
>
> OK, so your objection wasn't the lack of the use of the seq library, but
> that the patch implements functionality you don't think is useful?

Actually I expressed this opinion in context of my own situation that
is similar to this feature request - some time ago I wrote a patch
for isearch.el that implements a new feature of displaying numeric hints
on each visible lazy-isearch match.  But then my doubt was that it will
impact the size of isearch.el that is already one of the biggest files
in the Emacs repository.  Then I rewrote the patch using the seq library
that helped to squeeze the patch down to a couple dozen of lines,
but still I doubt the usefulness of my implemented feature.
This is why I decided to release it as a separate package.
So this is what I suggest to do with features that are not in high demand,
or are stil experimental, or are too big to fit into the existing packages.





  reply	other threads:[~2020-08-10 23:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-16  0:59 bug#37417: 26.3; [PATCH] Isearch yank text at point improvements Drew Adams
2019-11-19 16:44 ` Drew Adams
2019-11-19 23:13   ` Juri Linkov
2020-08-09 19:00     ` Lars Ingebrigtsen
2020-08-09 23:28       ` Juri Linkov
2020-08-10 10:48         ` Lars Ingebrigtsen
2020-08-10 23:45           ` Juri Linkov [this message]
2020-08-11 11:07             ` Lars Ingebrigtsen
2020-08-18 16:13               ` Lars Ingebrigtsen

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=87k0y6kqfo.fsf@mail.linkov.net \
    --to=juri@linkov.net \
    --cc=37417@debbugs.gnu.org \
    --cc=larsi@gnus.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).