Sponsored Content
Top Forums Shell Programming and Scripting Aligning output with null fields in shell script Post 302698927 by alister on Monday 10th of September 2012 05:49:19 PM
Old 09-10-2012
As mentioned above, the field width of some of the conversion specifiers in your printf format string aren't wide enough to accomdate the data. You have a decision to make: Do you want to truncate the values or not?

If you want to truncate, add precision to the specifier. %-8s creates an 8 character-wide field, but if the value is wider it will still be printed in its entirety, shifting following fields as necessary. Adding precision prevents this with truncation: %-8.8s. Note that the precision does not have to equal the field width. For example, %-8.5s represents a left-justified, 8 character-wide field whose string value will never exceed 5 characters.

If you do not want to truncate, then you have two choices. You can increase field widths until they are no longer likely to be a problem; or you can read all of the data first, determine the width of the widest value in each field, and then build the printf format string accordingly.

Regards,
Alister
This User Gave Thanks to alister For This Post:
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Find null fields in file

Hi All, I have some csv files out of which i want to find records which have empty values in either the 14th or 16th fields. The following is a sample. $cut -d',' -f14,16 SPS* | head -5 VOIP_ORIG_INFO,VOIP_DEST_INFO sip:445600709315@sip.com,sip:999@sip.com... (2 Replies)
Discussion started by: rahulrathod
2 Replies

2. Shell Programming and Scripting

Replace 3 fields with null in the file

Hi, I have a file with 104 columns delimited by comma. I have to replace fields 4,5 and 19 with null values and after replacing the columns in the file , the file should be still comma delimited. I am new to shell scripting, Experts please help me out. Thank you (1 Reply)
Discussion started by: vukkusila
1 Replies

3. Shell Programming and Scripting

exclude records with null fields

Hi, can I do something like this to add a condition of checking if the 4th field is number or space or blank also: awk -F, '$4 /^*||*/' MYFILE >> OTHERFILE I also want the other part i.e. I need to exclude all lines whose 4th field is space or blank or number: MYFILE a,b,c,d,e a,b,c,2,r... (2 Replies)
Discussion started by: praveenK_Dudala
2 Replies

4. Shell Programming and Scripting

Find out if few fields in a file are null

Hi, I've a pipe delimited file where I want to find out a number of lines where 1st 2nd and last field are null using awk/sed. Is it possible? Thanks (5 Replies)
Discussion started by: rudoraj
5 Replies

5. Shell Programming and Scripting

Shell script for validating fields in a file

Hi, I have not used Unix in a very long time and I am very rusty. I would appreciate any help I can get from the more experienced and experts in Shell script. I am reading one file at a time from a folder. The file is a flat file with no delimeters or carriage return. Col1 through col6 is... (5 Replies)
Discussion started by: asemota
5 Replies

6. Shell Programming and Scripting

pass null value to sql script from korn shell script

There are 4 parameters that I have to pass from korn shell to sql script. 1) I have to check if $1 , $2 , $3 and $4 are null values or not . How can I do that ? 2) Once its determined that these values are null (in the sense they are empty) how can I pass null values to sql script... (11 Replies)
Discussion started by: megha2525
11 Replies

7. Shell Programming and Scripting

How to get fields and get output with awk or shell script.?

I have a flat file A.txt with field seperate by a pipe 2012/11/13 20:06:11 | 284:hawk pid=014268 opened Locations 12, 13, 14, 15 for /home/hawk_t112/t112/macteam/qt/NET12/full_ddr3_2X_FV_4BD_1.qt/dbFiles/t112.proto|2012/11/14 15:19:26 | still running |norway|norway 2012/11/14 12:53:51 | ... (6 Replies)
Discussion started by: sabercats
6 Replies

8. Shell Programming and Scripting

Shell Script to Group by Based on Multiple Fields in a file

Hi, I want to know if there is any simple approach to SUM a field based on group by of different fields for e.g. file1.txt contains below data 20160622|XXX1||50.00||50.00|MONEY|Plan1| 20160622|XXX1||100.00||100.00|MONEY|Plan1| 20160623|XXX1||25.00||25.00|MONEY|Plan1|... (3 Replies)
Discussion started by: cnu_theprince
3 Replies

9. Shell Programming and Scripting

Shell script to pull certain fields

I/m a beginner so be easy. I have text files that live on an AIX server. The files come in and I've been charged with writing a shell script to email out that pulls the first date, and the last date of the file. I need to load these 2 dates into 2 separate variables. I can figure out the variables,... (13 Replies)
Discussion started by: mattadams1983
13 Replies

10. Shell Programming and Scripting

Fields shifting in file, do to null values?

The below code runs and creates an output file with three sections. The first 2 sections are ok, but the third section doesn't seem to put a . in all the fields that are blank. I don't know if this is what causes the last two fields in the current output to shift to a newline, but I can not seem... (3 Replies)
Discussion started by: cmccabe
3 Replies
format(n)						       Tcl Built-In Commands							 format(n)

__________________________________________________________________________________________________________________________________________________

NAME
format - Format a string in the style of sprintf SYNOPSIS
format formatString ?arg arg ...? _________________________________________________________________ INTRODUCTION
This command generates a formatted string in the same way as the ANSI C sprintf procedure (it uses sprintf in its implementation). Format- String indicates how to format the result, using % conversion specifiers as in sprintf, and the additional arguments, if any, provide val- ues to be substituted into the result. The return value from format is the formatted string. DETAILS ON FORMATTING
The command operates by scanning formatString from left to right. Each character from the format string is appended to the result string unless it is a percent sign. If the character is a % then it is not copied to the result string. Instead, the characters following the % character are treated as a conversion specifier. The conversion specifier controls the conversion of the next successive arg to a particu- lar format and the result is appended to the result string in place of the conversion specifier. If there are multiple conversion speci- fiers in the format string, then each one controls the conversion of one additional arg. The format command must be given enough args to meet the needs of all of the conversion specifiers in formatString. Each conversion specifier may contain up to six different parts: an XPG3 position specifier, a set of flags, a minimum field width, a pre- cision, a length modifier, and a conversion character. Any of these fields may be omitted except for the conversion character. The fields that are present must appear in the order given above. The paragraphs below discuss each of these fields in turn. If the % is followed by a decimal number and a $, as in ``%2$d'', then the value to convert is not taken from the next sequential argument. Instead, it is taken from the argument indicated by the number, where 1 corresponds to the first arg. If the conversion specifier requires multiple arguments because of * characters in the specifier then successive arguments are used, starting with the argument given by the number. This follows the XPG3 conventions for positional specifiers. If there are any positional specifiers in formatString then all of the specifiers must be positional. The second portion of a conversion specifier may contain any of the following flag characters, in any order: - Specifies that the converted argument should be left-justified in its field (numbers are normally right-justified with leading spaces if needed). + Specifies that a number should always be printed with a sign, even if positive. space Specifies that a space should be added to the beginning of the number if the first character isn't a sign. 0 Specifies that the number should be padded on the left with zeroes instead of spaces. # Requests an alternate output form. For o and O conversions it guarantees that the first digit is always 0. For x or X conver- sions, 0x or 0X (respectively) will be added to the beginning of the result unless it is zero. For all floating-point conver- sions (e, E, f, g, and G) it guarantees that the result always has a decimal point. For g and G conversions it specifies that trailing zeroes should not be removed. The third portion of a conversion specifier is a number giving a minimum field width for this conversion. It is typically used to make columns line up in tabular printouts. If the converted argument contains fewer characters than the minimum field width then it will be padded so that it is as wide as the minimum field width. Padding normally occurs by adding extra spaces on the left of the converted argu- ment, but the 0 and - flags may be used to specify padding with zeroes on the left or with spaces on the right, respectively. If the mini- mum field width is specified as * rather than a number, then the next argument to the format command determines the minimum field width; it must be a numeric string. The fourth portion of a conversion specifier is a precision, which consists of a period followed by a number. The number is used in dif- ferent ways for different conversions. For e, E, and f conversions it specifies the number of digits to appear to the right of the decimal point. For g and G conversions it specifies the total number of digits to appear, including those on both sides of the decimal point (how- ever, trailing zeroes after the decimal point will still be omitted unless the # flag has been specified). For integer conversions, it specifies a minimum number of digits to print (leading zeroes will be added if necessary). For s conversions it specifies the maximum num- ber of characters to be printed; if the string is longer than this then the trailing characters will be dropped. If the precision is spec- ified with * rather than a number then the next argument to the format command determines the precision; it must be a numeric string. The fifth part of a conversion specifier is a length modifier, which must be h or l. If it is h it specifies that the numeric value should be truncated to a 16-bit value before converting. This option is rarely useful. If it is l it specifies that the numeric value should be | (at least) a 64-bit value. If neither h or l are present, numeric values are interpreted as being values of the width of the native | machine word, as described by tcl_platform(wordSize). The last thing in a conversion specifier is an alphabetic character that determines what kind of conversion to perform. The following con- version characters are currently supported: d Convert integer to signed decimal string. u Convert integer to unsigned decimal string. i Convert integer to signed decimal string; the integer may either be in decimal, in octal (with a leading 0) or in hexadecimal (with a leading 0x). o Convert integer to unsigned octal string. x or X Convert integer to unsigned hexadecimal string, using digits ``0123456789abcdef'' for x and ``0123456789ABCDEF'' for X). | c | Convert integer to the Unicode character it represents. s No conversion; just insert string. f Convert floating-point number to signed decimal string of the form xx.yyy, where the number of y's is determined by the precision (default: 6). If the precision is 0 then no decimal point is output. e or e Convert floating-point number to scientific notation in the form x.yyye+-zz, where the number of y's is determined by the preci- sion (default: 6). If the precision is 0 then no decimal point is output. If the E form is used then E is printed instead of e. g or G If the exponent is less than -4 or greater than or equal to the precision, then convert floating-point number as for %e or %E. Otherwise convert as for %f. Trailing zeroes and a trailing decimal point are omitted. % No conversion: just insert %. For the numerical conversions the argument being converted must be an integer or floating-point string; format converts the argument to binary and then converts it back to a string according to the conversion specifier. DIFFERENCES FROM ANSI SPRINTF
The behavior of the format command is the same as the ANSI C sprintf procedure except for the following differences: [1] %p and %n specifiers are not currently supported. [2] For %c conversions the argument must be a decimal string, which will then be converted to the corresponding character value. [3] The l modifier is ignored for real values and on 64-bit platforms, which are always converted as if the l modifier were present | (i.e. the types double and long are used for the internal representation of real and integer values, respectively). If the h modi- fier is specified then integer values are truncated to short before conversion. Both h and l modifiers are ignored on all other conversions. SEE ALSO
sprintf(3), string(n) KEYWORDS
conversion specifier, format, sprintf, string, substitution Tcl 8.1 format(n)
All times are GMT -4. The time now is 12:38 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy