Making lots of assumptions and having no idea why you have an empty here-document feeding data into a tr command that is also reading from a pipeline nor why you think you need a case insensitive search while using egrep on input that has already been converted to uppercase only by two preceding tr commands, you might want to try:
This assumes that you don't want to convert tabs and sequences of one or more spaces and tabs in the expansion of $environment to single spaces and that the first character of the expansion of $environment is not a minus sign immediately after any leading spaces and tabs have been removed. I also assume that there are backslash escape sequences embedded in the expansion of $environment or you would have just used:
instead of:
and that you are using a version of bash on a system where echo expands backslash escapes by default.
Hi,
When I run the below shell script I'm getting the error " syntax error near unexpected token `"
Script:
REM :: File Name : Refresh_OTL.bat
REM :: Parameters : %1 - Region
REM :: : %2 - Cube Type
REM :: :
REM :: Notes :
REM ============================== set ENVIRONMENT... (2 Replies)
Hi all,
Here is a simple script that is working in one server and is giving a syntax error in other server. Can somebody help me ?
#!/bin/bash
# ftp files
done < $file
errors:
I tried..with no success:
if ; then (21 Replies)
Hi,
I am running the following script through cygwin and getting below mentioned error.
*******************************************
#!/bin/sh
# constants
WORK_DIR="deploy"
INFOFILE="deploy.info"
INTROFILE="Intro.sh"
CMGMT_PKG="com.kintana.cmgmt.deploy"
DEPLOY_PREFIX="mitg"
... (2 Replies)
hi! just want to seek help on this error: syntax error near unexpected token 'do
this is my script
# !/bin/sh
#
for y in 27 25
do
exemmlmx -c "ZEEI;" -n XRT$y >> blah
done
what can be wrong? thanks! (6 Replies)
Hi all,
This is a script which converts hex to bin. However am finding an error while executing
syntax error near unexpected token `='
`($hexfile, $binfile) = @ARGV;'
I am running using ./fil.pl <hexfile> <binfile>
###################################################
#
# this script... (3 Replies)
What do I do here?
#!/bin/bash
payload=-1 AND 1=IF(21,BENCHMARK(5000000,MD5(CHAR(115,113,108,109,97,112))),0)#
hash=`echo -n $payload md5sum tr -d 'n' sed 'ss-sg' md5sum tr -d 'n' sed 'ss-sg'`
curl --data cs2=chronopay&cs1=$payload&cs3=$hash&transaction_type=rebill... (2 Replies)
Hi all,
I have a simple script that doesn't work somehow. I can't seem to be spotting the cause of the malfunction.
count=$((1))
for item in `cat test1.txt`
printf %s `sed -n $((count))p test2.txt` > test3.txt
count=$((count+1))
do
something
done
I get ;
./why.sh: line 3:... (14 Replies)
howdy,
so I'm make a plugin work for Nagios, and the commandline is:
/usr/lib/nagios/plugins/check_mssql -H MySQLServerName -u MySqlAccountName -p MyPassword(#XXXXX -d MyDatabaseName
it is barfing with:
bash: syntax error near unexpected token `('
Thoughts?
Do I have to wrap something... (2 Replies)
Dears,
While executing the below script im getting the error at line 30. Please let me know what changes to be done to fix this.
test.sh: line 30: syntax error near unexpected token `done'
test.sh: line 30: ` done '
#!/bin/sh
# Rev. PA1
# author: eillops
# date: 26-04-2018
#
#... (1 Reply)
detect_mouse_mvt.sh
/home/andy/bin/detect_mouse_mvt.sh: line 4: syntax error near unexpected token `('
/home/andy/bin/detect_mouse_mvt.sh: line 4: `fh = file('/dev/input/mice')'
#!/bin/bash
#
#
fh = file('/dev/input/mice')
while True:
fh.read(3)
print 'Mouse... (15 Replies)
Discussion started by: drew77
15 Replies
LEARN ABOUT HPUX
newform
newform(1) General Commands Manual newform(1)NAME
newform - change or reformat a text file
SYNOPSIS
[file]...
DESCRIPTION
reads lines from the named files, or standard input if no input file is named, and reproduces the lines on standard output. Lines are
reformatted in accordance with command line options in effect.
Command line options can appear in any order, can be repeated, and can be intermingled with the optional files. Command line options are
processed in the order specified. This means that option sequences such as yield results different from Options are applied to all files
on the command line.
Options
recognizes the following options:
Same as except characters are appended to the end of a line.
Truncate n characters from the beginning of the line when the line length is greater than the effective line length (see The
default is to truncate the number of characters necessary to obtain the effective line length. The default value is
used when with no n is used. This option can be used to delete the sequence numbers from a COBOL program as follows:
The must be used to set the effective line length shorter than any existing line in the file so that the option is
activated.
Change the prefix/append character to
k. The default character for k is a space.
Same as except that characters are truncated from the end of the line.
Write the tab specification format line on the standard output
before any other lines are output. The tab specification format line which is printed will correspond to the format
specified in the option. If no option is specified, the line which is printed contains the default specification of
Input tab specification:
expands tabs to spaces, according to the tab specifications given. The tabspec recognizes all tab specification
forms described in tabs(1). In addition, tabspec can be in which assumes that the tab specification is to be found
in the first line read from the standard input (see fspec(4)). If no tabspec is given, tabspec defaults to A tabspec
of expects no tabs; if any are found, they are treated as
Set the effective line length to
n characters. If n is not entered, defaults to 72. The default line length without the option is 80 characters.
Note that tabs and backspaces are treated as single characters (use to expand tabs to spaces).
Output tab specification:
replaces spaces with tabs, according to the tab specifications given. The tab specifications are the same as for If
no tabspec is given, tabspec defaults to A tabspec of means that no spaces will be converted to tabs on output.
Prefix n characters (see to the beginning of a line when the line length is less than the effective line length. The
default is to prefix the number of characters necessary to obtain the effective line length.
Shear off leading characters on each line up to the first tab and
place up to 8 of the sheared characters at the end of the line. If more than 8 characters (not counting the first
tab) are sheared, the eighth character is replaced by a and any characters to the right of it are discarded. The
first tab is always discarded.
An error message and program exit occur if this option is used on a file without a tab on each line. The characters
sheared off are saved internally until all other options specified are applied to that line. The characters are then
added at the end of the processed line.
For example, to convert a file with leading digits, one or more tabs, and text on each line, to a file beginning with
the text, all tabs after the first expanded to spaces, padded with spaces out to column 72 (or truncated to column
72), and the leading digits placed starting at column 73, the command would be:
RETURN VALUE
returns one of the following values:
No errors encountered.
An error occurred.
DIAGNOSTICS
All diagnostics are fatal.
was called with a bad option.
There was no tab on one line.
Self-explanatory.
A line exceeds 512 characters
after being expanded in the internal work buffer.
A tab specification is incorrectly formatted,
or specified tab stops are not ascending.
A tabspec read from a file (or standard input) must not contain a tabspec referencing another file (or standard input).
WARNINGS
normally only keeps track of physical characters; however, for the and options, keeps track of backspaces in order to line up tabs in the
appropriate logical columns.
does not prompt the user if a tabspec is to be read from the standard input (by use of or
If the option is used, and the last option specified was and was preceded by either a or a the tab specification format line will be incor-
rect.
SEE ALSO csplit(1), tabs(1), fspec(4).
newform(1)