Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: Help with making the output of a command a variable
Top Forums Shell Programming and Scripting Help with making the output of a command a variable Post 303034613 by Defunct_Lizard on Tuesday 30th of April 2019 08:38:29 PM
Old 04-30-2019
Help with making the output of a command a variable
I'm writing a script that goes something like this:

Code:
#!/bin/bash

zenity --list --checklist --title="Choose Packages to Install" --width="1000" --height="400" \
--column="Select" --column="Package Name" --column="Description" \
GIMP=$( " " GIMP "GIMP is a free and open source photo editor."  \ )
if [ $GIMP == "GIMP" ]
then 
	sudo apt-get install $GIMP
fi

I want to open a dialog box with check boxes, package names, and descriptions. The box I have written is the first attached file.

I plan on adding other programs, but I have not gotten there yet.

The
Code:
" "

in the line
Code:
" " GIMP "Known as GIMP, GNU Image Manipulation Program is a free and open source photo editor." \

is for the first checkbox.

My main problem is the quotation marks at the end and beginning of the line (attached file #2). The quotation marks read in the wrong direction, and not how I want them to, having quotation marks inside of quotation marks?

Is there any way to fix this? Do I need to take a completely different approach?
Help with making the output of a command a variable-dialogbox10png
Help with making the output of a command a variable-zenity1png
Last edited by Defunct_Lizard; 04-30-2019 at 10:15 PM.. Reason: I did not intend for the attached files not to be alongside the text.
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Command output to a variable.

With cut -c 8-13 myfile, I am getting some numeric value. In my shell script I am trying to assign something like this, var=cut -c 8-13 myfile But at the time of execution I am getting -c is not found. If I dont assign, then script executes well. Can we not simply use the value from one... (8 Replies)
Discussion started by: videsh77
8 Replies

2. UNIX for Dummies Questions & Answers

redirect command output to variable

Hi, I am looking for a way to redirect the result from a command into a variable. This is the scenario. Using the find command I will be getting multiple records/lines back. Here is the command I am using: find /”path”/ -name nohup.out -print This now is giving me the paths and file... (1 Reply)
Discussion started by: hugow
1 Replies

3. Shell Programming and Scripting

get characters from output of a command in a variable

Hi, i have two questions, I am new to programming 1. I have an output of a command and i want to get some specific part of it in a variable. i am trying sr=`some comand xyz| grep 'Last Changed Rev:' | cut -c19-` now variable sr gets a end of line character at end. output of the command... (3 Replies)
Discussion started by: muaz
3 Replies

4. Shell Programming and Scripting

Assigning output of a command to variable

When I run time -p <command>, it outputs: real X.XX user X.XX sys X.XXwhere X.XX is seconds. How I can take just that first number output, the seconds of real time, and assign that to a variable? (9 Replies)
Discussion started by: jeriryan87
9 Replies

5. Programming

Command output into a variable

Hi, with this command: cu -l /dev/ttyACM0 -s 9600 > name.txt I put the output of the port in a txt Is posible to do the same (or similar) in a var directly, inside a C program? cu -l /dev/ttyACM0 -s 9600 > variable ? I have trying this withs pipes, but i dont know how to... (6 Replies)
Discussion started by: daaran
6 Replies

6. Shell Programming and Scripting

How to put output of one command into a variable

Hi, Let say I have these 3 files (state, list and myscript). I want to be able get the sample output like below when I run myscript. Any one know how to fix the code? TIA. ~~~~~~~~~~~~~~~ > cat /home/state CA > cat /home/list CA 100 50 20 AUS 120 61 10 > cat myscript... (6 Replies)
Discussion started by: joker_789us
6 Replies

7. Shell Programming and Scripting

Making script show command (e.g. copy) being executed and variable substitution?

When script is running you only see when some of the commands are not successfull. Is there a way to see which command are executed and to show the substitution of variables as every line is executed ? (3 Replies)
Discussion started by: gr0124
3 Replies

8. Shell Programming and Scripting

how to save an output of a command in a variable

Hi, in shell script, i have the command swstart -p which returns an output. i want to store the output of this command into a variable. how i can do that excerpt from the script #!/usr/bin/ksh # # # # Program: swstart -p # # Description: Starts the sentinels on Slave server ... (4 Replies)
Discussion started by: lookinginfo
4 Replies

9. UNIX for Advanced & Expert Users

ls output into a read command as a variable

I'm working on a short BASH script on my Ubuntu box that will run powerpoint scripts with MS Powerpoint Viewer 2007 via WINE. I can run the presentation when I run it manually but what i'd like to do is have the script look for the newest file then run it. #! /bin/sh # Start the newest... (2 Replies)
Discussion started by: binary-ninja
2 Replies

10. Shell Programming and Scripting

How to get the output of a ISQL command in a variable?

I am trying to run a query which returns a sum value(a number). I want to get it in a variable so that i can refer to that variable in different places. when i am running the following command variable=`isql -Uuser -Sserver -Ppassword 1> select sum(count(*)) from xyz..abc where clm_id... (2 Replies)
Discussion started by: Sharma331
2 Replies

LEARN ABOUT CENTOS

gimptool-2.0

GIMPTOOL-2.0(1) 					      General Commands Manual						   GIMPTOOL-2.0(1)

NAME

       gimptool-2.0 - script to perform various GIMPy functions

SYNOPSIS

       gimptool-2.0  [--prefix[=DIR]]  [--exec-prefix[=DIR]]  [--version]  [--help] [--quiet] [--silent] [-n] [--just-print] [--dry-run] [--recon]
       [--msvc-syntax]	[--bindir]  [--sbindir]  [--libexecdir]  [--datadir]  [--sysconfdir]   [--sharedstatedir]   [--localstatedir]	[--libdir]
       [--infodir]   [--mandir]  [--includedir]  [--gimpplugindir]  [--gimpdatadir]  [--libs]  [--libs-noui]  [--cflags]  [--cflags-noi]  [--build
       plug-in.c] [--build-strip plug-in.c] [--install plug-in.c] [--install-strip plug-in.c] [--install-admin plug-in.c] [--install-bin  plug-in]
       [--install-admin-strip	 plug-in.c]    [--install-bin-strip   plug-in]	 [--install-admin-bin	plug-in]   [--install-script   script.scm]
       [--install-admin-script script.scm] [--uninstall-bin plug-in]  [--uninstall-admin-bin  plug-in]	[--uninstall-script  script.scm]  [--unin-
       stall-admin-script script.scm]

DESCRIPTION

       gimptool-2.0 is a tool that can, among other things, build plug-ins or scripts and install them if they are distributed in one source file.

       gimptool-2.0 can also be used by programs that need to know what libraries and include-paths GIMP was compiled with. gimptool-2.0 uses pkg-
       config for this task. For use in Makefiles, it is recommended that you use pkg-config directly instead of calling gimptool-2.0.

OPTIONS

       gimptool-2.0 accepts the following options:

       --version
	       Print the currently installed version of GIMP on the standard output.

       --help  Print out the help blurb, showing commonly used commandline options.

       --quiet Run quietly without echoing any of the build commands.

       --silent
	       Run silently without echoing any of the build commands. Same as --quiet.

       -n      Test mode. Print the commands but don't actually execute them. Useful for making dry runs for testing.

       --just-print
	       Test mode. Print the commands but don't actually execute them. Same as -n.

       --dry-run
	       Test mode. Print the commands but don't actually execute them. Same as -n.

       --recon Test mode. Print the commands but don't actually execute them. Same as -n.

       --msvc-syntax
	       Useful on Windows. Outputs the compiler and linker flags in the syntax used by Microsoft's toolchain. Passed to the pkg-config com-
	       mand that does most of gimptool-2.0's work.

       --bindir
	       Outputs the bindir used to install the GIMP.

       --sbindir
	       Outputs the sbindir used to install the GIMP.

       --libexecdir
	       Outputs the libexecdir used to install the GIMP.

       --datadir
	       Outputs the datadir used to install the GIMP.

       --sysconfdir
	       Outputs the sysconfdir used to install the GIMP.

       --sharedstatedir
	       Outputs the sharedstatedir used to install the GIMP.

       --localstatedir
	       Outputs the localstatedir used to install the GIMP.

       --libdir
	       Outputs the libdir used to install the GIMP.

       --infodir
	       Outputs the infodir used to install the GIMP.

       --mandir
	       Outputs the mandir used to install the GIMP.

       --includedir
	       Outputs the includedir used to install the GIMP.

       --gimpdatadir
	       Outputs the actual directory where the GIMP data files were installed.

       --gimpplugindir
	       Outputs the actual directory where the GIMP plug-ins were installed.

       --build plug-in.c
	       Compile and link plug-in.c into a GIMP plug-in.

       --build-strip plug-in.c
	       Compile,link, and strip plug-in.c into a GIMP plug-in.

       --install plug-in.c
	       Compile, link, and install plug-in.c into the user's personal GIMP plug-in directory ($HOME/.gimp-2.8/plug-ins)

       --install-strip plug-in.c
	       Compile, link,strip, and install plug-in.c into the user's personal GIMP plug-in directory ($HOME/.gimp-2.8/plug-ins)

       --install-admin plug-in.c
	       Compile, link, and install plug-in.c into the system-wide GIMP plug-in directory (/usr/lib64/gimp/2.0/plug-ins)

       --install-bin plug-in
	       Install plug-in into the user's personal GIMP plug-in directory ($HOME/.gimp-2.8/plug-ins)

       --install-admin-bin plug-in
	       Install plug-in into the system-wide GIMP plug-in directory (/usr/lib64/gimp/2.0/plug-ins)

       --install-bin-strip plug-in
	       Install stripped plug-in into the user's personal GIMP plug-in directory ($HOME/.gimp-2.8/plug-ins)

       --install-admin-bin-strip plug-in
	       Install stripped plug-in into the system-wide GIMP plug-in directory (/usr/lib64/gimp/2.0/plug-ins)

       --install-script script.scm
	       Install script.scm into the user's personal GIMP script directory ($HOME/.gimp-2.8/scripts)

       --install-admin-script script.scm
	       Install script.scm into the system-wide GIMP script directory (/usr/share/gimp/2.0/scripts)

       --uninstall-bin plug-in
	       Uninstall plug-in from the user's personal GIMP plug-in directory ($HOME/.gimp-2.8/plug-ins)

       --uninstall-admin-bin plug-in
	       Uninstall plug-in from the system-wide GIMP plug-in directory (/usr/lib64/gimp/2.0/plug-ins)

       --uninstall-script script.scm
	       Uninstall script.scm from the user's personal GIMP script directory ($HOME/.gimp-2.8/scripts)

       --uninstall-admin-script script.scm
	       Uninstall script.scm from the system-wide GIMP script directory (/usr/share/gimp/2.0/scripts)

       --libs  Print the linker flags that are necessary to link a GIMP plug-in.

       --libs-noui
	       Print the linker flags that are necessary to link a GIMP plug-in, for plug-ins that do not require the GTK+ libraries.

       --cflags
	       Print the compiler flags that are necessary to compile a GIMP plug-in.

       --clags-noui
	       Print the compiler flags that are necessary to compile a GIMP plug-in for plug-ins that do not require the GTK+ libraries.

       --prefix=PREFIX
	       If specified, use PREFIX instead of the installation prefix that GIMP was built with when computing the output for the --cflags and
	       --libs options. This option is also used for the exec prefix if --exec-prefix was not specified.  This  option  must  be  specified
	       before any --libs or --cflags options.

       --exec-prefix=PREFIX
	       If  specified,  use  PREFIX  instead  of  the  installation  exec prefix that GIMP was built with when computing the output for the
	       --cflags and --libs options. This option must be specified before any --libs or --cflags options.

ENVIRONMENT

       CC      to get the name of the desired C compiler.

       CFLAGS  to get the preferred flags to pass to the C compiler for plug-in building.

       LDFLAGS to get the preferred flags for passing to the linker.

       LIBS    for passing extra libs that may be needed in the build process. For example, LIBS=-lintl .

       PKG_CONFIG
	       to get the location of the pkg-config program that is used to determine details about your glib, pango, gtk+ and gimp installation.

SEE ALSO

       gimp(1), gimprc(5), pkg-config(1)

AUTHORS

       gimptool was written by Manish Singh (yosh@gimp.org) and is based on gtk-config by Owen Taylor (owen@gtk.org).

       This man page was written by Ben Gertzfield (che@debian.org), and tweaked by Manish Singh (yosh@gimp.org), Adrian Likins  (adrian@gimp.org)
       and Marc Lehmann (pcg@goof.com>).

GIMP Manual Pages						  Version 2.8.10						   GIMPTOOL-2.0(1)
All times are GMT -4. The time now is 06:45 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy