Package home | Report new bug | New search | Development Roadmap Status: Open | Feedback | All | Closed Since Version 1.0.0RC2

Request #13441 console output too long
Submitted: 2008-03-19 21:58 UTC
From: kguest Assigned: kguest
Status: Closed Package: PEAR_Size (version 0.1.1)
PHP Version: 5.1.6 OS:
Roadmaps: 0.1.2    
Subscription  
Comments Add Comment Add patch


Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know! Just going to say 'Me too!'? Don't clutter the database with that please !
Your email address:
MUST BE VALID
Solve the problem : 43 + 37 = ?

 
 [2008-03-19 21:58 UTC] kguest (Ken Guest)
Description: ------------ limit Console_Table output to 80 columns, as per Laurent Laville's request.

Comments

 [2008-03-21 12:25 UTC] farell (Laurent Laville)
To complete the feature/request: Restrict text output to 80 columns, rather than give such output (for example) Total: 2.37 MB pear.php.net: ============= Total: 2.37 MB +----------------+---------+---------------------------------------------------- -------------------------+ | HTML_Progress2 | 2.37 MB | (data: 65.50 KB; doc: 1.91 MB; php: 318.87 KB; scri pt: 0 B; test: 84.64 KB) | +----------------+---------+---------------------------------------------------- -------------------------+ A possible solution (no patch: I'll let you see what is the best one) is (as I did for PHP_CompatInfo) to addFilter function on Console_Table, in Size_Output_text.php file. A line by role file is a bit more readable Something like : +-----------------+---------+--------------------------+ | HTML_Progress2 | 2.37 MB | data: 65.50 KB | | | | doc: 1.91 MB | | | | php: 318.87 KB | | | | script: 0 B | | | | test: 84.64 KB | +-----------------+---------+--------------------------+
 [2008-03-27 21:43 UTC] kguest (Ken Guest)
This bug has been fixed in CVS. If this was a documentation problem, the fix will appear on pear.php.net by the end of next Sunday (CET). If this was a problem with the pear.php.net website, the change should be live shortly. Otherwise, the fix will appear in the package's next release. Thank you for the report and for helping us make PEAR better.