Beefy Boxes and Bandwidth Generously Provided by pair Networks
There's more than one way to do things

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??
I'll chime in with the Mac folk on BBEdit. My only gripe with it is that it's Mac only. If there were a *nix and Win32 port it would be my only editor. Since it's not, I agonized over this issue for a long while. I finally opted for vi/vim/gvim.

As a sys admin, proficiency in vi is essential, so why learn another editor? vi is like Unix itself, you can be immersed in it for years and still learn something new almost every day. Anything it can't do is likely only a shell escape away.

As GVIM, I get all the GUI features I need, syntax coloring, customization, consistency, etc. I can run the same editor on MacOS (9 or X), Win32, and *nix, and it behaves the same way. The admins that work for me and I agreed on a .exrc/.vimrc set up to help us enforce our shell/perl scripting standards.

When vim/gvim is not available there is always vi. By using vim/gvim I maintain my vi proficiency. That way when the axe falls, and I'm down in single user mode, I'm ready to rock. No worrying about what the proper syntax is for that global search/replace or whether or not I can mount that file system I had emacs/pico/joe/etc. installed on.

In reply to Re: Perl Programming Tools - (who, what, where, when, and why) by rah
in thread Perl Programming Tools - (who, what, where, when, and why) by diakonos

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 or How to display code and escape characters are good places to start.
Log In?

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

How do I use this? | Other CB clients
Other Users?
Others contemplating the Monastery: (6)
As of 2022-08-18 16:07 GMT
Find Nodes?
    Voting Booth?

    No recent polls found