Beefy Boxes and Bandwidth Generously Provided by pair Networks
Clear questions and runnable code
get the best and fastest answer

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??
Just to get a few things out of the way:
  • vim is what I use - if you don't fine.
  • flames are useless, I use ar0n as a shield.
  • you may think your editor is the best and that's fine, but this is a post about vim.
  • I am not a vim expert.
  • vim rules. =)

On to The Meat (tm).
I was playing a bit with my .vimrc file today and wondered what some of you out there had slapped together. I am no expert programmer and I don't live in this tool as much as some of you probably do. I was wondering if anybody would be willing to show some fancy tricks or part of their configs that they liked to share.

Here is my .vimrc (very short):

    :abbr #b # ----------
    set background=dark
    syntax on
    set smartindent
    set softtabstop=4

line #1: sets an alias '#b' to '# ----------' for comments.
line #2: sets my background to dark so my gnome terminal looks ok with the syntax on.
line #3: turns syntax highlighting on.
line #4: turns smartindent on (watches for left and right curly braces for automatic insertion and removal of indentation).
line #5: mingles tabs and spaces for tabbing within your file. At my setting, if I hit tab once, it creates four spaces, if I hit it again, it creates a tab. Nice when going from one editor to another and not having too much tabs.

Anyhow, that is my config and I know its fairly sparse. Anybody else want to share?


In reply to Vim configs (slightly OT) by djw

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 drinking their drinks and smoking their pipes about the Monastery: (3)
As of 2022-05-27 01:09 GMT
Find Nodes?
    Voting Booth?
    Do you prefer to work remotely?

    Results (94 votes). Check out past polls.