Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

our text editors, our secret masters 6 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • If I have a comment that I want to stand out I use the shebang rule to my advantage (dark blue instead of cyan).
    #!# A very important comment that want everyone to notice

    • Re:I'm Guilty (Score:1)

      by sigzero (5768) on 2008.10.08 12:49 (#65328) Journal

      I am color weak so that is hard for me to tell so I just use # XXX to have something stand out.

      • Heh. I also use that trick from time to time. That reminds me, I need to modify my Vim config to make '# BUG' stand out in red.
        • I copied the perl syntax file to my .vim directory and tweaked it to highlight bug comments differently. 'BUG' gets colored white on red and the rest of the comment in the normal cyan (if you use the default color scheme).

          [mmusgrove@test perl]$ diff /usr/share/vim/vim70/syntax/perl.vim ~/.vim/syntax/perl.vim
          125a126
          > syn keyword perlBug                     BUG contained
          371c372
          < syn match  perlComment           

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.