Don is right of course and it all depends what it is that you require.
To illustrate, to add the additional requirements, you could try these adjustments, which makes the code more precise, but more complex.
How much precision you need depends on the variability of your input files. So to understand the limitations, you need to understand both your data and your code and you need to test of course.
This approach uses RS=, which is a special case, where an empty line (two consecutive newlines) is used as a record separator. The additional requirements, meant that the field separator FS needed to be changed to a newline, so that each field constitutes a line within a record in file2. These lines then needed to be split into smaller subfields using the split() command.
Each approach has its pros and cons.
A pro of this approach may be that the code can be simpler, so it may be easier to understand.
The cons are:
Adding more precision can sometimes lead to more complexity than a line based approach.
If there is so much as a space or TAB character on any of the empty lines, then it may break the solution..
You need to weigh these considerations when choosing your approach. It all depends..
Last edited by Scrutinizer; 01-23-2019 at 12:42 AM..
These 2 Users Gave Thanks to Scrutinizer For This Post:
First off, I have been learning AWK by trial and error over the last week or so, and there are some gaps in my basic understanding of the language.
Here is my situation: I am coding and outputting results from an experiment I conducted in Psyscope, which has all been compiled into a master file.... (2 Replies)
Hi Friends,
Can any of you explain me about the below line of code?
mn_code=`env|grep "..mn"|awk -F"=" '{print $2}'`
Im not able to understand, what exactly it is doing :confused:
Any help would be useful for me.
Lokesha (4 Replies)
Hi All,
I have working (Perl) code to combine 2 input files into a single output file using the join function that works to a point, but has the following limitations:
1. I am restrained to 2 input files only.
2. Only the "matched" fields are written out to the "matched" output file and... (1 Reply)
Hi,
I have line in input file as below:
3G_CENTRAL;INDONESIA_(M)_TELKOMSEL;SPECIAL_WORLD_GRP_7_FA_2_TELKOMSEL
My expected output for line in the file must be :
"1-Radon1-cMOC_deg"|"LDIndex"|"3G_CENTRAL|INDONESIA_(M)_TELKOMSEL"|LAST|"SPECIAL_WORLD_GRP_7_FA_2_TELKOMSEL"
Can someone... (7 Replies)
Hi everyone,
I've been thinking and trying/changing all day long the below code, maybe some awk expert could help me to fix the for loop I've thought,
I think I'm very close to the correct output.
file1 is:
<boxes content="Grapes and Apples">
<box No.="Box MT. 53">
<quantity... (8 Replies)
Hello everyone
Sorry I have to add another sed question. I am searching a log file and need only the first 2 occurances of text which comes after (note the space) "string " and before a ",". I have tried
sed -n 's/.*string \(*\),.*/\1/p' filewith some, but limited success. This gives out all... (10 Replies)
logs:
"/home/abc/public_html/index.php"
"/home/abc/public_html/index.php"
"/home/xyz/public_html/index.php"
"/home/xyz/public_html/index.php"
"/home/xyz/public_html/index.php"
how to use "cut" or "awk" or "sed" to get the following result:
abc
abc
xyz
xyz
xyz (8 Replies)
Hi,
I'm using Linux and bash shell. I have a file (F1.txt) with contents like
Table1 Column1 123abc
Table1 Column2 xyz
Table2 Column1 543
Now, I would like to get the output as
UPDATE Table1 SET Column1='123abc';
UPDATE Table1 SET Column2='xyz';
UPDATE Table2 SET Column1='543';... (3 Replies)
Hi Team. I am trying to execute a simple for loop within an awk but its giving a different result. Below is the main code:
awk '{for(i=1;i<=6;i++) print $i}'The result should be 1 2 3 4 5 6 but its not giving this result. Can someone please help? (3 Replies)
Discussion started by: chatwithsaurav
3 Replies
LEARN ABOUT DEBIAN
mencal
mencal(1) 1 mencal(1)NAME
mencal - menstruation calendar
SYNOPSIS
mencal [options] [file1 file2 ... -c CONF1 -c CONF2 ...]
DESCRIPTION
Display options:
-m, --monday
draw monday as first weekday (sunday is default)
-1 current month (default)
-3 previous, current and next month
-y [YYYY]
all-year calendar (default YYYY is current year)
-q, --quiet
no top information will be printed
-n, --nocolor
noncolored output
-i, --icolor COLOR
intersection color (default red)
available colors: red, green, blue, yellow, violet, cyan, shiny, bold
mencal configuration:
-c, --config
s=[YYYY]MMDD,l=LL,d=DD,n=NAME,f=FILE,c=COLOR
The second argument is a comma separated list of options. No spaces are allowed in this list. If no name is specified, 'Unknown' is
used. Various -c options or filenames can be set.
s,start=[YYYY]MMDD
start day of period (default current day)
l,length=LL
length of period in days (default 28)
d,duration=D
duration of menstruation in days (default 4)
n,name=NAME
name of subject
f,file=FILE
filename to save configuration to (see section FILES)
only menstruation related variables will be saved
c,color=COLOR
color used for menstruation days
available colors: red, green, blue, yellow, violet, cyan, shiny, bold default color is red, with '-n' switch color settings are
ignored
Info options:
-h, --help
print help
-V, --version
print version information
FILES :
$HOME/.mencalrc - the default configuration file that is automatically loaded
AUTHOR :
(C) 2002 C. McCohy
e-mail: <mccohy@kyberdigi.cz>
Word-Wide-Web: http://www.kyberdigi.cz/projects/mencal/english
This manual page was written for the Debian GNU/Linux distribution because the original program does not have a manual page (but may be
used by others).
HISTORY
22 March 2002 - Originally written by Amaya Rodrigo <amaya@debian.org>.
24 Apr 2002 - New manpage contributed by Pablo S. Torralba <psanchez@skyrealms.org>.
Amaya Rodrigo <amaya@debian.org> is now responsible for developing and maintaining this manual page. Comments and suggestions are greatly
wellcome.
mencal Menstruation calendar mencal(1)