unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Tino Calancha <tino.calancha@gmail.com>
To: Juri Linkov <juri@linkov.net>
Cc: 39154@debbugs.gnu.org, Tino Calancha <tino.calancha@gmail.com>
Subject: bug#39154: 27.0.60; Use character history in zap-up-to-char
Date: Sat, 18 Jan 2020 15:37:42 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.21.2001181530490.29021@calancha-pc.dy.bbexcite.jp> (raw)
In-Reply-To: <877e1rexzi.fsf@mail.linkov.net>



On Fri, 17 Jan 2020, Juri Linkov wrote:

> BTW, why we added only isearch-yank-until-char corresponding to zap-to-char,
> but not an isearch command corresponding to zap-up-to-char?
I wasn't aware about that function; I like it! It saves typing.

After playing with it, I see that above function corresponds to 
`zap-up-to-char' (i.e., it doesn't add CHAR to the search string).

The following changes might be worth:
- A rename, or an alias, of above function to `isearch-yank-up-to-char'
- Add similar funtion `iseach-yank-to-char' (i.e. one that inserts CHAR
   in the seach string).





  parent reply	other threads:[~2020-01-18 14:37 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 [this message]
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

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=alpine.DEB.2.21.2001181530490.29021@calancha-pc.dy.bbexcite.jp \
    --to=tino.calancha@gmail.com \
    --cc=39154@debbugs.gnu.org \
    --cc=juri@linkov.net \
    /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).