Sponsored Content
Full Discussion: AWK Syntax errors :/
Top Forums Shell Programming and Scripting AWK Syntax errors :/ Post 74237 by vgersh99 on Wednesday 8th of June 2005 01:45:04 PM
Old 06-08-2005
works just fine on Solaris 8
Make sure you have no hidden control characters anywhere in the file - in particular the first line.
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

awk errors

Hello, Can you please let me know how to find all lines that don't begin with pattern1, pattern2, pattern3 and pattern4? Here is my awk script that gives an error. awk 'BEGIN { NAME="$FILE" GSNO=0 } /^ISA/ { FIRST=$0; LAST="IEA*1*" +... (4 Replies)
Discussion started by: billy5
4 Replies

2. Shell Programming and Scripting

perl version for syntax errors

All, Does it matter what perl verios your running when you get syntax errors? on version 5.6.1 the code works fine, but on 5.8.0 the code gets errors? #!/usr/bin/perl #use strict; #use warnings; my $mess = 'messages'; my $mess1 = 'messages.1'; my $mess2 = 'messages.2'; my... (13 Replies)
Discussion started by: bigben1220
13 Replies

3. Shell Programming and Scripting

PERL Syntax Errors

Hi, I am a newbie to PERL and working on a script. When running it I get a lot of compilation errors. The actual command in the program (which is within a case structure) is given below # This gives the actual count of inquires from a log file (It works fine when I type this on the... (2 Replies)
Discussion started by: nurani
2 Replies

4. UNIX for Dummies Questions & Answers

I dont really think that the math header has syntax errors

Hi, Mini:Evaluator develop$ make bison -d grammar.y grammar.y: conflicts: 24 shift/reduce flex rules.l cc -0 -o Evaluator grammar.tab.c lex.yy.c -ly -ll -lm In file included from grammar.y:3: /usr/include/architecture/i386/math.h:310: error: syntax error before numeric constant... (1 Reply)
Discussion started by: tcerka
1 Replies

5. Shell Programming and Scripting

line count with if /else - syntax errors

this is the script: ps -ef|grep "x_jobstat 10 v001" > jobstatv001.txt ps -ef |grep "x_jobserver 10 v001" >> jobstatv001.txt #Sample text - each line preceded by 4 spaces # root 133064 102986 0 08:49:28 pts/6 0:00 grep x_jobstat 10 v001 # root 137550 1 0 Nov 08 - 0:28... (6 Replies)
Discussion started by: kwalkner
6 Replies

6. Emergency UNIX and Linux Support

Seek help on shell script syntax errors

I want to delete archivelog files that has been archived and applied from primary database to standby database. This piece of script is working in Linux server. However, I copy it to Unix server with tiny modification. It won't work and generate the error message. I have checked code carefullt... (8 Replies)
Discussion started by: duke0001
8 Replies

7. Programming

Errors in Perl when using awk command

Hi Guys, Hope everyone is fine :) I have this code below: #!/usr/bin/perl $num_of_files=`ls | grep -v remover | wc -l`; $remover=`ls -lrt | grep -v total | grep -v remover | head -1 | awk '{print $8}' | rm \`xargs\``; if ($num_of_files>3) { system ($remover); } When I... (3 Replies)
Discussion started by: rymnd_12345
3 Replies

8. Shell Programming and Scripting

Converting from Linux bash (GNU) to Solaris script syntax errors

Original script written on CentOS 6.3 with GNU bash 4.1.2 Destination system is Solaris 9 with GNU bash 2.05 (not changeable by me) I have a script written on the linux side but now we need to provide a version to another site that "doesn't like linux". I've been going through changing the ] or... (13 Replies)
Discussion started by: oly_r
13 Replies

9. Homework & Coursework Questions

Help with shell scrip syntax errors

Use and complete the template provided. The entire template must be completed. If you don't, your post may be deleted! 1. The problem statement, all variables and given/known data: This script will analyse the channels.txt e registrations.txt and it will allow to mage the channels and the... (9 Replies)
Discussion started by: Demas
9 Replies

10. Shell Programming and Scripting

Finding latest file in dir but getting syntax errors

I believe there are couple of syntax issues in my script, couldn't find them :( can someone help me with fixing it to make it work. cd /abcde/ #get the latest filename excluding subdirs filename=`ls -ltr | grep ^- | tail -1 | awk '{print $8}'` #get system date and file timestamp and... (3 Replies)
Discussion started by: simpltyansh
3 Replies
VIS(1)							    BSD General Commands Manual 						    VIS(1)

NAME
vis -- display non-printable characters in a visual format SYNOPSIS
vis [-cbflnostw] [-F foldwidth] [file ...] DESCRIPTION
The vis utility is a filter for converting non-printable characters into a visual representation. It differs from 'cat -v' in that the form is unique and invertible. By default, all non-graphic characters except space, tab, and newline are encoded. A detailed description of the various visual formats is given in vis(3). The options are as follows: -b Turns off prepending of backslash before up-arrow control sequences and meta characters, and disables the doubling of backslashes. This produces output which is neither invertible or precise, but does represent a minimum of change to the input. It is similar to ``cat -v''. -c Request a format which displays a small subset of the non-printable characters using C-style backslash sequences. -F Causes vis to fold output lines to foldwidth columns (default 80), like fold(1), except that a hidden newline sequence is used, (which is removed when inverting the file back to its original form with unvis(1)). If the last character in the encoded file does not end in a newline, a hidden newline sequence is appended to the output. This makes the output usable with various editors and other utilities which typically do not work with partial lines. -f Same as -F. -l Mark newlines with the visible sequence '$', followed by the newline. -n Turns off any encoding, except for the fact that backslashes are still doubled and hidden newline sequences inserted if -f or -F is selected. When combined with the -f flag, vis becomes like an invertible version of the fold(1) utility. That is, the output can be unfolded by running the output through unvis(1). -o Request a format which displays non-printable characters as an octal number, ddd. -s Only characters considered unsafe to send to a terminal are encoded. This flag allows backspace, bell, and carriage return in addi- tion to the default space, tab and newline. -t Tabs are also encoded. -w White space (space-tab-newline) is also encoded. SEE ALSO
unvis(1), vis(3) HISTORY
The vis command appeared in 4.4BSD. BUGS
Due to limitations in the underlying vis(3) function, the vis utility does not recognize multibyte characters, and thus may consider them to be non-printable when they are in fact printable (and vice versa). BSD
June 25, 2004 BSD
All times are GMT -4. The time now is 11:04 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy