OK, the saga continues. I am nearly done, but have this structure left, e.g.:
and I need to replace the line breaks in that last field with text '\n'. However when I use awk to access $s of line '/three/', I just get '"'.
I don't want to just replace all line breaks with '\n' in the file, because the ones at the end of lines one and two are not harming the input, whereas the ones in field three are (I'm trying to json_decode in PHP).
:confused:
I have a script that Cats a flat database file which contains 12 columns into sed. I want to add a 13th column which includes " ,2005-08-29 " * The date needs to be the current date.
This 13th column would be appended to the end of each line.
Does anyone have a clue... (5 Replies)
Have another question that has been eluding me all day.
I have data file I'm trying to reformat so that each line is appended with an ID code, but the ID code needs to update as it searches through the file.
I.e.
----Begin Original Datafile-----
Condition = XXX
Header Line 1
Header... (1 Reply)
i am trying to append a 5 line SGML file(file1) with a 500,000 line SGML file (file2).
file1 is a template, so i wish to preserve.
i only want to add lines 5 to the end of file2.
i have:
cp file1 temp1
sed -n '5,$p' file2 >> temp1
when i check the tail of temp1, i consistantly find the... (3 Replies)
I know this has been asked before but I just can't parse the syntax as explained. I have a set of files that has user information spread out over two lines that I wish to merge into one:
User1NameLast User1NameFirst User1Address
E-Mail:User1email
User2NameLast User2NameFirst User2Address... (11 Replies)
Source File:
abcdefghijklmnop01qrstuvwxyz
abcdefghijklmnop02qrstuvwxyz
abcdefghijklmnop03qrstuvwxyz
abcdefghijklmnop04qrstuvwxyz
abcdefghijklmnop05qrstuvwxyz
Whatever characters are in 17-18 on each line of the file, it should be concatenated to the same line at the character number... (6 Replies)
Hi ,
I have the below ouput,
=====gopi=====
assasassaa
adsadsadsdsada
asdsadsadasdsa
sadasdsadsd
=====kannan===
asdasdasd
sadasddsaasd
adasdd
=====hbk===
asasasssa
....
..
I want the output like as below, not able paste here correctly. (2 Replies)
Hi, I wanted to add each row of file2.txt to entire length of file1.txt given the sample data below and save it as new file. Any idea how to efficiently do it. Thank you for any help.
input file
file1.txt file2.txt
140 30 200006 141 32
140 32 200006 142 33
140 35 200006 142... (5 Replies)
Discussion started by: ida1215
5 Replies
LEARN ABOUT NETBSD
join
JOIN(1) BSD General Commands Manual JOIN(1)NAME
join -- relational database operator
SYNOPSIS
join [-a file_number | -v file_number] [-e string] [-j file_number field] [-o list] [-t char] [-1 field] [-2 field] file1 file2
DESCRIPTION
The join utility performs an ``equality join'' on the specified files and writes the result to the standard output. The ``join field'' is
the field in each file by which the files are compared. The first field in each line is used by default. There is one line in the output
for each pair of lines in file1 and file2 which have identical join fields. Each output line consists of the join field, the remaining
fields from file1 and then the remaining fields from file2.
The default field separators are tab and space characters. In this case, multiple tabs and spaces count as a single field separator, and
leading tabs and spaces are ignored. The default output field separator is a single space character.
Many of the options use file and field numbers. Both file numbers and field numbers are 1 based, i.e. the first file on the command line is
file number 1 and the first field is field number 1. The following options are available:
-a file_number
In addition to the default output, produce a line for each unpairable line in file file_number. (The argument to -a must not be
preceded by a space; see the COMPATIBILITY section.)
-e string Replace empty output fields with string.
-o list The -o option specifies the fields that will be output from each file for each line with matching join fields. Each element of
list has the form 'file_number.field', where file_number is a file number and field is a field number. The elements of list must
be either comma (``,'') or whitespace separated. (The latter requires quoting to protect it from the shell, or, a simpler
approach is to use multiple -o options.)
-t char Use character char as a field delimiter for both input and output. Every occurrence of char in a line is significant.
-v file_number
Do not display the default output, but display a line for each unpairable line in file file_number. The options -v 1 and -v 2
may be specified at the same time.
-1 field Join on the field'th field of file 1.
-2 field Join on the field'th field of file 2.
When the default field delimiter characters are used, the files to be joined should be ordered in the collating sequence of sort(1), using
the -b option, on the fields on which they are to be joined, otherwise join may not report all field matches. When the field delimiter char-
acters are specified by the -t option, the collating sequence should be the same as sort(1) without the -b option.
If one of the arguments file1 or file2 is ``-'', the standard input is used.
The join utility exits 0 on success, and >0 if an error occurs.
COMPATIBILITY
For compatibility with historic versions of join, the following options are available:
-a In addition to the default output, produce a line for each unpairable line in both file 1 and file 2. (To distinguish between
this and -a file_number, join currently requires that the latter not include any white space.)
-j1 field Join on the field'th field of file 1.
-j2 field Join on the field'th field of file 2.
-j field Join on the field'th field of both file 1 and file 2.
-o list ...
Historical implementations of join permitted multiple arguments to the -o option. These arguments were of the form ``file_num-
ber.field_number'' as described for the current -o option. This has obvious difficulties in the presence of files named ``1.2''.
These options are available only so historic shell scripts don't require modification and should not be used.
SEE ALSO awk(1), comm(1), paste(1), sort(1), uniq(1)STANDARDS
The join command is expected to be IEEE Std 1003.2 (``POSIX.2'') compatible.
BSD April 28, 1995 BSD