Hi, For a while, I've played with some ideas on unifying the choose-* and list-* commands in some way. Granted, neither type of command can be considered a set of each other as not all list-* commands have choose-* command equivalents [1] and hence it's not as simple as switching over the list-* commands to have a flag to enter choose-mode or vice-versa. This can only make sense if both commands have each other's equivalence.
So there's a few options here: * Bring all list-* commands in line with having choose-* counterparts (such as a "choose-panes" command (which might be an extension of choose-tree?), but then not every command warrants a choose-* equivalent -- such as list-keys. Or: * Deprecate list-* commands in favour of some flag to choose-* commands. Or: * If a choose-* command is called without an interactive tmux instance, emulate what list-* would have done. Unifying these concepts to me, however we might choose to do it makes sense to me, as the logic between both choose-* and list-* is the same in each case, and what differs is whether they're interactive or not. Thoughts welcome. :) Kindly, -- Thomas Adam [1] It could be argued is a bug... ------------------------------------------------------------------------------ Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev _______________________________________________ tmux-users mailing list tmux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tmux-users
