Sponsored Content
Top Forums Shell Programming and Scripting Pass shell variable to gnuplot Post 302634501 by LeePhillips on Thursday 3rd of May 2012 12:10:32 PM
Old 05-03-2012
Try using backquotes instead of the $() syntax. Like this:
var=`command`



Lee Phillips
----------------
gnuplot Cookbook
Available on Amazon
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

How to Pass variable to shell Script

Hi , i am beginner to Unix, I have one small script which execute java programme,it has java command input output structure . Right now i have given Input output structure manually that is on same directory, now how can i pass that by commandline #!/bin/sh java Classjava input.txt... (5 Replies)
Discussion started by: sam70
5 Replies

2. UNIX for Dummies Questions & Answers

How to pass Shell script variable to awk

Hi, I have a shell script with an ambedded awk script. i need to pass a script variable to the awk script. Please help. Thanks in advance Himani (3 Replies)
Discussion started by: HIMANI
3 Replies

3. Shell Programming and Scripting

Is it possible to pass variable from awk to shell script

Hello experts, can I return a value from gawk to a shell script ? My script as follows, #Here I want the num value to shell script so that I can use later gawk ' { split($0,num,","); print num }' gawk -v no=$number '{print no}' file1 ... (3 Replies)
Discussion started by: user_prady
3 Replies

4. Shell Programming and Scripting

Is it possible to pass variable from awk to shell back

I am passing a varaible to from Shell to awk then I am doing some maniplation for that variable inside awk. I want that maniplated variable value back to shell , Is this possible .Please let me know. (12 Replies)
Discussion started by: unishiva
12 Replies

5. UNIX for Dummies Questions & Answers

How to pass a variable from shell to awk

I know this topic has been dealt with previously, but the solutions I've seen don't work for me apparently. I need to pass a variable defined in the shell to one in awk: $ echo $var1 3 $ cat aaa aaa 1 bbb 2 ccc 3 ddd 4 eee 5I've tried this, without success: $ awk... (2 Replies)
Discussion started by: metaltree
2 Replies

6. Shell Programming and Scripting

How to pass variable with spaces from shell to expect?

I need call expect script from shell script and pass values some of which could contain space. How to make expect to treat such values as one variable? (1 Reply)
Discussion started by: urello
1 Replies

7. Shell Programming and Scripting

How to pass nawk variable to shell within the same script?

Hi All, I tried googling but so far no luck, can someone tell me how pass the variable value used inside the nawk command to shell. In the below script i get the value of $c (without color: Total Executed: " c ") but the printf which is outside the nawk command doesn't print the value or it... (4 Replies)
Discussion started by: Optimus81
4 Replies

8. Shell Programming and Scripting

Pass awk array variable to shell

Hi, all suppose I have following myfile (delimited by tab) aa bb cc dd ee ffand I have following awk command: awk 'BEGIN{FS="\t"}{AwkArrayVar_1=$1;AwkArrayVar_2=$2};END{for(i=0; i<NR; i++) print i, AwkArrayVar_1, AwkArrayVar_2,}' myfileMy question is: how can I assign the awk array... (7 Replies)
Discussion started by: littlewenwen
7 Replies

9. UNIX for Dummies Questions & Answers

Pass shell Variable to awk

Hello, May i please know how do i pass the shell variable to awk expression in the below script. It is returning null #!/bin/bash UNINUM=720922 UNINUM_DESC=`awk -F'|' -v UNINUM=$2 '/UNINUM/ {print $4}' datafile` echo $UNINUM_DESC datafile 4|First|720194|asdasdad 4|First|720735|asdasdsa... (8 Replies)
Discussion started by: Ariean
8 Replies

10. Shell Programming and Scripting

How to pass variable from awk script to shell?

Hi, Please need to print the Rej variable outsite the awk script which is given below...please advised how to achieve it. #!/bin/bash echo "Enter DMU Pipe delimited File name for the Feed to be validated" read DMU_File echo "Enter Pre-DMU File name for the Feed" read Predum_file ... (3 Replies)
Discussion started by: pelethangjam
3 Replies
PLOTCHANGELOG(1)					      General Commands Manual						  PLOTCHANGELOG(1)

NAME
plotchangelog - graph debian changelogs SYNOPSIS
plotchangelog [options] changelog ... DESCRIPTION
plotchangelog is a tool to aid in visualizing a Debian changelog. The changelogs are graphed with gnuplot(1) , with the X axis of the graph denoting time of release and the Y axis denoting the debian version number of the package. Each individual release of the package is repre- sented by a point, and the points are color coded to indicate who released that version of the package. The upstream version number of the package can also be labeled on the graph. Alternatively, the Y axis can be configured to display the size of the changelog entry for each new version. Or it can be configured to display approximately how many bugs were fixed for each new version. Note that if the package is a debian-specific package, the entire package version will be used for the Y axis. This does not always work perfectly. READING THE GRAPH
The general outline of a package's graph is typically a series of peaks, starting at 1, going up to n, and then returning abruptly to 1. The higher the peaks, the more releases the maintainer made between new upstream versions of the package. If a package is debian-only, it's graph will just grow upwards without ever falling (although a bug in this program may cause it to fall sometimes, if the version number goes from say, 0.9 to say, 0.10 - this is interpreted wrong..) If the graph dips below 1, someone made a NMU of the package and upgraded it to a new upstream version, thus setting the debian version to 0. NMU's in general appear as fractional points like 1.1, 2.1, etc. A NMU can also be easily detected by looking at the points that repre- sent which maintainer uploaded the package -- a solitary point of a different type than the points before and after it is typically a NMU. It's also easy to tell by looking at the points when a package changes maintainers. OPTIONS
-l, --linecount Instead of using the debian version number as the Y axis, use the number of lines in the changelog entry for each version. Cannot be used together with --bugcount. -b, --bugcount Instead of using the debian version number as the Y axis, use the number of bugs that were closed by each changelog entry. Note that this number is obtained by searching for "#dddd" in the changelog, and so it may be inaccurate. Cannot be used together with --linecount. -c, --cumulative When used together with either --bugcount or --linecount, graphs the cumulative count rather than the count in each individual changelog entry. -v, --no-version Do not show upstream version labels. Useful if the graph gets too crowded. -m, --no-maint Do not differentiate between different maintainers of the package. -s file, --save=file Save the graph to file in postscript format instead of immediately displaying it. -u, --urgency Use larger points when displaying higher-urgency package uploads. --verbose Output the gnuplot script that is fed into gnuplot (for debugging purposes). -gcommands, --gnuplot=commands This allows you to insert gnuplot(1) commands into the gnuplot script that is used to generate the graph. The commands are placed after all initialization but before the final plot command. This can be used to override the default look provided by this program in arbitrary ways. You can also use things like "set terminal png color" to change the output file type, which is useful in conjunc- tion with the -s option. --help Show a usage summary. --version Display version, author and copyright information. --noconf, --no-conf Do not read any configuration files (see below). changelog ... The changelog files to graph. If multiple files are specified they will all be display on the same graph. The files may be com- pressed with gzip. Any text in them that is not in Debian changelog format will be ignored. CONFIGURATION VARIABLES
The two configuration files /etc/devscripts.conf and ~/.devscripts are sourced by a shell in that order to set configuration variables. The --no-conf option can be used to prevent reading these files. Environment variable settings are ignored when these configuration files are read. The currently recognised variables are: PLOTCHANGELOG_OPTIONS This is a space-separated list of options to always use, for example -l -b. Do not include -g or --gnuplot among this list as it may be ignored; see the next variable instead. PLOTCHANGELOG_GNUPLOT These are gnuplot commands which will be prepended to any such commands given on the command line. SEE ALSO
devscripts.conf(5). AUTHOR
Joey Hess <joey@kitenet.net> DEBIAN
Debian Utilities PLOTCHANGELOG(1)
All times are GMT -4. The time now is 03:02 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy