From: Drew Adams <drew.adams@oracle.com>
To: Juri Linkov <juri@linkov.net>
Cc: 15839@debbugs.gnu.org
Subject: bug#15839: 24.3.50; `isearch-allow-scroll': be able to scroll point off screen temporarily
Date: Mon, 26 Nov 2018 16:49:21 -0800 (PST) [thread overview]
Message-ID: <8af20443-841d-4211-99ae-269e042a9a33@default> (raw)
In-Reply-To: <877egzmmyk.fsf@mail.linkov.net>
> > Sorry, but I don't really understand.
> >
> > There are several parts to this bug report. I don't know
> > what "the first part" refers to.
>
> It refers to your original request cited below:
Thanks for clarifying what you meant.
But those points 1,2,... in the bug report are not
independent. They are meant to make a logical argument
for what's being requested. They are all of a piece.
They describe different, but related, aspects of the
inconvenience that the requested feature would
alleviate.
I don't want to customize one variable to be able to
scroll farther, and another variable to have what's
shown by that scrolling have lazy-highlighting
(especially if the latter requires lazy-highlighting
the entire buffer, rather than just what I see when
scrolling).
I want to be able to use `isearch-allow-scroll' to
let me scroll as far as I want, and see search hits
lazy-highlighted in what parts of the buffer I
scroll to.
> > 1. Non-nil `isearch-allow-scroll' lets you use a scroll command
> > (e.g. `C-v') without exiting Isearch. Unfortunately, this is coupled
> > with the hard-coded behavior that you cannot scroll far enough in
> > either direction that point would be moved off screen.
> >
> > That restriction is general for Emacs, and it generally makes sense.
> > It does not necessarily make sense during Isearch, however. Why?
> >
> > Because the search position is one thing, and it is not lost. What
> > you might want to look at temporarily is another thing.
> >
> > It's a bit like using `C-SPC' in a buffer, scrolling up a couple of
> > screenfuls to look at something, and then using `C-u C-SPC' to
> > return. But in Isearch there is no need for `C-SPC' or `C-u C-SPC':
> > the search position is recorded. Search resumes from that same
> > position, no matter how far away one might have scrolled.
>
> This is implemented now with an option `nil' of the customizable
> variable `search-exit-option'. It lets you use a scroll command
> (e.g. `C-v') without exiting Isearch, so you can scroll far enough
> in either direction that point would be moved off screen.
>
> > 2. What's more, the lazy highlighting of search hits is even more
> > limited currently. When you scroll to the current limit, there can
> > be lots of search hits that are not highlighted.
> >
> > One of the reasons for scrolling is to see what search hits lie
> > beyond the currently shown text. This is already partly defeated,
> > in that even when you scroll some of the hits are not highlighted.
> > This seems more like a bug, but if the enhancement of #1 is done
> > then it should (it needs to) take care of #2 as well: Whatever
> > text is shown should have all of its search hits highlighted with
> > lazy highlighting.
>
> This is implemented now with the customizable variable
> `lazy-highlight-buffer'.
I do appreciate your letting me know what's newly
available; thanks. And thanks for making those
improvements. But no, I don't think we have what
I requested, and I don't think this bug (enhancement
request) should be closed.
next prev parent reply other threads:[~2018-11-27 0:49 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-08 23:02 bug#15839: 24.3.50; `isearch-allow-scroll': be able to scroll point off screen temporarily Drew Adams
2013-11-09 0:57 ` Juri Linkov
2013-11-09 3:09 ` Drew Adams
2013-11-10 13:46 ` Stefan Monnier
2013-11-10 16:52 ` Drew Adams
2013-11-11 19:08 ` Drew Adams
2018-11-24 22:45 ` Juri Linkov
2018-11-25 3:14 ` Drew Adams
2018-11-25 20:15 ` Juri Linkov
2018-11-26 0:16 ` Drew Adams
2018-11-26 23:35 ` Juri Linkov
2018-11-27 0:49 ` Drew Adams [this message]
2018-11-28 0:35 ` Juri Linkov
2018-11-28 15:15 ` Drew Adams
2018-11-28 23:01 ` Juri Linkov
2018-11-29 3:36 ` Drew Adams
2018-11-29 22:23 ` Juri Linkov
2018-11-30 0:27 ` Drew Adams
2018-11-30 7:28 ` Eli Zaretskii
[not found] ` <<83lg5bc9d6.fsf@gnu.org>
2018-11-30 15:33 ` Drew Adams
2018-12-04 0:29 ` Juri Linkov
2018-12-04 14:46 ` Drew Adams
2018-12-04 20:46 ` Drew Adams
2018-12-04 21:38 ` Juri Linkov
2018-12-05 0:32 ` Drew Adams
2018-12-05 23:44 ` Juri Linkov
2018-12-06 1:20 ` Drew Adams
2018-12-05 12:59 ` Michael Heerdegen
2018-12-05 23:49 ` Juri Linkov
2018-12-06 12:15 ` Michael Heerdegen
2018-12-06 23:03 ` Juri Linkov
2018-12-07 12:42 ` Michael Heerdegen
2018-12-08 23:38 ` Juri Linkov
2018-12-09 1:13 ` Michael Heerdegen
2018-12-10 0:21 ` Juri Linkov
2018-12-10 0:58 ` Michael Heerdegen
2018-12-11 0:37 ` Juri Linkov
2018-12-11 18:22 ` Michael Heerdegen
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=8af20443-841d-4211-99ae-269e042a9a33@default \
--to=drew.adams@oracle.com \
--cc=15839@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).