Case Nesting Post: 302358933

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

lower case to upper case string conversion in shell script

How can convert a Lower case variable value to an upper case in the kron shell script.

2. UNIX for Dummies Questions & Answers

zip nesting empty folders

I'm using the following command to zip a project file, but when it finishes, the resulting zip file contains all the directories above the file I wanted zipped, myapp.app, each one empty until you get to the actual app. zip -r myapp.app.zip ...

3. Shell Programming and Scripting

Script needed to select and delete lower case and mixed case records

HELLO ALL, URGENTLY NEEDED A SCRIPT TO SELECT AND DELETE LOWER AND MIXED CASE RECORDS FROM A COLUMN IN A TABLE. FOR EXAMPLE : Table name is EMPLOYEE and the column name is CITY and the CITY column records will be: Newyork washington ...

4. UNIX for Dummies Questions & Answers

Isn't a shell found on a beach? Need help nesting if's or loops.

As of a week ago i thought a shell was somthing found on a beach. I'm a virgin when it comes to scripting and i'm having a really bad time here. What i need to do is prompt for a group number grep the /etc/groups to get the GID and name if it exists i want to prompt the user for...

5. Shell Programming and Scripting

How to ignore STDERR when nesting commands?

I have a pel script running as root that needs to read the contents of a file on a remote system, I have an ssh trust relationship as a particular user but not as root. I then need to write back out to that file again to change it's content a bit. On the surface this seemed really easy but...

6. Shell Programming and Scripting

BASH Varible nesting and user input

Well, I think I've managed to take two different issues and conglomerate them into and embarrasing mess. #!/bin/bash # Set some variables dir1=/path/that/isnt/variable/$variabledir/dir/ dir2=/path/that/isnt/variable/$variabledir/important/"$variabledir"-subdirectory/path/ echo "Gimme...

7. Shell Programming and Scripting

Nesting backticks

I'm trying to make a dialog window that prints the output of grep that takes the output of find. Unfortunately my nested backticks don't work. Here is the dialog window: dialog --stdout --title "test" --backtitle "test" --msgbox "Test:\n `grep -l "${tablica}" `find $string``" 16 60I think I...

8. Shell Programming and Scripting

Bash - Nesting if statement in for loop

I have the basic command written in bash for element in 1 2 do if ]; then set el = "t" else set el = "p" fi done but i get the following error syntax error near unexpected token `for' ` for element in 1 2' What should i do differently?

9. Shell Programming and Scripting

Issue nesting variables in csh.

The variables given are already defined ($file1-$file3, $obsid1-$obsid3, and $n=3). When I go to run the code, the terminal outputs "Missing }." I believe the error is with the nesting of variables. It would save a lot of time getting this while loop working. set i = 1 while (${i} <=...

LEARN ABOUT DEBIAN

sdcdb

SDCDB(1)						      General Commands Manual							  SDCDB(1)

NAME

       sdcdb - Source debugger for SDCC

SYNOPSIS

       sdcdb [options] filename

WARNING

       The information in this man page is an extract from the full documentation of SDCC, and is limited to the meaning of the options.

       For complete and current documentation, refer to the SDCC Compiler User Guide.

DESCRIPTION

       sdcdb is a source debugger for SDCC. It uses ucSim to execute the program, the programm execution is controlled by the debugger.

       The  command  interface for the debugger has been deliberately kept as close the GNU debugger gdb, as possible. This will help the integra-
       tion with existing graphical user interfaces (like ddd, xxgdb or xemacs) existing for the GNU debugger.

STARTING THE DEBUGGER

       The debugger can be started using the following command line (Assume the file you are debugging has the file name foo):

       sdcdb foo

       The debugger will look for the following files:

       foo.c   - the source file.
       foo.cdb - the debugger symbol information file.
       foo.ihx - the intel hex format object file.

OPTIONS

       -directory=<source file directory>
	      This option can used to specify the directory search list. The debugger will look into the directory list specified for source,  cdb
	      & ihx files. The items in the directory list must be separated by ':', e.g. if the source files can be in the directories /home/src1
	      and /home/src2, the -directory option should be -directory=/home/src1:/home/src2. Note there can be no spaces in the option.

       -cd <directory>
	      Change to the <directory>.

       -fullname
	      Used by GUI front ends.

       -cpu <cpu-type>
	      This argument is passed to the simulator. Please see the simulator docs for details.

       -X <Clock frequency>
	      This option is passed to the simulator. Please see the simulator docs for details.

       -s <serial port file>
	      This option is passed to simulator. Please see the simulator docs for details.

       -S <serial in,out>
	      This argument is passed to simulator. Please  see the simulator docs for details.

COPYING

       The entire source code for the debugger is distributed under GNU General Public License.

SEE ALSO

       sdcc(1), ucsim(1), s51(1), savr(1), sz80(1).

AUTHOR

       This manual page was written by Aurelien Jarno <aurel32@debian.org>, for the Debian GNU/Linux system (but may be used by others).

																	  SDCDB(1)