Bashrc Syntax Error Near Unexpected Token
Contents |
communities company blog Stack Exchange Inbox Reputation and Badges sign up log in tour help Tour Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn
Bashrc Syntax Error Near Unexpected Token Fi
more about Stack Overflow the company Business Learn more about hiring developers or bash syntax error posting ads with us Ask Ubuntu Questions Tags Users Badges Unanswered Ask Question _ Ask Ubuntu is a question and answer
Bash Syntax Error Near Unexpected Token '
site for Ubuntu users and developers. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise syntax error near unexpected token c to the top bash: /home/gaja/.bashrc: line 4: syntax error near unexpected token `(' up vote 0 down vote favorite When I open the Terminal I got the following the errors. bash: /home/gaja/.bashrccu: No such file or directory bash: /home/gaja/.bashrc: line 4: syntax error near unexpected token (' bash: /home/gaja/.bashrc: line 4: see /usr/share/doc/bash/examples/startup-files (in the package bash-doc)' bash bashrc share|improve this question edited Jan 4 '14 at 13:07 souravc 13.6k34672 syntax error near unexpected token do asked Jan 4 '14 at 12:57 raja 30138 3 can you add the output of head -n 5 ~/.bashrc? –souravc Jan 4 '14 at 13:05 how to add the output please send information. –raja Jan 4 '14 at 13:32 add a comment| 1 Answer 1 active oldest votes up vote 0 down vote accepted To get rid of the error messages use the following command in your terminal, cp /etc/skel/.bashrc ~/ It will replace your corrupt ~/.bashrc with a fresh one. But any changes in ~/.bashrc made by you (if any) will be lost. Do not forget to source the ~/.bashrc, write in terminal, source ~/.bashrc To continue with your existing ~/.bashrc you need to add the output of head -n 5 ~/.bashrc So that we can point out the syntax error in your existing ~/.bashrc share|improve this answer edited Jan 5 '14 at 14:23 answered Jan 5 '14 at 5:01 souravc 13.6k34672 Thanks sourav, it works fine. but i found a new problem. I couldn't install anything. When i use install command, the following error appears. “ dpkg: warning: 'tar' not found in PATH or not executable dpkg: error: 1 expected program not found in PATH or not executable Note: root'
kevinae91 Member Registered: 2012-09-26 Posts: 32 Syntax error near unexpected token >> bash.bashrc I'm trying to color and reformat my console but for some reason I continue to get this
Syntax Error Near Unexpected Token Else
error when I log in to my box: -bash: /etc/bash.bashrc: line 27: syntax error near unexpected token javascript syntax error near unexpected token ')' 'bash: /etc/bash.bashrc: line 27: '27 xterm|rxvt|Eterm|aterm|kterm|gnome)So anyways, I'm just using a standard
Syntax Error Near Unexpected Token Then
bash.bashrc template that was posted on here: https://wiki.archlinux.org/index.php/Co … ep_by_step and I am using the main bash prompt and I'm not running any gui. I'm not really sure what the http://askubuntu.com/questions/399958/bash-home-gaja-bashrc-line-4-syntax-error-near-unexpected-token problem is and I have tried a few different things but it always seems to hang on that error.I was hoping I could get a little help with this, as I would greatly appreciate any and all help. Thanks. Last edited by kevinae91 (2013-09-25 19:52:22) Offline #2 2013-09-25 20:01:42 karol Archivist Registered: 2009-05-06 Posts: 25,433 Re: Syntax error near unexpected token https://bbs.archlinux.org/viewtopic.php?id=170354 >> bash.bashrc A guess: remove the '27' from the beginning of the line. There should be no line numbers in your .bashrc.If it doesn't work, post your /etc/bash.bashrc. Offline #3 2013-09-25 20:08:33 Jasonvw Member From: Detroit, Michigan Registered: 2011-12-23 Posts: 22 Re: Syntax error near unexpected token >> bash.bashrc Are you sure is it an exact copy of what is on the wiki? That seems OK to me, but that error is seeming to indicate that it's not picking up the 'case' section properly. Hard to tell really. RAID !=backup Offline #4 2013-09-25 20:14:56 kevinae91 Member Registered: 2012-09-26 Posts: 32 Re: Syntax error near unexpected token >> bash.bashrc Thanks for the quick replies guys, very much appreciated. I'm leaving for class right now so I can't paste anything but as soon as I get there I will try some things and if I can't get them to work I will post my bash file here. However, karol, your post has made me realize something. I copied this bash file from a different site that had line numbers as per the "
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the http://stackoverflow.com/questions/25781257/why-am-i-getting-a-syntax-near-unexpected-token-newline-error workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; syntax error it only takes a minute: Sign up Why am I getting a syntax near unexpected token newline error? up vote 0 down vote favorite I am trying to create a .bashrc file with the android dev kit in Ubuntu. Only problem is, when i edit/ add to the bashrc file, I get a "syntax error near unexpected token newline". syntax error near I posted the code where the error is, specifially between android SDK home token and android NDK token. Thanks for the help #Android SDK Home export ANDROID_SDK= #ANDROID NDK Home export NDK=~/android-ndk-r10b export PATH=$PATH: $ANDROID_SDK/tools:$ANDROID_SDK/platform-tools linux bash share|improve this question asked Sep 11 '14 at 7:10 user3299894 33 Don't forget to accept an answer by clicking on the ✔ next to it. This will mean that your question is marked as solved. –Tom Fenech Sep 11 '14 at 13:03 add a comment| 2 Answers 2 active oldest votes up vote 1 down vote I guess that you have read something like this in a guide somewhere: Add the following lines to your .bashrc file: export ANDROID_SDK=