Indirect variables in Bash Post: 302769096

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Compound indirect variable references

Using bash, I'm trying to read a .properties file (name=value pairs), assigning an indirect variable reference for each line in the file. The trick is that a property's value string may contain the name of a property that occurred earlier in the file, and I want the name of the 1st property to...

2. Shell Programming and Scripting

Length of an indirect variable

The construct ${#parameter} returns the number of characters in the parameter and ${!parameter} specifies an indirect variable. My question is: How do I combine these two. What I want is ${#!parameter} but this gives an error. Of course I can use: dummy=${!parameter} ${#dummy} but that's a...

3. 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...

4. Linux

How to get an Indirect Variable Value..?

Hi, I've got a small problem. If varible A stores "B" and Variable B stores C, How to get the value of variable B by using only Variable A..? I tried the following but didnt work pease help.. $ var1=vikram $ echo $var1 vikram $ vikram=sampath $ echo $vikram sampath $ echo...

5. Shell Programming and Scripting

Indirect variable assignment

Hi I have variable A_B=alpha also var1="A" var2="B" I want to retrieve the value alpha using var1 and var2 , somthing like echo ${${var1}_${var2}} that works. Obviously this is receiving syntax error

6. Shell Programming and Scripting

Does SH support indirect expansion like BASH?

Hello, is there a kind soul who can answer me, does the SH support double substitution known as indirect expansion similar to BASH? The syntax for bash is ${!var}. For instance in bash I can write something like this: VAR="value" REF_VAR="VAR" echo ${!REF_VAR} and get the "value"...

7. Shell Programming and Scripting

Indirect Referral Script

I have a file with two columns of numbers (member IDs): 1 1 2 1 3 1 4 2 5 4 6 1 7 5 8 3 9 2 Think of column 1 as the referee and column 2 as the referrer. Is there a good way to backtrack who referred who? I would like an output, for this example here to be: 1 1 2 1 3 1 4 2 1

8. 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:...

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

devscripts.conf

DEVSCRIPTS.CONF(5)						File Formats Manual						DEVSCRIPTS.CONF(5)

NAME

       devscripts.conf - configuration file for the devscripts package

DESCRIPTION

       The  devscripts	package provides a collection of scripts which may be of use to Debian developers and others wishing to build Debian pack-
       ages.  Many of these have options which can be configured on a system-wide and per-user basis.

       Every script in the devscripts package which makes use of values from these configuration files describes the specific settings	recognised
       in its own manpage.  (For a list of the scripts, either see /usr/share/doc/devscripts/README.gz or look at the output of dpkg -L devscripts
       | grep /usr/bin.)

       The two configuration files are /etc/devscripts.conf for system-wide defaults and ~/.devscripts for per-user settings.	They  are  written
       with  bash(1)  syntax, but should only have comments and simple variable assignments in them; they are both sourced (if present) by many of
       the devscripts scripts.	Variables corresponding to simple switches should have one of the values yes and no; any other setting is regarded
       as equivalent to the default setting.

       All  variable  names  are  written  in  uppercase, and begin with the script name.  Package-wide variables begin with "DEVSCRIPTS", and are
       listed below, as well as in the relevant manpages.

       For a list of  all  of  the  available  options	variables,  along  with  their	default  settings,  see  the  example  configuration  file
       /usr/share/doc/devscripts/devscripts.conf.ex.   This  is  copied  to  /etc/devscripts.conf  when the devscripts package is first installed.
       Information about configuration options introduced in newer versions of the package will be appended to /etc/devscripts.conf when the pack-
       age is upgraded.

       Every script which reads the configuration files can be forced to ignore them by using --no-conf as the first command-line option.

PACKAGE-WIDE VARIABLES
       The currently recognised package-wide variables are:

       DEVSCRIPTS_CHECK_DIRNAME_LEVEL, DEVSCRIPTS_CHECK_DIRNAME_REGEX
	      These  variables	control  scripts  which change directory to find a debian/changelog file or suchlike, and some other miscellaneous
	      cases.  In order to prevent unwanted, even possibly dangerous, behaviour, these variables control when actions  will  be	performed.
	      The scripts which currently make use of these variables are: debc, debchange/dch, debclean, debi, debrelease, debuild and uscan, but
	      this list may change with time (and I may not remember to update this manpage).  Please see the manpages of individual  scripts  for
	      details of the specific behaviour for each script.

SEE ALSO

       devscripts(1) and /usr/share/doc/devscripts/README.gz.

AUTHOR

       This manpage was written for the devscripts package by the package maintainer Julian Gilbey <jdg@debian.org>.

DEBIAN
								 Debian Utilities						DEVSCRIPTS.CONF(5)