LinuxQuestions.org
Register a domain and help support LQ
Go Back   LinuxQuestions.org > Forums > Non-*NIX Forums > Programming
User Name
Password
Programming This forum is for all programming questions.
The question does not have to be directly related to Linux and any language is fair game.

Notices

Reply
 
LinkBack Search this Thread
Old 12-09-2012, 02:05 AM   #1
fatalerror0x00
Member
 
Registered: Oct 2012
Location: Holden, ME, USA
Distribution: SlackWare64 14.00
Posts: 185

Rep: Reputation: 0
Bash: Help with solving bugs in a script


At this time I have 2 concerning issue with my script (4 if you wanna count an issue with how you run the script and the kinda messy menus (which I am at this moment fixing but you don't need that fixed to help with all this))

because of length and that I don't know how to copy from vim to another application I will attach it for download it's all one file to run but theres a file-betas beta which has a map of the directories and also has the bugs in the script that are known so far. it will explain what happens and what seems to cause the issue if known or why it's a bug.

This is a game it's actually gonna be a gift for my girlfriend who loves it when I write scripts and tell her about them. So I figured why not for our 3 year anniversary I make her a little game to play and in the end will have a special message but everything I've got is in the attachment and any help would be appreciated I'd rather not move to cleaner coding I know I could make a lot of improvements but I'm not really worried about those right now if I have time when I finish the game I might go through and clean up alot of coding but for now unless the way i have it coded now is what causes the error I don't need other codes but thank you and if you wait it out a few months I will be more then happy to take your ideas

NOTE: Also upon everything else here I do have one formatting issue I can't seem to find a solution to so here it is. I want line breaks between words not between letters is there anyway to tell echo or bash to do this so that no matter how big the terminal screen line breaks are between words not letters so works don't get broken up and hard to read. Thanks

Currently I am actually working on improving the start menu (basically all there is) so that it looks better which I've got you guys in the middle but everything works for displaying things.

Well let me know what your opinion is on my issues at hand

Had to fool the website into thinking my file was a .txt file so really though it doesn't same it's tarballed as a tar.gz so like I normally do just run tar xvf game.txt and it will extract to Game and in there you will find files_beta and you can open that and find where everything is

I know that my issue with how I run the script is labeled a minor bug when it's not really a bug and I apologize for that
Attached Files
File Type: txt game.txt (7.9 KB, 15 views)

Last edited by fatalerror0x00; 12-09-2012 at 03:21 AM. Reason: Mistake on concerning issues
 
Old 12-09-2012, 02:25 AM   #2
fatalerror0x00
Member
 
Registered: Oct 2012
Location: Holden, ME, USA
Distribution: SlackWare64 14.00
Posts: 185

Original Poster
Rep: Reputation: 0
New bug found after some formatting changes and testing

Found a new bug that has seemed to occur after some formatting changes haven't really looked into it but since it's in the file I might as well give an updated tarball with .txt extension :P

In the fact it's late and I'm tired I wasn't thinking that grep's duty is to extract anything matching and display to the screen so this is NOT a bug just a mistake on my part not paying attention :P

What was claimed as a bug has been downgraded to an annoyance but progress is not shown in file as I will be fixing this shortly and post a new update with formatting changes to startMenu.bash
Attached Files
File Type: txt game.txt (6.3 KB, 12 views)

Last edited by fatalerror0x00; 12-09-2012 at 03:10 AM. Reason: Claimed bug is NOT a bug
 
Old 12-09-2012, 03:34 AM   #3
fatalerror0x00
Member
 
Registered: Oct 2012
Location: Holden, ME, USA
Distribution: SlackWare64 14.00
Posts: 185

Original Poster
Rep: Reputation: 0
Updated with fix to grep

Applied quiet argument to grep so user can't see what string I use to verify my save files (though I don't I'd ever in my situation have to worry about a file with the same name and extension existing in that directory to where this file is going but I did it for fun and what not :P

Also has finishing touches on menu options but not complete without finding out how to get line breaks forced between words rather then letters if possible

on another note files_beta is not really a change log file it just for now one has bugs that I noticed and maybe of significance to put in I will try to put in everything I change that's not just tiny stuff but i do have in there I fixed grep if you notice the - Fixed this is mostly just so that if I ever see the issue I know I fixed it and so I either undone something or I did the same thing again or something similar.

Thanks everyone Let me know what you got for me
Attached Files
File Type: txt game.txt (7.8 KB, 18 views)
 
Old 12-09-2012, 11:56 AM   #4
millgates
Member
 
Registered: Feb 2009
Location: 192.168.x.x
Distribution: Slackware
Posts: 650

Rep: Reputation: 268Reputation: 268Reputation: 268
Hi,
nice script! A few notes, though:

1)
Code:
	# Some intro text
	echo -e "\n\t\t***Game Title Here***\n"
	echo -e "\nWelcome adventurer! Are you ready to continue your journey?\n"

	# Start menu options
	echo -e "\n\t\tNEW game"
	echo -e "\t\tLOAD saved game"
	echo -e "\t\tQUIT game\n"
Instead of a lot of echo statements, it may be nicer and more readable to use a heredocument (just a suggestion).

2)
Code:
	case $startMenu_action in
		[Nn][Ee][Ww])
			newGame

			;;
Also just a small suggestion: I think following might be slightly more readable (if you have recent enough bash):
Code:
	case "${startMenu_action^^}" in
		NEW)
			newGame

			;;
Now, the more important things:

Quote:
When creating a new game on occassion mkdir will run several times. (minor)
When creating a new game on occassion will echo "Load successful" from the loadGame function several times (which isn't called anywhere in newGame function) (minor)
Occassionally when creating a new game if folder name exist in another case mkdir throws an error but creates the folder anyway. (minor)
Code:
newGame() {
	read -p "Name your save folder: " savedGame_fileName

	if ...
	elif [[ $savedGame_fileName == [Dd][Ee][Ll][Ee][Tt][Ee] ]]; then
		newGame
                ...
	fi

	mkdir ../savedGames/$savedGame_fileName

	if ...
	else
                ...
		newGame

	fi

}
The problem here is the recursion. As long as you enter invalid $savedGame_fileName, the newGame functions stack up. When you finally get it right, all the stack items will exit just before the mkdir command.
Please note the difference between recursion and goto statement. Recursion is not the good way to re-read the variable.

Quote:
Formatting of menus are messy (improvement)
You may want to try the fold -s command.

Hope this helps
 
Old 12-09-2012, 03:35 PM   #5
fatalerror0x00
Member
 
Registered: Oct 2012
Location: Holden, ME, USA
Distribution: SlackWare64 14.00
Posts: 185

Original Poster
Rep: Reputation: 0
Heredocs - I will have to consider that it is a good idea I know a little about it and how to use it (I believe) and will look more into it thank you

"${variable^^}" - Having some issues finding what this does but I haven't gone in depth looking but incase I can't find it anyone care to explain a little (I mean I assume I know what it does kinda but before I use it I'd like to learn a little about it so I'm not just using something and clueless about it. Thank you for that answer and will consider it

Bugs: I don't understand what your saying totally if I enter a valid name this bug happens and then I can delete that folder and reuse that exact same name same format and that time it's successful and I've never had an issue with it exiting just before the mkdir command unless you mean when it fails but it actually does create the directory though it throws an error. So because I'm pretty sure you probably understood what I threw in the known bugs section that I'm just not understanding you I'm sorry could anyone explain this a little better but gonna sit here a little and try to decipher this on my own but i'm not sure if I'll be able too.

Formatting: I will look into fold and see if I can make it work thank you

Possible changes to be released soon but maybe delayed because of the example used to show me why my bugs are happening. I was gonna change whatever possible to case statements instead of if statements since I believe today I realized I could do that just before didn't see it. Maybe I'll make a startMenu2.bash to do this and test it but I think I'll wait till I work out if statements and that then transfer but thats probably my next update to this script along with making temp files hidden so the user can't easily transfere temp data thats held til save to there file manually so they never have to save (unless I were to add a check at loading save files to make sure your save location really is a save point which I may do anyone but I wish to make temp files hidden either way so that also things aren't as messy)

Complements to my script: Thank you I appreciate you saying that I've worked more then 12 hours on this script I'm semi new to bash yet I'm not I struggle learning and understanding as you maybe able to tell by now. But I'm determined to learn bash it's not my first choice but I feel that maybe if I finally learn a popular scripting language to the system I use (wheres so common and many resources) I might be able to start expanding after finally for once.

Also as this script grows larger I may need help testing the script for bugs. If you don't mind seeing past the lovey dovey stuff in the script (keeping in mind this is a three year anniversary gift for my girl) then I'd love to recruit you and even if you wanna help develop well I may turn you down on taking on projects but you can most certainly help to improve my scripts and see what we can come up with. The reason for this is I want to be doing almost all the work or at least have everything made my own way that I can and then I can at least say I made the basics and then people helped to improve. But I do have something if this project turns out to be successful I may actually think about creating a text based game (I know there not as popular these days but I still know at lot of people who would play them to there hearts content and I may start a new project and be looking for people to actually take on parts of the project. But lets not worry about that much right now I have 3 and a half months to complete this project between jobs and the several appointments I have in every week and other constant interuptions I really need help and there are some parts of this project I don't know if I'm capable of doing and wish to learn but is normally in every language where I get so frustrated I can't continue but I'm hoping this time it be different. I believe i've rambled on enough I'm sorry but thank you for reading this and hope to hear more from you guys. I will have an updated script up when I find out about fold and change to hidden temp files thank you


EDITS:

Formatting: fold -s causes a lot of unwanted spaces in the actual file and doesn't seem to apply to all strings and also actually saves a file with line breaks I'm sure everyime the file is run it will update it for the size of your terminal but the fact is alot of commands are broken and sometimes the script can't even run depending how I use fold -s (either in the script or outside and then run the line broken script for my terminal size which is the one that causes the most amount of issues at an unchanged terminal) So i think fold -s is out of the question now unless you got some kinda knowledge I couldn't find (which wouldn't surprise me :P I can't find much on it -.-)

CHANGES: Changes so far at this point in time (12/09/12 5:03PM) are making temporary files hidden files (.filename.temp) not enough to put up a new version of the code we have a new bug that has seemed to sneak in but I believe it's because of formatting in the script or it's the exact same reason why mkdir seems to be acting up. Alright for now thats all I've got.

BUGS: from reading about recursion only so far on this issue I'm very puzzled on how I used recursion all examples I've found is the the function being called constantly til something else happens which isn't as far as I can tell the situation of my script. But I guess too I should look at what you mean by goto.

Last edited by fatalerror0x00; 12-09-2012 at 04:47 PM. Reason: Update
 
Old 12-09-2012, 04:52 PM   #6
millgates
Member
 
Registered: Feb 2009
Location: 192.168.x.x
Distribution: Slackware
Posts: 650

Rep: Reputation: 268Reputation: 268Reputation: 268
Quote:
Originally Posted by fatalerror0x00 View Post
"${variable^^}" - Having some issues finding what this does but I haven't gone in depth looking but incase I can't find it anyone care to explain a little (I mean I assume I know what it does kinda but before I use it I'd like to learn a little about it so I'm not just using something and clueless about it. Thank you for that answer and will consider it
It's actually quite simple. the ^^ transforms the text held in variable to upper case. Example:
Code:
$ foo=bar

# now, a single ^ will transform the first character to upper-case:
$ echo "${foo^}"
Bar

# ^^ transforms the entire string:
$ echo "${foo^^}"
BAR
Similarly, you can use commas to transform text to lower-case:


Code:
$ foo=BAR

$ echo "${foo,}"
bAR

$ echo "${foo,,}"
bar
There's a lot of other string manipulations in bash you might find useful.

Quote:
Originally Posted by fatalerror0x00 View Post
Bugs: I don't understand what your saying totally
What I mean is this. Consider a simple script in bash with a recursive function foo()like this:

Code:
#!/bin/bash
# recursive.sh

foo() {
    read -p "enter value: " string
    case "$string" in
        valid) echo "input is valid" ;;
        *) echo "Invalid input"
           foo
           ;;
    esac
    echo "foo() is finished."
}

foo
Now, let's run it (text entered by user in bold:

Code:
$ ./recursive.sh
enter value: invalid
Invalid input
enter value: valid
input is valid
foo() is finished.
foo() is finished.
$
What has happened here? Let's see the flow of the program:

Code:
foo() {                                         ,-----> foo() {
    read -p "enter value: " string              |           read -p "enter value: " string
    case "$string" in                           |           case "$string" in
        valid) echo "input is valid" ;;         |               valid) echo "input is valid" ;;
        *) echo "Invalid input"                 |                   *) echo "Invalid input"
           # the first time, input is invalid   |                      foo
           foo  --------------------------------'                      ;;
           #             Now, the flow returns back         esac
           ;; <---------------------------------,           echo "foo() is finished."
    esac                                        '------ }   
    echo "foo() is finished."                                             
}
Please note that the echo statement is actually executed twice.

Quote:
Originally Posted by fatalerror0x00 View Post
if I enter a valid name this bug happens and then I can delete that folder and reuse that exact same name same format and that time it's successful and I've never had an issue with it exiting just before the mkdir command unless you mean when it fails but it actually does create the directory though it throws an error.
I'm not quite sure I understand what you mean; if this is not related to what I wrote above, can you post the exact steps (and input) to duplicate your bug?
EDITS:

Quote:
Originally Posted by fatalerror0x00 View Post
Formatting: fold -s causes a lot of unwanted spaces in the actual file and doesn't seem to apply to all strings and also actually saves a file with line breaks I'm sure everyime the file is run it will update it for the size of your terminal but the fact is alot of commands are broken and sometimes the script can't even run depending how I use fold -s (either in the script or outside and then run the line broken script for my terminal size which is the one that causes the most amount of issues at an unchanged terminal) So i think fold -s is out of the question now unless you got some kinda knowledge I couldn't find (which wouldn't surprise me :P I can't find much on it -.-)
What did you do with it? What I meant is that you can use fold -s to format text that you output to stdout. It will make your text break between words instead of in the middle of a word. You should not format code with fold.

Last edited by millgates; 12-09-2012 at 04:53 PM.
 
Old 12-09-2012, 05:36 PM   #7
fatalerror0x00
Member
 
Registered: Oct 2012
Location: Holden, ME, USA
Distribution: SlackWare64 14.00
Posts: 185

Original Poster
Rep: Reputation: 0
first I'll start with fold cause it's maybe simplest and right there for me. also fold I probably used it wrong is all so I will see what I can find out about it but I'm still unsure how to use it in my case but I think I might have a better idea now. - has been implented but not done with as I will need to redo this when I do heredocs in the very near future.

second "${variable^^}" seeing actually what exactly it does I think I'm gonna use it because the fact that my formatting for commands are all capitalized when I say do this commmand to do this I think it be a good idea to keep to that so I've decided I will switch to using that. - has been implemented into all places I want it.

third Then my next question because I believe I understand now why things are happening that are happening everytime it fails to do something else once my actions are successful it or something like that it shows all messages over again for what reason I don't really know but I believe I understand enough now to see whats going on but the question is how would I go about fixing this issue then? :/ thats where I think the struggle comes on

HEREDOC status - Not working out so well but I'll keep working on it on the side but for now I'm not too worried about it this is nothing that professional but it would be nice to have for this project but I'm not gonna freak out about it But I love the idea

thanks

Last edited by fatalerror0x00; 12-09-2012 at 06:41 PM.
 
Old 12-09-2012, 06:39 PM   #8
millgates
Member
 
Registered: Feb 2009
Location: 192.168.x.x
Distribution: Slackware
Posts: 650

Rep: Reputation: 268Reputation: 268Reputation: 268
Quote:
Originally Posted by fatalerror0x00 View Post
first I'll start with fold cause it's maybe simplest and right there for me. also fold I probably used it wrong is all so I will see what I can find out about it but I'm still unsure how to use it in my case but I think I might have a better idea now. - has been implented but not done with as I will need to redo this when I do heredocs in the very near future.
Considering you want to format your output for terminal that is 40 characters wide (using part of your previous post as test data),

Code:
#!/bin/bash

fold -s -w 40 << EOF
first I'll start with fold cause it's maybe simplest and right there for me. also fold I probably used it wrong is all so I will\
 see what I can find out about it but I'm still unsure how to use it in my case but I think I might have a better idea now. - has\
 been implented but not done with as I will need to redo this when I do heredocs in the very near future.
EOF
will output

Code:
first I'll start with fold cause it's 
maybe simplest and right there for me. 
also fold I probably used it wrong is 
all so I will see what I can find out 
about it but I'm still unsure how to 
use it in my case but I think I might 
have a better idea now. - has been 
implented but not done with as I will 
need to redo this when I do heredocs in 
the very near future.

Quote:
Originally Posted by fatalerror0x00 View Post
third Then my next question because I believe I understand now why things are happening that are happening everytime it fails to do something else once my actions are successful it or something like that it shows all messages over again for what reason I don't really know but I believe I understand enough now to see whats going on but the question is how would I go about fixing this issue then? :/ thats where I think the struggle comes on
If you're referring to the recursion issue, a possible solution would be a while loop. Just keep reading the variable until the input becomes valid.
 
Old 12-09-2012, 06:43 PM   #9
fatalerror0x00
Member
 
Registered: Oct 2012
Location: Holden, ME, USA
Distribution: SlackWare64 14.00
Posts: 185

Original Poster
Rep: Reputation: 0
I got the whole fold thing fixed for any size terminal I'm not sure if she might maximize her terminal so I don't wanna limit it though I should but I feel thats just not ognna cut some issues

I read about using while loops instead and was gonna mention but I thought if I went assuming things there I might look like an idiot but apparently not :P Thank you I think from here I should be able to figure out the while loop if not I'll check back in here but thank you

by tomorrow early afternoon I should have an updated version of the script without the while loop probably I doubt between work and stuff and having to go to bed very soon here that I'll be able to get some things done with the while loop especially where I'm gonna make some other adjustments

I'll let you know if I have any real trouble I appreciate your help and hope you might be willing to help me out with this script if thats not too much to ask I don't want be an annoyance is all

I think I found a nice website that shows how to fix my exact situation so tomorrow I will hopefully implement this by 3 or so and have something for you guys to look at since you been all day today seeing none of my changes which none were big really but still it's important for you to continue to see the code as it changes

Actually if I may I have a few questions about what I'm doing with a while loop...Would I have a while loop that checks for valid input and then my case statement I have now or would I implement the case statement inside the while loop somehow or would I use if statements to check for valid input and run my functions with that if anything matches? I'm lost on if I get rid of the case or if I use it and if I get rid of it I assuming I've got to use if statements.

Also I assume using if statemetns to check if it's valid then exiting the while loop to a case statement to check for what the input was might be redundent but I haven't been able to decide yet if thats true or not

I think I may have figured out the whole while loop thing for now maybe if theres anything more I should add tomorrow you can tell me I didn't overwrite the last program where this is such a change that if I was to have to redo it it take me unneccessary time to do and so names will be slightly different but also in this new update I will be giving you guys the old one too just for reference on changes made hopefully it will be out tomorrow I might if things go well tonight even have it for you but I'm unsure. I'm so unsure about if I've even done it right but we will find out

Last edited by fatalerror0x00; 12-09-2012 at 08:03 PM.
 
Old 12-09-2012, 07:35 PM   #10
grail
Guru
 
Registered: Sep 2009
Location: Perth
Distribution: Manjaro
Posts: 7,193

Rep: Reputation: 1784Reputation: 1784Reputation: 1784Reputation: 1784Reputation: 1784Reputation: 1784Reputation: 1784Reputation: 1784Reputation: 1784Reputation: 1784Reputation: 1784
Seems millgates has answered most of the pressing questions, but my 2 cents would be that you ask the user to enter data which to me is error prone as we know how easy it is to enter a typo.

To this end may I suggest you have a look at the 'select' command / statement. Whilst it will still ask the user for entries, it does number them and hence make it at least a reduced set of typing,
ie. no long file names to enter.

Also, you warn users of using 'special' characters. To help negate issues with such characters you should get in the habit of quoting your variables, especially when using things like mkdir.
Remember, this is also to protect you or your script from malicious users who may intentionally enter dangerous data.
 
1 members found this post helpful.
Old 12-09-2012, 08:33 PM   #11
fatalerror0x00
Member
 
Registered: Oct 2012
Location: Holden, ME, USA
Distribution: SlackWare64 14.00
Posts: 185

Original Poster
Rep: Reputation: 0
I thought quoting variables was to bring support for text given to it with 2 words or more not quoted already. and I'll look into select and see what I can find thank you and quoting I know won't hurt anything and anyone while on the topic of variables and quoting anyone care to explain the use of ${variable} like I understand when using something like ${variable^^} but whats with it all by it self I looked for this on the internet weeks ago for a while and got nothing on it just all about using '' and "" differences whihc I should look back into to figure out what kinda quotes you are refering too. but again thank you for your help very much will go and quote my variables once I figure out what kinda quotes and then I will look into select and see what I can come up with :O

I will work on select if I use it when I get done quoting variables update and updating to using while loops I will look at it

Also will add a list to newGame function for user to see already save files (choosing not to do this as chances they don't need to look everytime to see what there choices are)

Also having severe troubles making a while statement that works properly in the newGame function so I'm skipping that til the next update when I see what I can get working and can't.

Last edited by fatalerror0x00; 12-09-2012 at 09:13 PM.
 
Old 12-09-2012, 08:46 PM   #12
grail
Guru
 
Registered: Sep 2009
Location: Perth
Distribution: Manjaro
Posts: 7,193

Rep: Reputation: 1784Reputation: 1784Reputation: 1784Reputation: 1784Reputation: 1784Reputation: 1784Reputation: 1784Reputation: 1784Reputation: 1784Reputation: 1784Reputation: 1784
${variable} - this format is used by some to simply clarify it IS a variable reference. More often than not you may see it in the following form, ${variable}part2, this allows you to append the string 'part2' as without the
braces bash will look to expand the variable $variablepart2, which more than likely does not exist and if it does you will be returning an unexpected value.

As for quote:

'' - called full quoting and general rule is, what you see is what you get

"" - called partial quoting, this preserves whitespace and metacharacters (ie. *, ?, etc)

See here for fuller details.

The double quotes are the ones I was referring to earlier.
 
Old 12-09-2012, 09:15 PM   #13
fatalerror0x00
Member
 
Registered: Oct 2012
Location: Holden, ME, USA
Distribution: SlackWare64 14.00
Posts: 185

Original Poster
Rep: Reputation: 0
DISREGARD EDITING LAST SCRIPT FILE I have made some changes and will give you what I have now. Have not done quoting added list command but had to remove clear from being used in the function it self to make loading saved game files work out properly the way i want. this has not been tested but no reason it shouldn't work properly as I took the code from another section and changed variable names is all. to see my latest chages with while statements and the list please refere to startMenu_beta.bash I know theres a better way to do my while loop too that I just found and I'll see what you guys give me and see what can be found and made of from you guys I'm out for the night

Thank you for giving me that and okay so far this night looking at this script is getting frustrating and overwhelming so I'm gonna call it off to bed and hopefully around early noon I can have something up thank you everyone

what about this if I'm appending text to a variable like my $savedGame_fileName.3ysf stuff what about those should it be written as

properly with ${variable} form if needed along with quotes cause I'm a little puzzled how that works out "properlY" I was gonna write the combinations I thought it could be but I decided that was too much :P also I still have to quote ${variable} right from what you recommended correct? Thank you

I think my issue while creating my while loops in other sections is when involving the check for a files existance it seems to throw errors so I guess where all the rest are the same I'm done with while loops since it's very puzzling and I have examples of how to do it I believe properly but it's just not working it seems so maybe I'm doing something wrong maybe if you could do one for me I can do the other one or two that are left I think one but yeah maybe that would help I had to ask you to do something like that for me but I may need the favor :P

you can base it off the last version I gave you of the files nothing has really changed that should make a difference
Attached Files
File Type: txt game.txt (6.7 KB, 9 views)

Last edited by fatalerror0x00; 12-09-2012 at 09:51 PM.
 
Old 12-09-2012, 09:30 PM   #14
konsolebox
Senior Member
 
Registered: Oct 2005
Distribution: Gentoo, Slackware, LFS
Posts: 2,242
Blog Entries: 15

Rep: Reputation: 233Reputation: 233Reputation: 233
Soon enough if you find yourself making multiple scripts you might need a helper to have the loading managed easily: http://loader.sourceforge.net/
Just like an example program like this one: http://sourceforge.net/p/playshell/c...h=ref%2Fmaster
 
Old 12-09-2012, 09:51 PM   #15
fatalerror0x00
Member
 
Registered: Oct 2012
Location: Holden, ME, USA
Distribution: SlackWare64 14.00
Posts: 185

Original Poster
Rep: Reputation: 0
Sweet I will have to look into that sometime Thanks
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Variables and Mkvextract in a bash script and a good resource for bash help? gohmifune Linux - General 9 04-13-2011 08:37 AM
SSH connection from BASH script stops further BASH script commands tardis1 Linux - Newbie 3 12-06-2010 08:56 AM
[SOLVED] #!/bin/sh vs #!/bin/bash -- script executes differently; each way = different bugs GrapefruiTgirl Programming 21 12-16-2009 05:30 PM
[SOLVED] Finding bugs in bash scripts, Analyis tool for bash traene Programming 2 10-31-2009 11:42 AM
[SOLVED] Using a long Bash command including single quotes and pipes in a Bash script antcore Linux - General 9 07-22-2009 11:10 AM


All times are GMT -5. The time now is 03:18 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration