Quoting martin f krafft ([EMAIL PROTECTED]): > This is totally backwards. Unix tools (other than man) don't use > pagers under any other circumstances than when the user told the > shell to connect a pager to stdout.
"Other than man" is pretty broad. That includes "git <foo> --help". Why is git allowed to use a pager here and ldapvi --help is not, when both print documentation that is longer than a page of output? Git also uses a pager in other situations, for example "git --log" and "git --diff". Off the top of my head, I cannot recall examples other than git, but I certainly find it user-friendly and do not really see the point of, say, "tar --help" printing 249 lines without a pager. As a user, you can either pipe through a pager if the program does not do that automatically, or you can pipe through cat to avoid the pager for programs that default to using one. So for both implementations, users can force the other output style if they want, reducing this issue to the question of getting the default right. Recent ldapvi versions print more than a page of output for --help, so sending it to a pager seems like the right default to me. It's not a bug, it's a feature. Feel free to disagree, of course, but this is how it's going to stay in upstream. d. PS Note that this applies only to the explicit argument --help. If an error message used a pager, in situations the user cannot foresee, it would be a bug. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
