Search:

You're mighty welcome.

I really wish I could tell you why the changes we made to ~/.bashrc to modify your PATH fixed the problem. But, I can't because I don't know.

When steeldriver challenged...

To Langstracht:

I'd like you to answer some more questions:

What Linux operating system are you running?
Are you running your operating system in WUBI?
What application did you use to...

Oh, man!
I have my threads confused. There's no "Jonathan" here.
Time to do some heavy editing.

Well, I did it because when I compared Langstracht's PATH to what I have in my PATH, /home/username/bin was the only path that was missing. Since the script runs for me, but doesn't run for him, I...

Yup...sure as hell would be.

Yeah...well...that's why I told you to:

Please post the output you get, in a code box, when you run it.


So, based on what you described, in lieu of posting the output, I'm assuming that...

Well, maybe I don't understand what you want the script to do.
You write: "The above code displays every line it is supposed to ... plus the "Hit [ ... abort." after each "batch" of lines." <--...

You might want to remember that you'll need to use the "shebang" as the first line of every bash script that you write in the future:


#!/bin/bash

See if your script runs if you put the following line in as the very first line of your code (it's called a shebang):


#!/bin/bash


Here's how to make a code box:

It would be nice to see the entire content of your script in a code box. Otherwise, we're just guessing as to why what works for us isn't working for you.

In keeping with your coding style, which is much different than mine, your script worked for me when I added the blue line shown in the code box below:


#!/bin/bash
set -e

count=10
i=1...