Thanks! So say I start a / or Ctrl-S search with the regular expression "a..d", to pick a concrete example. If the text has multiple matches such as "axxd", "ayzd", they will all be highlighted. Then if the user presses n, incremental search runs with the first exact match, in this case "axxd". So in this case all "axxd" will be highlighted and "ayzd" will not. Basically incremental will run with the first match encountered using that as the search string (not regexp). Does that make sense?
On Wed, Nov 20, 2019 at 1:01 PM Nicholas Marriott < [email protected]> wrote: > I think search-forward/backward should change to use regexps but > incremental should not. > > > On Wed, 20 Nov 2019, 20:59 Anindya Mukherjee, <[email protected]> wrote: > >> Following up, is it desirable to add a new command to do regexp search >> and leave the old commands as they are? This would mean >> window_copy_regexp_search_... variants of some of the existing functions >> and associated UI hookup. >> >> I was able to fix the line wrapped search issue mentioned above, still >> doing character wise comparison, of course. Wondering if it deserves a >> separate commit to the existing search infrastructure? >> >> Thanks! >> >> On Tue, Nov 12, 2019 at 9:29 AM Anindya Mukherjee <[email protected]> >> wrote: >> >>> Yes my thoughts exactly :D >>> >>> On Tue, Nov 12, 2019 at 8:50 AM Nicholas Marriott < >>> [email protected]> wrote: >>> >>>> If you are adding regex search it would be a perfect opportunity to >>>> fix that also :-). >>>> >>>> On Tue, 12 Nov 2019 at 16:27, Anindya Mukherjee <[email protected]> >>>> wrote: >>>> > >>>> > Thanks for clarifying! >>>> >>> -- You received this message because you are subscribed to the Google Groups "tmux-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web, visit https://groups.google.com/d/msgid/tmux-users/CAN%2Bi5iM_5a8tzdbo%3D3PLF%3DT%3D5LBq_yqiFjSveOpNLWXbj-yf_g%40mail.gmail.com.
