unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Third <alan@idiocy.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Keith David Bershatsky <esq@lawlist.com>, 15667@debbugs.gnu.org
Subject: bug#15667: 24.3.50; ns-win.el -- keymap assignments for isearch-repeat-backward/forward.
Date: Thu, 21 Jan 2021 21:47:04 +0000	[thread overview]
Message-ID: <YAn2WIjp5J6jKb5e@breton.holly.idiocy.org> (raw)
In-Reply-To: <87a6t45nx1.fsf@gnus.org>

On Wed, Jan 20, 2021 at 03:42:50AM +0100, Lars Ingebrigtsen wrote:
> Keith David Bershatsky <esq@lawlist.com> writes:
> 
> > The global-map key assignments within ns-win.el for
> > isearch-repeat-backward and isearch-repeat-forward are insufficient to
> > achieve the behavior contemplated by the source code of isearch.el.
> > Specifically, the isearch-mode terminates immediately after invoking
> > the repeat functions and the sticky highlight of searches found does
> > not automatically cleanup.  Invoking these repeat functions should
> > keep isearch-mode active, and then sticky highlight should
> > automatically clean up when exiting the isearch (e.g., by pressing the
> > return key after the search).  The problem is corrected by the
> > following keymap assignments, which mirrors the usage within the
> > source code of isearch.el
> >
> > (define-key global-map [?\s-f] 'isearch-forward)
> > (define-key esc-map [?\s-f] 'isearch-forward-regexp)
> > (define-key minibuffer-local-isearch-map [?\s-f] 'isearch-forward-exit-minibuffer)
> > (define-key isearch-mode-map [?\s-f] 'isearch-repeat-forward)
> >
> > (define-key global-map [?\s-F] 'isearch-backward)
> > (define-key esc-map [?\s-F] 'isearch-backward-regexp)
> > (define-key minibuffer-local-isearch-map [?\s-F] 'isearch-reverse-exit-minibuffer)
> > (define-key isearch-mode-map [?\s-F] 'isearch-repeat-backward)
> 
> (I'm going through old bug reports that unfortunately got no response at
> the time.)
> 
> I don't really use the Emacs on Macos much, but perhaps Alan has an
> opinion here?  Added to the CCs.

I don't ever really use these macOS shortcuts, TBH. I've generally
followed the rule that if it's replicating standard behaviour and it
doesn't interfere with something else then it may as well go in.
-- 
Alan Third





  reply	other threads:[~2021-01-21 21:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-21  0:02 bug#15667: 24.3.50; ns-win.el -- keymap assignments for isearch-repeat-backward/forward Keith David Bershatsky
2021-01-20  2:42 ` Lars Ingebrigtsen
2021-01-21 21:47   ` Alan Third [this message]
2021-01-22 18:19     ` 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=YAn2WIjp5J6jKb5e@breton.holly.idiocy.org \
    --to=alan@idiocy.org \
    --cc=15667@debbugs.gnu.org \
    --cc=esq@lawlist.com \
    --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).