Beefy Boxes and Bandwidth Generously Provided by pair Networks
Welcome to the Monastery

comment on

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

I personally believe that as an italian guy I should confirm that the name is very appealing! Just to pinpoint a detail though: pine nuts are a fundamental ingredient of pesto, but just not the main one. Of course we may use nano as a base for szabgab's IDE, which would bring us to... nesto? No, I don't think so, since it's horrible. OTOH serendipitously it suggests me of nest, which IMHO is fine albeit not Perl-related in any way I can think of. A nest, in fact, conveys the idea of (a nice and warm) environment. There only remains to find a suitable backronym for it, or not?

Well, how 'bout a self-recursive one: "Nest: Enhanced Sourcecode T..." D'Oh, I can't think of a suitable word beginning with T!

If you can't understand the incipit, then please check the IPB Campaign.

In reply to Re^3: Name a Perl IDE - get a Perl book or YAPC ticket by blazar
in thread Name a Perl IDE - get a Perl book or YAPC ticket by szabgab

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.