unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Tino Calancha <tino.calancha@gmail.com>
Cc: 39154@debbugs.gnu.org, Juri Linkov <juri@linkov.net>
Subject: bug#39154: 27.0.60; Use character history in zap-up-to-char
Date: Fri, 25 Sep 2020 13:28:37 +0200	[thread overview]
Message-ID: <87blhuqemy.fsf@gnus.org> (raw)
In-Reply-To: <87lfpyp9gk.fsf@calancha-pc.dy.bbexcite.jp> (Tino Calancha's message of "Thu, 23 Jan 2020 14:51:23 +0100")

Tino Calancha <tino.calancha@gmail.com> writes:

> We have discussed two topics in this report, thus I am proposing the
> following two commits:
>
> I) Adjust interactive specificaion for `zap-up-to-char':
>
> commit fe77bb9c2793fd7856c514f41e7a2ce4ccbc4f18
> Author: Tino Calancha <tino.calancha@gmail.com>
> Date:   Thu Jan 23 14:42:29 2020 +0100
>
>     Use character history in zap-up-to-char

I've now applied this patch to Emacs 28; it seems "obviously correct" to
do the same as zap-to-char here.

> II) Add new command `isearch-yank-to-char'.
>   - It is desirable to add a keybinding for it as well.  Tentatively, I
>   have used C-M-p in this patch; please, suggest me the one that fit better.

There was pushback here on both the key binding and the utility of the
command.  I have no opinion on the latter; all those keybindings in
isearch are kinda obscure to me, but they have lots of fans, I've
noticed.

So I'm closing this bug report; if this is something that should be
explored further, opening a new bug report for this would be welcome.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





      parent reply	other threads:[~2020-09-25 11:28 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-16 18:49 bug#39154: 27.0.60; Use character history in zap-up-to-char Tino Calancha
2020-01-16 18:56 ` Tino Calancha
     [not found] ` <877e1rexzi.fsf@mail.linkov.net>
2020-01-18 14:37   ` Tino Calancha
2020-01-20  0:24     ` Juri Linkov
2020-01-23 13:51       ` Tino Calancha
2020-01-23 18:16         ` Eli Zaretskii
2020-01-25 19:43           ` Tino Calancha
2020-01-28 23:49         ` Juri Linkov
2020-02-02 13:54           ` Tino Calancha
2020-02-05  7:21           ` Tino Calancha
2020-02-05 15:22             ` Drew Adams
2020-02-05 19:46               ` Tino Calancha
2020-02-05 21:10                 ` Drew Adams
2020-02-05 21:56             ` Juri Linkov
2020-09-25 11:28         ` Lars Ingebrigtsen [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=87blhuqemy.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=39154@debbugs.gnu.org \
    --cc=juri@linkov.net \
    --cc=tino.calancha@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).