Conversation
|
@Rarst: could you give this a spin? |
|
Works with
|
|
That means that You should be able to see the error message by piping it explicitly (using the master branch): |
|
No issue with explicitly piping it to Something probably goes bonkers in |
|
Looked closer at it. Actually it tries to run doesn't trigger.
|
|
|
|
Error code meaning might be same, but I am not getting that error code, it's |
|
Ok, thanks. I guess I'll just have to fire up my old Windows laptop one of these days and figure it out. |
|
It seems detecting if a command is available is not so straigthforward: http://superuser.com/questions/175466/determine-if-command-is-recognized-in-a-batch-file/175831#175831 Also, I found that the |
* Windows throws an unexpected exit status when trying to use `less` * more doesn't have an '-r' flag
|
Decided to skip paging on Windows, since I don't have a Windows machine handy to test either way. Manual piping should work, though: |
(should fix unrelated build errors)
Follow-up to #548.
When using
man, the output was paged. You could achieve the same effect, without this patch, by running this:less bug
When I run the above command, the output skips the "NAME" header.
Omitting the
--colorflag has no effect.Changing from iTerm2 to Terminal has no effect.
Piping explicitly instead of from PHP has no effect.
Removing
configfrom the command does have an effect. Maybe it's because the synopsis forcore configis longer than $COLUMNS.