On Mar 26, 2017 7:13 AM, "Christophe Gouiran" <bechris13...@gmail.com> wrote:
Hi all, First of all many thanks for all your feedback. I come back to you with an implemented solution. After many thinking, for me not all commands need to send their outputs to a pager. Only ones which may output a big amount of lines in a bunch. Therefore, I selected only some of them to be candidate for a pager: {snipped list of commands} I appreciate what you're trying to do here, but what you've done (based on your description) is create a maintenance nightmare (or headache at minimum). Your implementation will forever need to be tweaked when new commands are added or existing commands changed in some way that changes their amount of output, perhaps based on some extra parameter. DRH suggested that it should be based on any output, which would avoid the worry about how fossil changes over time. I'm coming around to the position that, given the ease of typing "| pager" when desired, or defining an alias or using a wrapper of sorts, this feature may be a mistake. I've never once wished that fossil had done this for me, though I could be in the minority.
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users