On 26 October 2017 at 05:39, Stephen Hicks <[email protected]> wrote: > I appreciate the patch that went in a while back to add "copy-mode -e", > allowing to automatically exit copy-mode when reaching the bottom of the > buffer. But I find that this functionality is a bit of "spooky action at a > distance": the decision to exit depends not on the input the caused the > scroll-down, but instead of the input that initially scrolled up.
I'm not sure I understand your use case or your issue with the current behaviour. Is it just the "spooky action at a distance" that you object to? The current behaviour is intended to model two different ways that copy mode can be used: 1) The normal mode where you are copying data out of the scrollback buffer, searching through it, or some other explicit action. This mode requires you to take an equally explicit action to exit. 2) Scrollback mode, where you are just scrolling back through the terminal history. In this mode, you enter typically with just a PageUp or ScrollUp event, not a binding that is explicitly copy-mode. This way, exiting mirrors your entry - when you scroll back to where you started, you're no longer in copy mode. I don't understand the "spooky action at a distance" (I get that how you enter the mode defines how you can exit the mode, but that's all related and not spooky unrelated stuff, or at a distance). I can't see how your approach allows the distinction between these two use cases to be retained. Perhaps using separate key tables, but that feels like a lot of extra configuration. Can you explain why you want to change this? > > I've put together a small patch to allow opting into the auto-exit behavior > on scroll-down commands instead. Currently I've overloaded the send-keys -R > argument (which seems somewhat appropriate given that exiting copy-mode is a > sort of "reset"), but I'd also be happy to find a different way to pass the > option (either adding an additional argument to send-keys, or adding > scroll-down, etc, to the 1-arg branch so that you'd write "send-keys -X > scroll-down -e", though in that case I'm not sure what to do if the argument > is anything *other* than -e - currently it silently does nothing if a > command has the wrong (number of) arguments, which isn't great. > > Please let me know how to proceed so that this functionality can be added. > Or if you'd rather continue on a GitHub pull request, that would be great as > well. > > Thanks! > steve > > -- > 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 post to this group, send email to [email protected]. > For more options, visit 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 [email protected]. To post to this group, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
