How set more than one paths has to be added to the PATH environment variable and other variable? [duplicate]

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
-3
down vote

favorite













This question already has an answer here:



  • bashrc not loaded on login

    2 answers



I am adding commands to $HOME/.bash_profile file 



export PATH=[PATH_TO_FLUTTER_GIT_DIRECTORY]/flutter/bin:$PATH

export ANDROID_HOME=/home/harsh/SDK

export PATH=$PATH:$ANDROID_HOME/tools


Now I have to run source $HOME/.bash_profile when my system boot every time. Is there any other option to permanent set these paths?



Problem: It's annoying to run this commands again and again when my system boot. Is there a way when I start my system and don't need to add this commands again?




bash environment-variables bash-profile




share|improve this question













marked as duplicate by roaima, Rui F Ribeiro, schily, meuh, Jesse_b Jun 6 at 16:03


This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.














  • Bash should read ~/.bash_profile on startup if it's started as a login shell, so it's not really just "a file". Now, the question is, how do you start Bash, if the login shell startup files don't take effect? In what sort of an environment?
    – ilkkachu
    Jun 6 at 6:30






  • 1




    What is the file actually called, and which shell are you using? You are hopefully aware that various filenames on UNIX-ish systems are "magic" so it really does make a difference.
    – Philip Kendall
    Jun 6 at 6:31










  • So I have to move that commands to .bashrc ? and link to .bash_login
    – Harsh Bhavsar
    Jun 6 at 6:35







  • 3




    Please just edit your question to explain: 1) what you're trying to achieve 2) precisely what you've tried so far (not hiding details like which filename) 3) what's happening. Stop making random guesses as to what you should do until you've explained the issue or we can't really help.
    – Philip Kendall
    Jun 6 at 6:41















up vote
-3
down vote

favorite













This question already has an answer here:



  • bashrc not loaded on login

    2 answers



I am adding commands to $HOME/.bash_profile file 



export PATH=[PATH_TO_FLUTTER_GIT_DIRECTORY]/flutter/bin:$PATH

export ANDROID_HOME=/home/harsh/SDK

export PATH=$PATH:$ANDROID_HOME/tools


Now I have to run source $HOME/.bash_profile when my system boot every time. Is there any other option to permanent set these paths?



Problem: It's annoying to run this commands again and again when my system boot. Is there a way when I start my system and don't need to add this commands again?




bash environment-variables bash-profile




share|improve this question













marked as duplicate by roaima, Rui F Ribeiro, schily, meuh, Jesse_b Jun 6 at 16:03


This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.














  • Bash should read ~/.bash_profile on startup if it's started as a login shell, so it's not really just "a file". Now, the question is, how do you start Bash, if the login shell startup files don't take effect? In what sort of an environment?
    – ilkkachu
    Jun 6 at 6:30






  • 1




    What is the file actually called, and which shell are you using? You are hopefully aware that various filenames on UNIX-ish systems are "magic" so it really does make a difference.
    – Philip Kendall
    Jun 6 at 6:31










  • So I have to move that commands to .bashrc ? and link to .bash_login
    – Harsh Bhavsar
    Jun 6 at 6:35







  • 3




    Please just edit your question to explain: 1) what you're trying to achieve 2) precisely what you've tried so far (not hiding details like which filename) 3) what's happening. Stop making random guesses as to what you should do until you've explained the issue or we can't really help.
    – Philip Kendall
    Jun 6 at 6:41













up vote
-3
down vote

favorite









up vote
-3
down vote

favorite












This question already has an answer here:



  • bashrc not loaded on login

    2 answers



I am adding commands to $HOME/.bash_profile file 



export PATH=[PATH_TO_FLUTTER_GIT_DIRECTORY]/flutter/bin:$PATH

export ANDROID_HOME=/home/harsh/SDK

export PATH=$PATH:$ANDROID_HOME/tools


Now I have to run source $HOME/.bash_profile when my system boot every time. Is there any other option to permanent set these paths?



Problem: It's annoying to run this commands again and again when my system boot. Is there a way when I start my system and don't need to add this commands again?




bash environment-variables bash-profile




share|improve this question














This question already has an answer here:



  • bashrc not loaded on login

    2 answers



I am adding commands to $HOME/.bash_profile file 



export PATH=[PATH_TO_FLUTTER_GIT_DIRECTORY]/flutter/bin:$PATH

export ANDROID_HOME=/home/harsh/SDK

export PATH=$PATH:$ANDROID_HOME/tools


Now I have to run source $HOME/.bash_profile when my system boot every time. Is there any other option to permanent set these paths?



Problem: It's annoying to run this commands again and again when my system boot. Is there a way when I start my system and don't need to add this commands again?





This question already has an answer here:



  • bashrc not loaded on login

    2 answers





bash environment-variables bash-profile





share|improve this question












share|improve this question




share|improve this question








edited Jun 6 at 6:51
























asked Jun 6 at 6:18









Harsh Bhavsar

952




952




marked as duplicate by roaima, Rui F Ribeiro, schily, meuh, Jesse_b Jun 6 at 16:03


This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.






marked as duplicate by roaima, Rui F Ribeiro, schily, meuh, Jesse_b Jun 6 at 16:03


This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.













  • Bash should read ~/.bash_profile on startup if it's started as a login shell, so it's not really just "a file". Now, the question is, how do you start Bash, if the login shell startup files don't take effect? In what sort of an environment?
    – ilkkachu
    Jun 6 at 6:30






  • 1




    What is the file actually called, and which shell are you using? You are hopefully aware that various filenames on UNIX-ish systems are "magic" so it really does make a difference.
    – Philip Kendall
    Jun 6 at 6:31










  • So I have to move that commands to .bashrc ? and link to .bash_login
    – Harsh Bhavsar
    Jun 6 at 6:35







  • 3




    Please just edit your question to explain: 1) what you're trying to achieve 2) precisely what you've tried so far (not hiding details like which filename) 3) what's happening. Stop making random guesses as to what you should do until you've explained the issue or we can't really help.
    – Philip Kendall
    Jun 6 at 6:41

















  • Bash should read ~/.bash_profile on startup if it's started as a login shell, so it's not really just "a file". Now, the question is, how do you start Bash, if the login shell startup files don't take effect? In what sort of an environment?
    – ilkkachu
    Jun 6 at 6:30






  • 1




    What is the file actually called, and which shell are you using? You are hopefully aware that various filenames on UNIX-ish systems are "magic" so it really does make a difference.
    – Philip Kendall
    Jun 6 at 6:31










  • So I have to move that commands to .bashrc ? and link to .bash_login
    – Harsh Bhavsar
    Jun 6 at 6:35







  • 3




    Please just edit your question to explain: 1) what you're trying to achieve 2) precisely what you've tried so far (not hiding details like which filename) 3) what's happening. Stop making random guesses as to what you should do until you've explained the issue or we can't really help.
    – Philip Kendall
    Jun 6 at 6:41
















Bash should read ~/.bash_profile on startup if it's started as a login shell, so it's not really just "a file". Now, the question is, how do you start Bash, if the login shell startup files don't take effect? In what sort of an environment?
– ilkkachu
Jun 6 at 6:30




Bash should read ~/.bash_profile on startup if it's started as a login shell, so it's not really just "a file". Now, the question is, how do you start Bash, if the login shell startup files don't take effect? In what sort of an environment?
– ilkkachu
Jun 6 at 6:30




1




1




What is the file actually called, and which shell are you using? You are hopefully aware that various filenames on UNIX-ish systems are "magic" so it really does make a difference.
– Philip Kendall
Jun 6 at 6:31




What is the file actually called, and which shell are you using? You are hopefully aware that various filenames on UNIX-ish systems are "magic" so it really does make a difference.
– Philip Kendall
Jun 6 at 6:31












So I have to move that commands to .bashrc ? and link to .bash_login
– Harsh Bhavsar
Jun 6 at 6:35





So I have to move that commands to .bashrc ? and link to .bash_login
– Harsh Bhavsar
Jun 6 at 6:35





3




3




Please just edit your question to explain: 1) what you're trying to achieve 2) precisely what you've tried so far (not hiding details like which filename) 3) what's happening. Stop making random guesses as to what you should do until you've explained the issue or we can't really help.
– Philip Kendall
Jun 6 at 6:41





Please just edit your question to explain: 1) what you're trying to achieve 2) precisely what you've tried so far (not hiding details like which filename) 3) what's happening. Stop making random guesses as to what you should do until you've explained the issue or we can't really help.
– Philip Kendall
Jun 6 at 6:41











1 Answer
1






active

oldest

votes

















up vote
-2
down vote













You have to add entries to ".bashrc" file to create persistent environment variables for a user. Please see this for the detailed explanation.






share|improve this answer

















  • 2




    Using .bash_profile should work too, provided that 1) the shell is a login shell, or 2) .bash_profile is sourced by .bashrc. In fact, I'd argue that .bash_profile is the correct place for setting up one's environment, while .bashrc is for things specifically related to interactive shell sessions (such as setting one's prompt, displaying a calendar or uptime etc.).
    – Kusalananda
    Jun 6 at 6:40







  • 1




    This is at best misleading and at worst actively wrong. There are plenty more config files than ~/.bashrc and /etc/profile.
    – Philip Kendall
    Jun 6 at 6:44

















1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes








up vote
-2
down vote













You have to add entries to ".bashrc" file to create persistent environment variables for a user. Please see this for the detailed explanation.






share|improve this answer

















  • 2




    Using .bash_profile should work too, provided that 1) the shell is a login shell, or 2) .bash_profile is sourced by .bashrc. In fact, I'd argue that .bash_profile is the correct place for setting up one's environment, while .bashrc is for things specifically related to interactive shell sessions (such as setting one's prompt, displaying a calendar or uptime etc.).
    – Kusalananda
    Jun 6 at 6:40







  • 1




    This is at best misleading and at worst actively wrong. There are plenty more config files than ~/.bashrc and /etc/profile.
    – Philip Kendall
    Jun 6 at 6:44














up vote
-2
down vote













You have to add entries to ".bashrc" file to create persistent environment variables for a user. Please see this for the detailed explanation.






share|improve this answer

















  • 2




    Using .bash_profile should work too, provided that 1) the shell is a login shell, or 2) .bash_profile is sourced by .bashrc. In fact, I'd argue that .bash_profile is the correct place for setting up one's environment, while .bashrc is for things specifically related to interactive shell sessions (such as setting one's prompt, displaying a calendar or uptime etc.).
    – Kusalananda
    Jun 6 at 6:40







  • 1




    This is at best misleading and at worst actively wrong. There are plenty more config files than ~/.bashrc and /etc/profile.
    – Philip Kendall
    Jun 6 at 6:44












up vote
-2
down vote










up vote
-2
down vote









You have to add entries to ".bashrc" file to create persistent environment variables for a user. Please see this for the detailed explanation.






share|improve this answer













You have to add entries to ".bashrc" file to create persistent environment variables for a user. Please see this for the detailed explanation.







share|improve this answer













share|improve this answer



share|improve this answer











answered Jun 6 at 6:36









TheGeek

1286




1286







  • 2




    Using .bash_profile should work too, provided that 1) the shell is a login shell, or 2) .bash_profile is sourced by .bashrc. In fact, I'd argue that .bash_profile is the correct place for setting up one's environment, while .bashrc is for things specifically related to interactive shell sessions (such as setting one's prompt, displaying a calendar or uptime etc.).
    – Kusalananda
    Jun 6 at 6:40







  • 1




    This is at best misleading and at worst actively wrong. There are plenty more config files than ~/.bashrc and /etc/profile.
    – Philip Kendall
    Jun 6 at 6:44












  • 2




    Using .bash_profile should work too, provided that 1) the shell is a login shell, or 2) .bash_profile is sourced by .bashrc. In fact, I'd argue that .bash_profile is the correct place for setting up one's environment, while .bashrc is for things specifically related to interactive shell sessions (such as setting one's prompt, displaying a calendar or uptime etc.).
    – Kusalananda
    Jun 6 at 6:40







  • 1




    This is at best misleading and at worst actively wrong. There are plenty more config files than ~/.bashrc and /etc/profile.
    – Philip Kendall
    Jun 6 at 6:44







2




2




Using .bash_profile should work too, provided that 1) the shell is a login shell, or 2) .bash_profile is sourced by .bashrc. In fact, I'd argue that .bash_profile is the correct place for setting up one's environment, while .bashrc is for things specifically related to interactive shell sessions (such as setting one's prompt, displaying a calendar or uptime etc.).
– Kusalananda
Jun 6 at 6:40





Using .bash_profile should work too, provided that 1) the shell is a login shell, or 2) .bash_profile is sourced by .bashrc. In fact, I'd argue that .bash_profile is the correct place for setting up one's environment, while .bashrc is for things specifically related to interactive shell sessions (such as setting one's prompt, displaying a calendar or uptime etc.).
– Kusalananda
Jun 6 at 6:40





1




1




This is at best misleading and at worst actively wrong. There are plenty more config files than ~/.bashrc and /etc/profile.
– Philip Kendall
Jun 6 at 6:44




This is at best misleading and at worst actively wrong. There are plenty more config files than ~/.bashrc and /etc/profile.
– Philip Kendall
Jun 6 at 6:44


-

Popular posts from this blog

How to check contact read email or not when send email to Individual?

Image
Clash Royale CLAN TAG #URR8PPP up vote 1 down vote favorite I'm using WordPress 4.9.8, CiviCRM to 5.5.1, I usually send email to contact by Search> Find contacts View contact details Action> Send email Send email ok, Contact received mail ok like picture But status only Email sent though contact read email or not. So, can CiviCRM can change status to Email read when contact read email? wordpress email share | improve this question asked Sep 26 at 0:12 ToanLuong 49 9 add a comment  |  up vote 1 down vote favorite I'm using WordPress 4.9.8, CiviCRM to 5.5.1, I usually send email to contact by Search> Find contacts View contact details Action> Send email Send email ok, Contact received mail ok like picture But status only Email sent though contact read email or not. So, can CiviCRM can change status to Email read when contact read email? wordpress email share | improve this questi...
Read more

Displaying single band from multi-band raster using QGIS

Image
Clash Royale CLAN TAG #URR8PPP 1 How can I extract a single band from multi-band raster in QGIS? I have an remote sensed image which has 6 bands (including NDVI band), I want to display each band separately, but have no idea how to do. I have seen some questions similar here but none worked for me. The original image (has 6 bands) is: I want to display the band 6 which should be like this: But I tried gdal_translate, and couldn't get the correct result. What I have got is: qgis raster multi-band share | improve this question edited Mar 5 at 0:53 Summer asked Mar 4 at 6:42 Summer Summer 23 6 Is this any help gis.stackexchange.com/questions/220658/… ? if not gis.stackexchange.com/questions/62133/… might help. – Michael Stimson Mar 4 at 6:46 Thanks for answering but when I used gdal_translate, qgis showed that 'Error 4: Kayena.tif: No such file or directory". Would you know how to fi...
Read more

How many registers does an x86_64 CPU actually have?

Image
Clash Royale CLAN TAG #URR8PPP up vote 2 down vote favorite I am currently learning reverse engineering and am studying the flags register. I had in my mind that rflags was just another name for one of the 16 general purpose registers, for example rax or rbx . But it looks like rflags is actually an additional register. So that makes 17 registers in total... how many more could there be? I have spent at least an hour on this and found numerous different answers. The best answer so far is this, which says that there are 40 registers in total. 16 General Purpose Registers 2 Status Registers 6 Code Segment Registers 16 SSE Registers 8 FPU/MMX Registers But if I add that up, I get 48. Could anybody provide an official answer on how many registers an x86_64 CPU has (e.g. an Intel i7). Additionally, I have seen references to 'hardware' and 'architectural' registers. What are those registers and how many are there? register x86-64 share | improve this...
Read more