all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tino Calancha <tino.calancha@gmail.com>
To: 39154@debbugs.gnu.org
Cc: juri linkov <juri@linkov.net>
Subject: bug#39154: 27.0.60; Use character history in zap-up-to-char
Date: Thu, 16 Jan 2020 19:49:12 +0100	[thread overview]
Message-ID: <87blr31bkn.fsf@calancha-pc.dy.bbexcite.jp> (raw)

X-Debbugs-Cc: Juri Linkov <juri@linkov.net>
Severity: wishlist

While zapping I saw in the news about recent `zap-to-char' changes...
( I mean Emacs news, I don't watch TV! :-| )

We might want to extend that to cover `zap-up-to-char' as well; as many others,
I weardly use the former, but I often use the latter.

--8<-----------------------------cut here---------------start------------->8---
commit 5436b891aadaf649ae6ab3e204b74c76bfa4e6f8
Author: Tino Calancha <tino.calancha@gmail.com>
Date:   Thu Jan 16 19:30:03 2020 +0100

    Use character history in zap-up-to-char
    
    Extend commit
    'Add CHARS arg to read-char-from-minibuffer compatible with read-char-choice.'
    (04ab67470706f1c66bdf08e4078ea3dffd79b41e)
    to `zap-up-to-char'.
    
    * lisp/misc.el (lisp/misc.el): Use same interactive specification
    as in `zap-to-char'.
    * etc/NEWS (): Mention zap-up-to-char as well.

diff --git a/etc/NEWS b/etc/NEWS
index d6eb5d9e66..08e8907a2c 100644
--- a/etc/NEWS
+++ b/etc/NEWS
@@ -603,10 +603,10 @@ navigation and editing of large files.
 
 +++
 ** 'zap-to-char' now uses the history of characters you used to zap to.
-'zap-to-char' uses the new 'read-char-from-minibuffer' function to allow
-navigating through the history of characters that have been input.
-This is mostly useful for characters that have complex input methods
-where inputting the character again may involve many keystrokes.
+'zap-to-char' and 'zap-up-to-char' use the new 'read-char-from-minibuffer'
+function to allow navigating through the history of characters that
+have been input.  This is mostly useful for characters that have complex
+input methods where inputting the character again may involve many keystrokes.
 
 +++
 ** 'save-some-buffers' now has a new action in the prompt: 'C-f' will
diff --git a/lisp/misc.el b/lisp/misc.el
index 05244a6ea2..8b6b7a7e0d 100644
--- a/lisp/misc.el
+++ b/lisp/misc.el
@@ -69,7 +69,9 @@ zap-up-to-char
 Case is ignored if `case-fold-search' is non-nil in the current buffer.
 Goes backward if ARG is negative; error if CHAR not found.
 Ignores CHAR at point."
-  (interactive "p\ncZap up to char: ")
+  (interactive (list (prefix-numeric-value current-prefix-arg)
+		     (read-char-from-minibuffer "Zap to char: "
+						nil 'read-char-history)))
   (let ((direction (if (>= arg 0) 1 -1)))
     (kill-region (point)
 		 (progn
--8<-----------------------------cut here---------------end--------------->8---


In GNU Emacs 27.0.60 (build 52, x86_64-pc-linux-gnu, GTK+ Version 3.24.5)
 of 2020-01-16 built on calancha-pc.dy.bbexcite.jp
Repository revision: 52080b5778cbe535c331fa14539aecd88f2be0a0
Repository branch: emacs-27
Windowing system distributor 'The X.Org Foundation', version 11.0.12004000
System Description: Debian GNU/Linux 10 (buster)





             reply	other threads:[~2020-01-16 18:49 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-16 18:49 Tino Calancha [this message]
2020-01-16 18:56 ` bug#39154: 27.0.60; Use character history in zap-up-to-char 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

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87blr31bkn.fsf@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.