[Autogenerated] Now,
I'm guessing if truth be told you're starting to look at org and
thinking actually maybe it's not for me but TIFF,
we continue to write everything in one go.
Of course, it looks inconvenient, but that is why we have AK files.
So just like said,
we can implement arc files and that then allows us to persist our
command line entries so we can start commenting our code.
We can have our begin block,
we can have anything we want in our bi begin block and of course,
then we can end it.
We can start commenting our main blog, we can open up our main block.
Remember there is no key word for the main block.
We can implement whatever we want within our main block.
Of course, we can close it with our closing brace bracket.
Then our summary information is going to be inside of our end blocks.
Should we want open up our end blocks and then close our end block.
Now, if we had tried writing this at the command line,
of course, it's going look horrendous.
But if we have this in our file, we can reference the file whenever we need it.
And that's what we're going to see.
Now by moving out to our command line, looking at how we create these arc files,
we can create a very simple one to begin with,
but then implement our password arc file.
Come on, I'm going to challenge you to join me.
And let's see who can do a better job.
If we create a very simple org file, we can go through and say, call it.
I don't know, say test dot org, we can put a shebang in if we want.
But I'm not going to bother and we can put in some comments,
but I'm not really going to bother.
If I just go in here, we can have our begin block.
If we need it,
we can open up our blo begin block and we can then write it on one line or
more conveniently probably write it on multiple lines.
Print this is the start, obviously,
we can do anything that we need and we can spell it correctly.
If we really want, we can end that line, write more lines if we want.
But then I'm just going to end my block in our main block.
Remember we just go into the block and then we can go through and specify,
we can print maybe the whole row so we can just go back to dollar zero,
end that line and then close our main block with that done.
We can go into our end block and then we can go
through and print whatever we want.
We can then have print, this is the end and again,
we can spell it however we want.
But once we're ready with that, we can close our brace bracket.
And this is now our arc file with this in place,
we can go through it and then go run our arc minus
lowercase F test dot org and run that across,
let's say our E T C and pass W D file.
Uh Let's make sure we've got our separator there correctly.
So we can see this is the start,
this is the end and then all of our data in between.
So we know now we can implement through our arc file.
We have got an arc file created for you.
If I go through then and cat out from their said an arc
directory and then pass W D dot org, we can see then that we've got the file.
Now,
I've put the shebang the shebang more of a reminder that we should be
running this with org lowercase F within our big blog.
We've got our field separator,
our header information and the initialization of our count variable.
We then move into our main block which is looking for those
lines ending in bash we increment our counter,
print out our data and end the block in our summary data.
That's all included within our end block.
We've got then our print statement for the total number of
users and those implementing the Bash shell.
So we can see how much more simple this is because it's all contained
within our text file that we can reference whenever we want.
As we access, it is going to be arc minus F.
Let me escape and dot To bring up my last argument and make a
reference to my E T C and pass W D file.
Let's move this to the top.
And you can see how simple my command line is because we're hiding the
complexity of the arc statement which is inside of our arc file.
But once we've perfected that it's easy to access through
the lowercase F as we execute this,
we can see now that we had the same information before,
but look how concise our command line information is.
And this is really the power of both sd and arc is by being able to
make use of these arc and said scripts to hide the complexity and
allow us to develop it over a period of time.