No the time is already as short as it is practical to make it.
On Tue, 9 Feb 2021, 05:13 Jason White, <[email protected]> wrote: > No, it works properly in master. > > I do notice that on a double click there's a slight fraction-of-a-second > delay > after a double-click before the word is highlighted, but if I triple click > there's virtually no delay between hitting that third click and the > selection > of the whole line. I assume this is tmux waiting, after two clicks, to see > if > there's going to be a third click. Any chance this wait period can be made > adjustable? > > Thank you. > -Jason > > On Tue, Feb 09, 2021 at 04:33AM +0000, Nicholas Marriott wrote: > >Does this still happen with master? > > > > > >On Tue, 9 Feb 2021, 01:49 Jason White, <[email protected]> wrote: > > > >> Hello, > >> > >> Using tmux 3.1c under macOS Catalina with latest iTerm2. I've seen an > >> number > >> of bindings that, with mouse mode enabled, allow one to double click to > >> select > >> a word and triple click to select a line. They look more or less like > what > >> I > >> have in my .tmux.conf: > >> > >> bind-key -n DoubleClick1Pane \ > >> select-pane \; \ > >> copy-mode -H \; \ > >> send-keys -MX select-word \; \ > >> run-shell "sleep .5s" \; \ > >> send-keys -X copy-pipe-and-cancel "pbcopy" > >> > >> bind-key -T copy-mode DoubleClick1Pane \ > >> select-pane \; \ > >> send-keys -MX select-word \; \ > >> run-shell "sleep .5s" \; \ > >> send-keys -X copy-pipe "pbcopy" > >> > >> bind-key -n TripleClick1Pane \ > >> select-pane \; \ > >> copy-mode -H \; \ > >> send-keys -MX select-line \; \ > >> run-shell "sleep .5s" \; \ > >> send-keys -X copy-pipe-no-cancel "pbcopy" > >> > >> bind-key -T copy-mode TripleClick1Pane \ > >> select-pane \; \ > >> send-keys -MX select-line \; \ > >> run-shell "sleep .5s" \; \ > >> send-keys -X copy-pipe "pbcopy" > >> > >> I have no issues with DoubleClick1Pane events whether in or out of copy > >> mode, > >> but the TripleClick1Pane events only trigger if I unbind the > >> DoubleClick1Pane > >> events, regardless of mode. It seems like tmux isn't waiting to see if > >> there's a third click -- it sees two clicks and declares it a > DoubleClick > >> and > >> triggers accordingly. > >> > >> I've tried the stock Terminal.app, but the behavior is the same. > >> > >> Any thoughts on what to try next? > >> > >> Thanks, > >> -Jason > >> > >> -- > >> Jason White > >> "The single biggest problem in communication is the illusion that it has > >> taken place." - George Bernard Shaw > >> > >> -- > >> 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/YCHpsXi%2B9sTG6GP3%40equinox.home.menelos.com > >> . > >> > -- > Jason White > "The single biggest problem in communication is the illusion that it has > taken place." - George Bernard Shaw > -- 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/CAEdLfcEuSF6h2PtBv%3DgQJ-78h3EER44K8fhLTOfZNT5BKR_oKA%40mail.gmail.com.
