I'm now in the process of updating and creating a working set of standard scripts for linux. This is the base, I will build everything else off of. Everything above it, will assume that the standard scripts are installed. They will eventually, want to be cross platform, at least on Windows and Linux. Since I'm focusing now on Linux, as it works better, this will be the first to be finished again. I'm writing here because I'm having some trouble. This is a network specific thing, for my home network. I may use them on other networks as time goes on, but let's start with my network. And then, soon after, I can work on my github page for my network, I hope, so that others can benefit possibly and stuff later, though I may start with making them private on there. We'll see. If I have to make them private, it's just because they contain some specific code identifying my network, which I may or may not want to share.

OK. Let's start with specifics, where I'm having trouble.

The first thing I'm going to want to do, is modify my install script, so that upon installing, as it's last task, it will output a log to its directory it's ran from, which will list in this format:

..the files it installed, which can be gotten from listing in that format, the files in it's below directory of ./scripts/ all the files in there. Then, in my install file, I'll use that script in that folder, to output the files, line by line, and then I'll redirect it to a text (log) file. I want to include itself in this listing.

This, will then be able to be printed, by sending the text file to a printer, probably for now, at the library, and I will be able to have a checklist once it's on paper, of what's debugged, and what still needs to be debugged, very easily. Then I can come back to you guys and have some help debugging these files. Otherwise, I need a checklist by hand, which is trickier. I am losing time trying to create it by hand.

I know how to list, with the ls command, in general in bash. But this is a trickier problem, because I want it in a certain format. I assume it will just be a list command of some sort.

It would help if you were more specific.

1 members found this post helpful.

I just mean I don't want it to list side by side, but as straight up and down. Let me try the command given, and see if it does what I want. Just a second...

Almost! Just get rid of the directory name in the front of each thing, because I know that! I don't need the path in my output. Other than that, that commmand works just fine. As long as it really listed everything in the dir. I can't tell for sure, but that's because it's too hard to check, hence my reason for wanting the command in the first place.

This is why, like I said in the other thread, I want to get commands listed by my everyday 2 workspaces!

Try the -1 option for ls or the -printf option for find. Review them in "man ls" or "man find" to ensure that they do what you need.

Will list files in the current directory one file per line but the find command above will recurse down the directory tree.
Review man find about controlling the print output.

I should have known that, but I didn't. The

command, was just what I needed. Now I can find out, what I really need to debug! The tough work is ahead for these scripts! But at least it's going to be simpler with this list!

My other scripts, with what's already is written, really IS tougher. But I had to have this list, so I could easily identify what I've already done.

only formats to columns if its output goes to a terminal.
Prove: redirect the output to a file
is an alternative. The shell expands the *
and the printf command prints them.
(The format is re-applied until all arguments are printed. Compare with
)

1 members found this post helpful.

NB :
lists files & dirs in a dir (but not hidden ones), in case that matters

Not sure if it helps but I know "ls -a" lists even hidden stuff. Maybe if you make it an array and pipe it through a function that does line by line. grep may be useful. X E.