Sponsored Content
Full Discussion: Adding Color to bash
Operating Systems OS X (Apple) Adding Color to bash Post 302403105 by ASGR on Thursday 11th of March 2010 11:56:23 AM
Old 03-11-2010
Hey guys,

This works...

Code:
#!/bin/bash
if [ $clr="r" ]; then 
    echo -e '\E[1;31m'
    fi

Notes:
Removed surrounding spaces around the '=' (doesn't like extra spaces)
Removed extra space after closing square bracket (not major)
Changed escape character at beginning of string to '\E' (can't remember the difference)
Used single quotes for the string (apparently recommended but optional)
Added 'fi' to terminate the 'if' command (compulsory)

A.
 

6 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

How to get rid of all the weird characters and color on bash shell

Does anyone of you know how to turn off color and weird characters on bash shell when using the command "script"? Everytime users on my server used that command to record their script, they either couldn't print it because lp kept giving the "unknown format character" messages or the print paper... (1 Reply)
Discussion started by: Micz
1 Replies

2. Shell Programming and Scripting

bash: color strings in log file

hello im looking for an easy way to color specific strings in text file. simple example: cat file1 acb 1234 qwer 5678 my goal: cat file1 (color the acb red and the 5678 blue) acb 1234 qwer 5678 cheers (2 Replies)
Discussion started by: modcan
2 Replies

3. Shell Programming and Scripting

Bash - changing a color of a substring

Hello! I need to write a bash script for my university classes, and I came up with an idea of a program that would test the speed of typing - there is some random text that you have to rewrite, and the script measures time, number of mistakes etc. The text would be visible on the screen all... (3 Replies)
Discussion started by: xqwzts
3 Replies

4. Shell Programming and Scripting

color in bash

I have some tcsh scripts that produce output in color, but does not work in bash. Any idea on a solution? echo " \033 (6 Replies)
Discussion started by: kristinu
6 Replies

5. UNIX for Dummies Questions & Answers

Adding Color using More

Daily Stupid Question: When I use a cat with a grep I can see "blind SQL injection vulnerablity" highlighted as red and is easily readable cat file |grep -i 'blind\ SQL\ injection\ vulnerability' When I add a more to view the results page at a time, the color is taken away and is... (3 Replies)
Discussion started by: metallica1973
3 Replies

6. Shell Programming and Scripting

Gawk adding color

I want to know if there is any way to highlight search results using GAWK. So for example: gawk '{IGNORECASE=1;} /^<a/&&/\$/' index.html <a class=author href="http://washingtondc.craigslist.org/search/?areaID=10&amp;amp;catAbb=sss&amp;amp;query=ps vita" title="craigslist washington, DC | all for sale... (3 Replies)
Discussion started by: metallica1973
3 Replies
CPAN::Meta::History(3)					User Contributed Perl Documentation				    CPAN::Meta::History(3)

NAME
CPAN::Meta::History - history of CPAN Meta Spec changes VERSION
version 2.120921 DESCRIPTION
The CPAN Meta Spec has gone through several iterations. It was originally written in HTML and later revised into POD (though published in HTML generated from the POD). Fields were added, removed or changed, sometimes by design and sometimes to reflect real-world usage after the fact. This document reconstructs the history of the CPAN Meta Spec based on change logs, repository commit messages and the published HTML files. In some cases, particularly prior to version 1.2, the exact version when certain fields were introduced or changed is inconsistent between sources. When in doubt, the published HTML files for versions 1.0 to 1.4 as they existed when version 2 was developed are used as the definitive source. Starting with version 2, the specification document is part of the CPAN-Meta distribution and will be published on CPAN as CPAN::Meta::Spec. Going forward, specification version numbers will be integers and decimal portions will correspond to a release date for the CPAN::Meta library. HISTORY
Version 2 April 2010 o Revised spec examples as perl data structures rather than YAML o Switched to JSON serialization from YAML o Specified allowed version number formats o Replaced 'requires', 'build_requires', 'configure_requires', 'recommends' and 'conflicts' with new 'prereqs' data structure divided by phase (configure, build, test, runtime, etc.) and relationship (requires, recommends, suggests, conflicts) o Added support for 'develop' phase for requirements for maintaining a list of authoring tools o Changed 'license' to a list and revised the set of valid licenses o Made 'dynamic_config' mandatory to reduce confusion o Changed 'resources' subkey 'repository' to a hash that clarifies repository type, url for browsing and url for checkout o Changed 'resources' subkey 'bugtracker' to a hash for either web or mailto resource o Changed specification of 'optional_features': o Added formal specification and usage guide instead of just example o Changed to use new prereqs data structure instead of individual keys o Clarified intended use of 'author' as generalized contact list o Added 'release_status' field to indicate stable, testing or unstable status to provide hints to indexers o Added 'description' field for a longer description of the distribution o Formalized use of "x_" or "X_" for all custom keys not listed in the official spec Version 1.4 June 2008 o Noted explicit support for 'perl' in prerequisites o Added 'configure_requires' prerequisite type o Changed 'optional_features' o Example corrected to show map of maps instead of list of maps (though descriptive text said 'map' even in v1.3) o Removed 'requires_packages', 'requires_os' and 'excluded_os' as valid subkeys Version 1.3 November 2006 o Clarified that all prerequisites take version range specifications o Added 'no_index' subkey 'directory' and removed 'dir' to match actual usage in the wild o Added a 'repository' subkey to 'resources' Version 1.2 August 2005 o Re-wrote and restructured spec in POD syntax o Changed 'name' to be mandatory o Changed 'generated_by' to be mandatory o Changed 'license' to be mandatory o Added required 'abstract' field o Added required 'author' field o Added required 'meta-spec' field to define 'version' (and 'url') of the CPAN Meta Spec used for metadata o Added 'provides' field o Added 'no_index' field and deprecated 'private' field. 'no_index' subkeys include 'file', 'dir', 'package' and 'namespace' o Added 'keywords' field o Added 'resources' field with subkeys 'homepage', 'license', and 'bugtracker' o Added 'optional_features' field as an alternate under 'recommends'. Includes 'description', 'requires', 'build_requires', 'conflicts', 'requires_packages', 'requires_os' and 'excluded_os' as valid subkeys o Removed 'license_uri' field Version 1.1 May 2003 o Changed 'version' to be mandatory o Added 'private' field o Added 'license_uri' field Version 1.0 March 2003 o Original release (in HTML format only) o Included 'name', 'version', 'license', 'distribution_type', 'requires', 'recommends', 'build_requires', 'conflicts', 'dynamic_config', 'generated_by' AUTHORS
o David Golden <dagolden@cpan.org> o Ricardo Signes <rjbs@cpan.org> COPYRIGHT AND LICENSE
This software is copyright (c) 2010 by David Golden and Ricardo Signes. This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself. perl v5.16.3 2012-04-01 CPAN::Meta::History(3)
All times are GMT -4. The time now is 06:48 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy