Bashscripts.org

this is just something i've been doing this evening, after being prodded and pushed by crouse, and jbsnake. i get some errors at the bottom, not sure what i'm doing wrong.

ok an update

WOOT !!!!! Coasties first script !!!!!!! YES, another convert !

nice job coastie...
you get an error on that one line cause the word echo is capitalized (in the future please post the error you got to better help)...

in the function hello
i would say echo $1 instead of echo $name
then when you call hello
say hello $name
(just to get an idea as to how you pass data to functions and how functions pass it back)

but very nice script... you're on a one way trip to programmer-ville

WTG Coastie

i'll be adding to it, just basically gonna plug in the basics and see where it takes me.

coastie,

I'm new here and I don't want to butt in or be rude.
I did, however, try running your script and I was getting errors also. This is what I did to fix the errors:
I changed the input section a little bit...very small change to avoid the errors.

Changed:

to:

...and the same for input =2.

I know you didn't ask me an I apologize for being rude if I was. I'm here to learn and I learned from you and if I can help in return, that is all I want to do!!!

Cool little script!!!

The question I have is when it asks for input '1' or '2' to exit or continue. When it hits 'read', is there a way to prevent it from actually printing the '1' or '2' on the screen and jump right into exiting or continuing?

Freestone

yes... instead of the standard "read" command you could do a



using the terminal..... i simply typed "man read" ..... it's a bash builtin, so i had to scroll down..... there i saw the entry for read and then looked at the options.... the options i used...

-s Silent mode. If input is coming from a terminal, characters are not echoed.
-n nchars
read returns after reading nchars characters rather than waiting for a complete line of input.


FWIW .... no question is stupid, and we will be HAPPY to help you

I did 'man read' and saw that it was a bash builtin but I was pressed for time. I would love to just read right through the whole man page on bash but it certainly isn't like reading a John Grisham novel. What I've been doing is just hopping around learning a little of this and a little of that. But to go straight through a manual is a bit maddening to me. I have the advanced bash scripting guide and I'd like to read all the way through that also...
unless I'm writing a script, reading about a command or technique kind of leaves my head spinning unless I'm able to put it into use. I have to remind myself that I'm not going to learn all of this overnight!!!!

he he he.. yeah.... i think most people have felt that way when they started. Just keep at it, keep writing scripts, and before you know it....... you've learned alot more than you thought you had


oh yeah....... and when you get into real trouble...... ask jbsnake

Yep crouse - that's how I started learning and improving - writing scripts and asking you and jb