Beefy Boxes and Bandwidth Generously Provided by pair Networks
Perl-Sensitive Sunglasses
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??

Hi Monks,

I want some help regarding console output formatting. As of now, I'm using print function rather printf. I don't know if printf can solve my problem.

I'm printing some informative message e.g "installing LUA.." and once this task gets over, based on the status, I print "done" or "failed". Now, the issue is, this done/failed status message is printed in scattered way (as first print size varies as per informative message length). How can I print all done/failed in one column from top to bottom (or if writing it to right side of console possible regardless of left side message size)?

Below is the output snippet I get as of now -

Mapping a drive to build machine 10.211.32.254.. done Mapped to V drive Deleting TestHarness_LUA directory.. done Deleting TestHarness_LUA-distribution.zip file.. done Copying TestHarness_LUA-distribution.zip from mapped V drive.. +done

Below is the output I'm looking for -

Mapping a drive to build machine 10.211.32.254.. done Mapped to V drive Deleting TestHarness_LUA directory.. done Deleting TestHarness_LUA-distribution.zip file.. done Copying TestHarness_LUA-distribution.zip from mapped V drive.. done

Please let me know your suggestions.


In reply to Console Output Formatting Help Required by tarunmudgal4u

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others lurking in the Monastery: (5)
As of 2024-04-19 06:48 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found