New Code Tags (Syntax Highlighting) Post: 303019458

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Emacs color syntax highlighting

So... i cant get it to work. I had already posted this but it got deleted. Details: Im running SSH shell on Windows XP, connecting to a server whose term is vt100 (someone asked me that last time) Im trying to get the syntax highlighting in cc mode to work in color, but its black and...

2. UNIX for Dummies Questions & Answers

color highlighting with 'more','grep' and 'vi'

Hi all, i would to find out how can i turn on color hightlighting with the 'more' command. When i view a big file, i tend to use the 'more' command and i would search for a interested string with the '/' command. Something the search returns more than 1 line found on the screen, how can i...

3. Programming

Vim highlighting annoyance

I was using vim about an hour ago doing abit of python (i only just started using vim). And I think i typed something wrong, and all of a sudden the letter i is always highlighted. Turning syntax off and on didn't work. and i couldent find the solution online. Thanks in advanced.

4. UNIX and Linux Applications

gedit/gtksourceview: Updating types for syntax highlighting?

I wrote a new .lang file for syntax highlighting a language I use frequently. It works fine, except that it doesn't glob onto the files automatically. Is there a utility I need to run to update a gtksourceview database? Here's the relevant portion of the code. <language id="pari"...

5. Shell Programming and Scripting

How to stop Vim from highlighting lines 73+

I am slowly developing my .vimrc and would like to know how to turn off the highlighting (black text on orange background) which starts at line 73. This doesn't seem to be controlled by any selected/customized colorscheme. I do CFD, and some older codes I use are written in F77, for which this...

6. AIX

[Vim] Question about syntax highlighting

Hi all, my sysadmin installed Vim packages (vim-enhanced-6.3-1 & vim-common-6.3-1) on an Aix system (7.1.0.0). I log in using Putty (vs 0.54) and got an annoying underline issue. All strings and var names are underlined as you can see on the attached file Is it possible to get rid of that...

7. UNIX for Dummies Questions & Answers

Reapplying syntax highlighting in vim

I had a bash script (ma_report.sh) that I was editing when my VPN connection died. So, when I reconnected, I recovered my changes and reopened the file. Everything looks fine except that there is no longer any syntax highlighting. Using ':syntax on' does not work. Other bash scripts in vim do...

8. Shell Programming and Scripting

Highlighting duplicate string on a line

Hi all I have a grep written to pull out values; below (in the code snip-it) is an example of the output. What I'm struggling to do, and looking for assistance on, is identifying the lines that have duplicate strings. For example 74859915K74859915K in the below is 74859915K repeated twice but...

LEARN ABOUT CENTOS

perl::critic::policy::valuesandexpressions::prohibitinterpolatio

Perl::Critic::Policy::ValuesAndExpressions::ProhibitInteUseraContribPerl::Critic::Policy::ValuesAndExpressions::ProhibitInterpolationOfLiterals(3)

NAME

       Perl::Critic::Policy::ValuesAndExpressions::ProhibitInterpolationOfLiterals - Always use single quotes for literal strings.

AFFILIATION

       This Policy is part of the core Perl::Critic distribution.

DESCRIPTION

       Don't use double-quotes or "qq//" if your string doesn't require interpolation.	This saves the interpreter a bit of work and it lets the
       reader know that you really did intend the string to be literal.

	   print "foobar";     #not ok
	   print 'foobar';     #ok
	   print qq/foobar/;   #not ok
	   print q/foobar/;    #ok

	   print "$foobar";    #ok
	   print "foobar
";   #ok
	   print qq/$foobar/;  #ok
	   print qq/foobar
/; #ok

	   print qq{$foobar};  #preferred
	   print qq{foobar
}; #preferred

       Use of double-quotes might be reasonable if the string contains single quote (') characters:

	   print "it's me";    # ok, if configuration flag set

CONFIGURATION

       The types of quoting styles to exempt from this policy can be configured via the "allow" option.  This must be a whitespace-delimited
       combination of some or all of the following styles: "qq{}", "qq()", "qq[]", and "qq//".

       This is useful because some folks have configured their editor to apply special syntax highlighting within certain styles of quotes.  For
       example, you can tweak "vim" to use SQL highlighting for everything that appears within "qq{}" or "qq[]" quotes.  But if those strings are
       literal, Perl::Critic will complain.  To prevent this, put the following in your .perlcriticrc file:

	   [ValuesAndExpressions::ProhibitInterpolationOfLiterals]
	   allow = qq{} qq[]

       The flag "allow_if_string_contains_single_quote" permits double-quoted strings if the string contains a single quote (') character.  It
       defaults to off; to turn it on put the following in your .perlcriticrc file:

	   [ValuesAndExpressions::ProhibitInterpolationOfLiterals]
	   allow_if_string_contains_single_quote = 1

SEE ALSO

       Perl::Critic::Policy::ValuesAndExpressions::RequireInterpolationOfMetachars

AUTHOR

       Jeffrey Ryan Thalhammer <jeff@imaginative-software.com>

COPYRIGHT

       Copyright (c) 2005-2011 Imaginative Software Systems.  All rights reserved.

       This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself.  The full text of this license
       can be found in the LICENSE file included with this module.

perl v5.16.3							    Perl::Critic::Policy::ValuesAndExpressions::ProhibitInterpolationOfLiterals(3)