Using sed with bash variables Post: 302945874

9 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

using sed on bash variables (or maybe awk?)

Hi all- I've been fooling with this for a few days, but I'm rather new at this... I have a bash variable containing a long string of various characters, for instance: JUNK=this that the other xyz 1234 56 789 I don't know what "xyz" actually is, but I know that: START=he other and ...

2. Shell Programming and Scripting

Bash variables

Ummm can anybody help me with this one? Its prob quite simple. I bascially have a file name say J1x2x3x7.dat Im using the file name as a variable in a bash script. Want I want to do is extract most of the file name and make it a new variable expect with say one of the number now a...

3. Shell Programming and Scripting

how to use in bash variables and quotes

I have some troubles with variables and quotes... I want: if $URL is empty (no user input) go to http://www.localhost/index.php/ else add this string (search) "?s=+$URL" EXAMPLE: No user input string= http://www.localhost/index.php/ User input = "unix" string=...

4. UNIX for Dummies Questions & Answers

Expanding variables with Ed Bash 3.2.33

Hi, The following code finds the line containing fruits in test.txt and replaces instances of apple with banana. ed -s test.txt <<< $'/fruits/s/apple/banana/g\nw' What I want to do is put variables in the place of fruits, apple and banana. I have tried replacing ' with " to get...

5. Shell Programming and Scripting

Complex bash/sed, variables and nested quotes

Ok, this one isn't for everybody, it's pretty tough and I've spent a good deal of time on it without figuring it out yet. Can anybody get this script to work: #!/bin/bash cq_fname="%let outputfile="/user/cq_"$1".csv";" sed "29s/.*/\"$cq_fname\"/" file1.sas >...

6. Shell Programming and Scripting

Indirect variables in Bash

Hello, I've spent hours this morning reading various past forum posts and documentation pages but I can't find exactly what I need. I'm trying to call a variable with a variable in the name without having to make a third variable. For example: path=AB legAB=50 leg$path I want to...

7. Shell Programming and Scripting

BASH arrays and variables of variables in C++

Sometimes it is handy to protect long scripts in C++. The following syntax works fine for simple commands: #define SHELLSCRIPT1 "\ #/bin/bash \n\ echo \"hello\" \n\ " int main () { cout <<system(SHELLSCRIPT1); return 0; } Unfortunately for there are problems for: 1d arrays:...

8. Shell Programming and Scripting

Expect - bash and variables

I was wondering if anyone could provide some assistance. I trying to run an expect script within bash and get the results of a variable called RESULT. I Have tried a few things but none of them have worked. I know that the child process (the expect script) in this instance cannot set a variable...

9. Shell Programming and Scripting

Passing awk variables to bash variables

Trying to do so echo "111:222:333" |awk -F: '{system("export TESTO=" $2)}'But it doesn't work

LEARN ABOUT CENTOS

perl::critic::policy::valuesandexpressions::prohibitquotesasquot

Perl::Critic::Policy::ValuesAndExpressions::ProhibitQuotPerl::Critic::Policy::ValuesAndExpressions::ProhibitQuotesAsQuotelikeOperatorDelimiters(3)

NAME

       Perl::Critic::Policy::ValuesAndExpressions::ProhibitQuotesAsQuotelikeOperatorDelimiters - Don't use quotes ("'", """, "`") as delimiters
       for the quote-like operators.

AFFILIATION

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

DESCRIPTION

       With the obvious exception of using single-quotes to prevent interpolation, using quotes with the quote-like operators kind of defeats the
       purpose of them and produces obfuscated code, causing problems for future maintainers and their editors/IDEs.

	   $x = q"q";		     #not ok
	   $x = q'q';		     #not ok
	   $x = q`q`;		     #not ok

	   $x = qq"q";		     #not ok
	   $x = qr"r";		     #not ok
	   $x = qw"w";		     #not ok

	   $x = qx`date`;	     #not ok

	   $x =~ m"m";		     #not ok
	   $x =~ s"s"x";	     #not ok
	   $x =~ tr"t"r";	     #not ok
	   $x =~ y"x"y";	     #not ok

	   $x =~ m'$x'; 	     #ok
	   $x =~ s'$x'y';	     #ok
	   $x = qr'$x'm;	     #ok
	   $x = qx'finger foo@bar';  #ok

CONFIGURATION

       This policy has three options: "single_quote_allowed_operators", "double_quote_allowed_operators", and "back_quote_allowed_operators",
       which control which operators are allowed to use each of "'", """, "`" as delimiters, respectively.

       The values allowed for these options are a whitespace delimited selection of the "m", "q", "qq", "qr", "qw", "qx", "s", "tr", and "y"
       operators.

       By default, double quotes and back quotes (backticks) are not allowed as delimiters for any operators and single quotes are allowed as
       delimiters for the "m", "qr", "qx", and "s" operators.  These defaults are equivalent to having the following in your .perlcriticrc:

	   [ValuesAndExpressions::ProhibitQuotesAsQuotelikeOperatorDelimiters]
	   single_quote_allowed_operators = m s qr qx
	   double_quote_allowed_operators =
	   back_quote_allowed_operators =

SUGGESTED BY

       Michael Schwern

AUTHOR

       Elliot Shank "<perl@galumph.com>"

COPYRIGHT

       Copyright (c) 2007-2011 Elliot Shank.

       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::ProhibitQuotesAsQuotelikeOperatorDelimiters(3)