On Feb 28, 2017, at 6:50 PM, Warren Young <war...@etr-usa.com> wrote: > > ...for those who run their terminals at > 80 columns
If you go with that, you might want to call isatty(stdout) in case fossil is being run in a pipeline, so code that tries to parse a hash out of the command gets the full length. I say “might” because it is variably evil for a command to emit one thing when connected to a terminal and another when its output is connected to a pipe, FIFO, etc. The variability has to do with how much the output changes. In this case, not much, so not very evil. For true evil, we must turn to PowerShell. :) A command that produces text can’t always be grepped because it may start emitting .NET objects when in a pipeline, which confuses Unix users transplanted to Windows. _______________________________________________ fossil-dev mailing list fossil-dev@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/fossil-dev
