Passing Global Shell variables to awk Post: 302847185

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Passing shell variables to awk program..

Hello, Can we pass shell variables like $PATH etc. to a awk program part for example, awk ' { fieldValue=$PATH .... }' file

2. Shell Programming and Scripting

Passing awk Variables

I am trying to pass the results from a variable gathered from awk, however when I echo the 'PARSE' and 'SUB', the response is blank. This is my command. awk -F= '/Unit/''{ PARSE=substr($2,1,5) ; SUB=substr($2,1,1) }' inputfile.lst Is this a kind of valid attempt or am I obligated to declare...

3. UNIX for Dummies Questions & Answers

How to declare global variables for shell script

Hi, I do have some variables accessed in more than one script. I want to have those variables in a command file anduse them. Something like a header file that we use in C programs. I dont want to set them as environment variables. Is there any other option, like header file in scripting ?? ...

4. Solaris

How to access ENV variables of non global zones in global zone???

Hi Guys, My requirement is I have file called /opt/orahome/.profile in non global zone. PATH=/usr/bin:/usr/ucb:/etc:/usr/sbin:/usr/local/bin:/usr/openwin/bin:. export PATH PS1="\${ORACLE_SID}:`hostname`:\$PWD$ " export PS1 EDITOR=vi export EDITOR ENV=/opt/orahome/.kshrc export ENV...

5. UNIX for Dummies Questions & Answers

Passing Shell Variables to an awk command

Hello, I have two files File1 & File2. File1 76 135 136 200 250 345 .... File2 1 24 1 35 1 36 1 72 .... I want to get all the values form File2 corresponding to the range in File 1 and feed it to a program. Is the code below right? Can I pass shell variables to awk in this...

6. Shell Programming and Scripting

Passing awk variables to shell

Hi. I need to parse file and assign some values to variables, right now i do like below MYHOMEDIR=`awk '/Home/ {print $NF}' output.txt` MYSHELL=`awk '/Shell/ {print $NF}' output.txt` PRGRP=`awk '/Primary/ {print $NF}' output.txt` SECGRP=`awk '/Second/ {print $NF}' output.txt` In this...

7. Shell Programming and Scripting

ksh passing to awk multiple dyanamic variables awk -v

Using ksh to call a function which has awk script embedded. It parses a long two element list file, filled with text numbers (I want column 2, beginning no sooner than line 45, that's the only known thing) . It's unknown where to start or end the data collection, dynamic variables will be used. ...

8. Shell Programming and Scripting

Problem in Global variables in shell script

hi, i have a shell script which calls another shell which in turn calls another shell script. Main_shell_script.sh echo "In Main_shell_script.sh" FILENAME="original.txt" # LINE 1 DST_FILENAME=$FILENAME # LINE 2 echo "FILENAME = {$FILENAME}" echo "DST_FILENAME =...

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

10. Shell Programming and Scripting

Awk: passing shell variables through and extracting text

Hello, new to the forums and to awk. Glad to be here. :o I want to pass two shell (#!/bin/sh) variables through to awk and use them. They will determine where to start and stop text extraction. The code with the variables hard-coded in awk works fine; the same code, but with the shell...

LEARN ABOUT MOJAVE

tklib_history

history(n)					       Provides a history for Entry widgets						history(n)

__________________________________________________________________________________________________________________________________________________

NAME

       history - Provides a history for Entry widgets

SYNOPSIS

       package require Tcl  8.4

       package require Tk  8.4

       package require history	?0.1?

       ::history::init pathName ?length?

       ::history::remove pathName

       ::history::add pathName text

       ::history::get pathName

       ::history::clear pathName

       ::history::configure pathName option ?value?

       bell

_________________________________________________________________

DESCRIPTION

       This package provides a convenient history mechanism for Entry widgets.	The history may be accessed with the up and down arrow keys.

       ::history::init pathName ?length?
	      Arranges	to  remember  the  history of the named Entry widget. An optional length determines the number of history entries to keep.
	      This may be changed later with ::history::configure. History entries must be added with the ::history::add command before  they  can
	      be seen.

       ::history::remove pathName
	      Forgets all history entries for the Entry pathName and removes the history bindings.

       ::history::add pathName text
	      This command is used to add history entries to an Entry that has previously had ::history::init called on it. This command should be
	      called from your Entry handler with the contents of the entry (or whatever you wish to add to the history).

       ::history::get pathName
	      This command returns a list containing the history entries for the Entry pathName

       ::history::clear pathName
	      This command clears the history list for the named Entry.

       ::history::configure pathName option ?value?
	      This command queries or sets configuration options. Currently the options recognized are length and alert. Setting the length deter-
	      mines the number of history entries to keep for the named Entry. Alert specifies the command to run when the user reaches the end of
	      the history, it defaults to

       bell

       entry .e
       bind .e <Return> [list ProcessEntry %W]
       ::history::init .e
       pack .e

       proc ProcessEntry {w} {
	   set text [$w get]
	   if {$text == ""} { return }
	   ::history::add $w $text
	   puts $text
	   $w delete 0 end
       }

KEYWORDS

       entry, history

history 								0.1								history(n)