edit path environment variable to include current working directory
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
And usually folks want the current directory to be searched first - the dot thing is the current directory try:
Code:
export PATH=.:$PATH
The only problem with this is if you create a program that has the same name as a standard utility, like cut or ls, PATH will find the local version first.
With no dot in the PATH, you can force the use of the local directory - example running a file called mycode:
Here is my .bashrc file, where do I add the pATH info.
# .bashrc
# User specific aliases and functions
# Source global definitions
if [ -f /etc/bashrc ]; then
. /etc/bashrc
ource global definitions
if [ -f /etc/bashrc ]; then
. /etc/bashrc
fi
~
~
~
~
~
~
~
~
At the end (you could at the beginning or elsewhere but I put mine at the end . I would put a new line after what is there just for the sake of readability. You can even put in a comment line beginning with a # to let yourself know what it is for.
Regarding the PATH --- /home/dave/.bashrc --- you answered in a previous question, what .bshrc file do I use if I dont have any in the specified directory, I only have the /etc/bashrc directory and I have already tried including the path of my javac and java files and it does not work.
Quote:
Originally posted by jim mcnamara
Code:
/home/dave/.bashrc
And usually folks want the current directory to be searched first - the dot thing is the current directory try:
Code:
export PATH=.:$PATH
The only problem with this is if you create a program that has the same name as a standard utility, like cut or ls, PATH will find the local version first.
With no dot in the PATH, you can force the use of the local directory - example running a file called mycode:
Regarding the PATH --- /home/dave/.bashrc --- you answered in a previous question, what .bshrc file do I use if I dont have any in the specified directory, I only have the /etc/bashrc directory and I have already tried including the path of my javac and java files and it does not work.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.