03-23-2012
getting first two characters of variable
From a shell script, I'm trying to get the first two characters of an environment variable.
If I type at the command promot:
XX=`echo $MYVAR | cut -c1-2`
echo $XX
It works just fine
However, if I execute the exact same thing from a shell script, I get:
cut: you must specify a list of bytes, characters, or fields
Try `cut --help' for more information.
Thank you.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi ,
I need to get the specified word from the variable.can some one help me out in this ?
input=ASD34567P
i need to get the value as :
output1=34567
So i need to ignore the last character and get the remaining values.
THANKS IN ADVANCE. (6 Replies)
Discussion started by: ithirak17
6 Replies
2. UNIX for Dummies Questions & Answers
Hi All,
I have scenario as below,
I want to cut the characters and store it variable2.. and want to display the variable2.. as shown below...
eg: the size may differs , i am show just an example.....
numbers are not fixed in variable1..i want to extract characters and... (1 Reply)
Discussion started by: G.K.K
1 Replies
3. Shell Programming and Scripting
I have a variable var which contains "ABCDEFDH"
Now I have to remove the first 4 characters that is "ABCD"
so my variable should contain only "DEFH"
plzz tell me how to do that .
i am using bash shell (1 Reply)
Discussion started by: cynosure2009
1 Replies
4. Shell Programming and Scripting
I'm using a shell script to get user input with this command:
read UserInput
I would then like to take the "UserInput" variable and strip out all of the following characters, regardless of where they appear in the variable or how many occurrences there are:
\/":|<>+=;,?*@
I'm not sure... (5 Replies)
Discussion started by: nrogers64
5 Replies
5. Shell Programming and Scripting
I need to cut the last seven characters of a variable length variable. The variable may be 7 characters or 70. I need to always be able to grab the last 7 characters. I looked at the cut command but it always seems to want to start at the beginning of a line, not the end and count backwards.
... (5 Replies)
Discussion started by: kblawson14
5 Replies
6. Shell Programming and Scripting
I am trying to store a string value to a temporary variable within my script. When I run the command manually it returns the expected value, but from the script an additional "\r" is at the end.
tCurrentStatus=`cat ${tPC_status} | grep 'Current status' | awk '{print $NF}'`
output:
cat... (1 Reply)
Discussion started by: jxrst
1 Replies
7. Shell Programming and Scripting
I have a script with a $PASSWORD variable. I unset it right after using it, just to minimize the chance it could be left around for a snooper. That worked just fine... until I used a password with a value of "P@ssw0rd" Now, unset (even with -f, even with the variable enquoted) tells me: unset:... (1 Reply)
Discussion started by: jnojr
1 Replies
8. Shell Programming and Scripting
My variable is something like:
f="/Volumes/VERVE/MOOTON_CALL/01_shots/XX/xx0195/Projects/program/rs0195_v400001.aep"
I use ${f:63:6} to call "rs0195" as characters counted from the left, but it'd be so much easier to count from the right.
If ${f:95:10} counts from the left, what would... (2 Replies)
Discussion started by: scribling
2 Replies
9. Shell Programming and Scripting
Hi all
I have a variable name as below
runbatch=FCSTworLOADfx_CYR
Now i need to search for FCST in this variable and run a program
I am doing like this but it is failing
if ; then ****RUN PROGRAM**
Please help
DJ
Please use CODE tags when displaying sample input,... (3 Replies)
Discussion started by: Hypesslearner
3 Replies
10. Shell Programming and Scripting
Debian 9 64x - LXDE
How can i disable escape sequences in a variable?
#!/bin/bash
#mainscript
. "./links.bash"
echo "$red_start This text should be red $color_end"#!/bin/bash
#links.bash
#colors
red_start="\eOutput that i get:
\e
Output expected:
This text should be... (5 Replies)
Discussion started by: int3g3r
5 Replies
LEARN ABOUT OPENDARWIN
script
SCRIPT(1) BSD General Commands Manual SCRIPT(1)
NAME
script -- make typescript of terminal session
SYNOPSIS
script [-a] [-k] [-q] [-t time] [file [command ...]]
DESCRIPTION
The script utility makes a typescript of everything printed on your terminal. It is useful for students who need a hardcopy record of an
interactive session as proof of an assignment, as the typescript file can be printed out later with lpr(1).
If the argument file is given, script saves all dialogue in file. If no file name is given, the typescript is saved in the file typescript.
If the argument command ... is given, script will run the specified command with an optional argument vector instead of an interactive shell.
Options:
-a Append the output to file or typescript, retaining the prior contents.
-k Log keys sent to program as well as output.
-q Run in quiet mode, omit the start and stop status messages.
-t time Specify time interval between flushing script output file. A value of 0 causes script to flush for every character I/O event. The
default interval is 30 seconds.
The script ends when the forked shell (or command) exits (a control-D to exit the Bourne shell (sh(1)), and exit, logout or control-d (if
ignoreeof is not set) for the C-shell, csh(1)).
Certain interactive commands, such as vi(1), create garbage in the typescript file. The script utility works best with commands that do not
manipulate the screen. The results are meant to emulate a hardcopy terminal, not an addressable one.
ENVIRONMENT
The following environment variable is utilized by script:
SHELL If the variable SHELL exists, the shell forked by script will be that shell. If SHELL is not set, the Bourne shell is assumed. (Most
shells set this variable automatically).
SEE ALSO
csh(1) (for the history mechanism).
HISTORY
The script command appeared in 3.0BSD.
BUGS
The script utility places everything in the log file, including linefeeds and backspaces. This is not what the naive user expects.
It is not possible to specify a command without also naming the script file because of argument parsing compatibility issues.
When running in -k mode, echo cancelling is far from ideal. The slave terminal mode is checked for ECHO mode to check when to avoid manual
echo logging. This does not work when in a raw mode where the program being run is doing manual echo.
BSD
June 6, 1993 BSD