I noticed the pull request for this was recently closed ( https://github.com/tmux/tmux/pull/293), because of lack of progress, and active changes to the original code.
Are there any plans to add this functionality as part of the new changes? I tried the original pull request version, and it seemed to work fine, and would be a great addition to copy mode. Thanks. -FR On Mon, May 2, 2016 at 5:52 AM, Nicholas Marriott < nicholas.marri...@gmail.com> wrote: > Neither of these patches are ready to go in as-is, they are too big and > the style is not right. I tidied up one of them and it will probably go > in eventually, after that the second patch will need to be adjusted to > apply on top of it and probably split into two. > > > > On Mon, May 02, 2016 at 05:40:17AM -0700, Felix Rosencrantz wrote: > > Any problems with the patches?** I would really like to see > incremental > > search added to Tmux copy mode.** It's not clear what the current > status > > is from the 2 pull requests. > > Thanks > > -FR. > > On Mon, Feb 1, 2016 at 5:27 AM, **ukasz Pi**tkowski > > <[1]lukaspiatkow...@gmail.com> wrote: > > > > I created the pull request: [2]https://github.com/tmux/ > tmux/pull/293 > > lets continue discussion there. > > > On Jan 29, 2016, at 4:27 PM, **ukasz Pi**tkowski > > <[3]lukaspiatkow...@gmail.com> wrote: > > > > > > I am glad to hear that tmux uses github, it will simplify this. I > will > > send the patches asap > > > > > > On 29 Jan 2016 4:25 pm, "Suraj N. Kurapati" <[4]sun...@riseup.net > > > > wrote: > > > On Fri, 29 Jan 2016 10:38:18 +0000, **ukasz Pi**tkowski wrote: > > > > There were 3 changes that I have send, the first one was only a > > > > refectory, the second and third was actually adding some logic: > > > > incremental search and highlighting of all words matching the > > search. > > > > > > **ukasz, could you please send all three patches to this mailing > list > > as > > > attachments so that others can help with or continue this > patchwork? > > > > > > In addition, what version of tmux were your patches made on top > of? > > > > > > Finally, if you could fork tmux on GitHub and start a pull > request, it > > > would help eliminate this back and forth exchange of patches along > > with > > > the ambiguity of what version of the tmux codebase they > correspond to. > > > > > > Thanks for your consideration. > > > > -- > > 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 [5]tmux-users+unsubscr...@googlegroups.com. > > To post to this group, send an email to [6] > tmux-users@googlegroups.com. > > For more options, visit [7]https://groups.google.com/d/optout. > > > > References > > > > Visible links > > 1. mailto:lukaspiatkow...@gmail.com > > 2. https://github.com/tmux/tmux/pull/293 > > 3. mailto:lukaspiatkow...@gmail.com > > 4. mailto:sun...@riseup.net > > 5. mailto:tmux-users%2bunsubscr...@googlegroups.com > > 6. mailto:tmux-users@googlegroups.com > > 7. https://groups.google.com/d/optout > -- 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 tmux-users+unsubscr...@googlegroups.com. To post to this group, send an email to tmux-users@googlegroups.com. For more options, visit https://groups.google.com/d/optout.