Sponsored Content
Top Forums UNIX for Beginners Questions & Answers Bad substitution issues.. but why? Post 302980258 by vbe on Thursday 25th of August 2016 01:07:04 PM
Old 08-25-2016
did you try this code
Code:
NUMBER_OF_FILES = ${ls ${PATH_TO_DATASET} |  wc -l )

before including it in a script?
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Bad Substitution

Need Help... I am getting a bad substitution error on my script on a Solaris Server. However the script has been proven to work on HPUX and Solaris servers... #!/usr/bin/sh # # Set the location of the tzupdater.jar file # JAR=/tmp/tzupdater.jar # <<<<< UPDATE THIS LINE... (3 Replies)
Discussion started by: D_Redd74
3 Replies

2. Shell Programming and Scripting

Array reference - bad substitution

I've created a series of arrays named as follows: row1 row2 row3 . . . row10 Each has 4 elements. I'm trying to echo the array elements out in a for loop. Here's what I have: for ((i=1;i<=10;i++)) do for ((j=1;j<=4;j++)) do eval out=${row`echo $i`} echo -n $out (3 Replies)
Discussion started by: swankgd
3 Replies

3. Shell Programming and Scripting

bad substitution error in ksh

hi, i created a shell script having the following content: #! /usr/bin/ksh FROM="myemail@domain.com" MAILTO="someemail@domain" SUBJECT="TEST" BODY="/export/home/adshocker/body.txt" ATTACH="/export/home/adshocker/attach.prog" echo $ATTACH ATTACH_NAME="${ATTACH##*/}" echo $ATTACH_NAME... (5 Replies)
Discussion started by: adshocker
5 Replies

4. Shell Programming and Scripting

bad substitution error in ksh

Hello, In bash I can use the following: TMP=12345 MID=${TMP:1:1} the expected result is: 2 but when using KSH I'm getting a ''bad substitution" error. What is the correct syntaxin ksh? Thanks (2 Replies)
Discussion started by: LiorAmitai
2 Replies

5. UNIX for Dummies Questions & Answers

bad substitution

#!/bin/bash a1=( win 12,01,02,03,04 ) a2=( pre 04,05,06 ) a3=( msn 06,07,08,09 ) Given the above arrays, I want the script to return/echo the following in a loop; win 12,01,02,03,04 pre 04,05,06,07 msn 06,07,08,09 But I can't get it to do as such. I've tried; (2 Replies)
Discussion started by: Muhammad Rahiz
2 Replies

6. Shell Programming and Scripting

bad substitution error!

Hi All, I'm building a new shell script but i'm facing a problem with one line which is giving "bad substitution" error. Please assist script lines: #!/bin/sh printf "%s: " "Occurrence DATE (YYYYMMDD)"; read DATE shortdate=${DATE#??} o/p: ./test1: bad substitution This command is... (2 Replies)
Discussion started by: Dendany83
2 Replies

7. Programming

Make: Bad Substitution

Hi, I have a make file which I try to execute, but it failed when it arrived to the line: for r in ${PIPESTATUS }; do if (($r != 0)); then exit $r; fi;done; With the Error: ""make:/bin/sh: Bad substitution"" Or the Error: "make:${PIPESTATUS[...}: Bad substitution" (Depend on the operating... (3 Replies)
Discussion started by: nadne
3 Replies

8. Shell Programming and Scripting

Why I get bad bad substitution when using eval?

Why I get bad replace when using eval? $ map0=( "0" "0000" "0") $ i=0 $ eval echo \${map$i} 0000 $ a=`eval echo \${map$i}` !!!error happens!!! bash: ${map$i}: bad substitution How to resolve it ? Thanks! (5 Replies)
Discussion started by: 915086731
5 Replies

9. Shell Programming and Scripting

Bad substitution

Cant undestand :) why i have an error on line 2.it is working on my other boxes #!/bin/bash ret=$(echo Q | timeout 5 openssl s_client connect "${1`hostname`}:${2-443}" -ssl3 2> /dev/null) if echo "${ret}" | grep -q 'Protocol.*SSLv3'; then if echo "${ret}" | grep -q 'Cipher.*0000'; then ... (7 Replies)
Discussion started by: kenshinhimura
7 Replies

10. Shell Programming and Scripting

Bad substitution - ShellCheck says okay

ShellCheck doesn't find any issues with this script. #!/bin/bash # color_meanings: explain meanings of colors used in bash ls eval "$(echo "no:fi:di:ln:pi:so:do:bd:cd:or:mi:su:sg:tw:st:ex" | sed -e 's/:/=/g; s/\;/\n/g')" { IFS=: for i in $LS_COLORS do ... (18 Replies)
Discussion started by: Xubuntu56
18 Replies
Locale::Script(3pm)					 Perl Programmers Reference Guide				       Locale::Script(3pm)

NAME
Locale::Script - ISO codes for script identification (ISO 15924) SYNOPSIS
use Locale::Script; use Locale::Constants; $script = code2script('ph'); # 'Phoenician' $code = script2code('Tibetan'); # 'bo' $code3 = script2code('Tibetan', LOCALE_CODE_ALPHA_3); # 'bod' $codeN = script2code('Tibetan', LOCALE_CODE_ALPHA_NUMERIC); # 330 @codes = all_script_codes(); @scripts = all_script_names(); DESCRIPTION
The "Locale::Script" module provides access to the ISO codes for identifying scripts, as defined in ISO 15924. For example, Egyptian hieroglyphs are denoted by the two-letter code 'eg', the three-letter code 'egy', and the numeric code 050. You can either access the codes via the conversion routines (described below), or with the two functions which return lists of all script codes or all script names. There are three different code sets you can use for identifying scripts: alpha-2 Two letter codes, such as 'bo' for Tibetan. This code set is identified with the symbol "LOCALE_CODE_ALPHA_2". alpha-3 Three letter codes, such as 'ell' for Greek. This code set is identified with the symbol "LOCALE_CODE_ALPHA_3". numeric Numeric codes, such as 410 for Hiragana. This code set is identified with the symbol "LOCALE_CODE_NUMERIC". All of the routines take an optional additional argument which specifies the code set to use. If not specified, it defaults to the two- letter codes. This is partly for backwards compatibility (previous versions of Locale modules only supported the alpha-2 codes), and partly because they are the most widely used codes. The alpha-2 and alpha-3 codes are not case-dependent, so you can use 'BO', 'Bo', 'bO' or 'bo' for Tibetan. When a code is returned by one of the functions in this module, it will always be lower-case. SPECIAL CODES The standard defines various special codes. o The standard reserves codes in the ranges qa - qt, qaa - qat, and 900 - 919, for private use. o zx, zxx, and 997, are the codes for unwritten languages. o zy, zyy, and 998, are the codes for an undetermined script. o zz, zzz, and 999, are the codes for an uncoded script. The private codes are not recognised by Locale::Script, but the others are. CONVERSION ROUTINES
There are three conversion routines: "code2script()", "script2code()", and "script_code2code()". code2script( CODE, [ CODESET ] ) This function takes a script code and returns a string which contains the name of the script identified. If the code is not a valid script code, as defined by ISO 15924, then "undef" will be returned: $script = code2script('cy'); # Cyrillic script2code( STRING, [ CODESET ] ) This function takes a script name and returns the corresponding script code, if such exists. If the argument could not be identified as a script name, then "undef" will be returned: $code = script2code('Gothic', LOCALE_CODE_ALPHA_3); # $code will now be 'gth' The case of the script name is not important. See the section "KNOWN BUGS AND LIMITATIONS" below. script_code2code( CODE, CODESET, CODESET ) This function takes a script code from one code set, and returns the corresponding code from another code set. $alpha2 = script_code2code('jwi', LOCALE_CODE_ALPHA_3 => LOCALE_CODE_ALPHA_2); # $alpha2 will now be 'jw' (Javanese) If the code passed is not a valid script code in the first code set, or if there isn't a code for the corresponding script in the second code set, then "undef" will be returned. QUERY ROUTINES
There are two function which can be used to obtain a list of all codes, or all script names: "all_script_codes ( [ CODESET ] )" Returns a list of all two-letter script codes. The codes are guaranteed to be all lower-case, and not in any particular order. "all_script_names ( [ CODESET ] )" Returns a list of all script names for which there is a corresponding script code in the specified code set. The names are capitalised, and not returned in any particular order. EXAMPLES
The following example illustrates use of the "code2script()" function. The user is prompted for a script code, and then told the corresponding script name: $| = 1; # turn off buffering print "Enter script code: "; chop($code = <STDIN>); $script = code2script($code, LOCALE_CODE_ALPHA_2); if (defined $script) { print "$code = $script "; } else { print "'$code' is not a valid script code! "; } KNOWN BUGS AND LIMITATIONS
o When using "script2code()", the script name must currently appear exactly as it does in the source of the module. For example, script2code('Egyptian hieroglyphs') will return eg, as expected. But the following will all return "undef": script2code('hieroglyphs') script2code('Egyptian Hieroglypics') If there's need for it, a future version could have variants for script names. o In the current implementation, all data is read in when the module is loaded, and then held in memory. A lazy implementation would be more memory friendly. SEE ALSO
Locale::Language ISO two letter codes for identification of language (ISO 639). Locale::Currency ISO three letter codes for identification of currencies and funds (ISO 4217). Locale::Country ISO three letter codes for identification of countries (ISO 3166) ISO 15924 The ISO standard which defines these codes. http://www.evertype.com/standards/iso15924/ Home page for ISO 15924. AUTHOR
Neil Bowers <neil@bowers.com> COPYRIGHT
Copyright (c) 2002-2004 Neil Bowers. This module is free software; you can redistribute it and/or modify it under the same terms as Perl itself. perl v5.12.1 2010-05-13 Locale::Script(3pm)
All times are GMT -4. The time now is 07:48 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy