Why doesn't my terminal load .profile when I launch it?












0















I am very new to being a developer, and I have just started using Ubuntu. I am currently trying to run elasticbeanstalk CLI on my terminal, but I always get "eb: command not found" error when I type "eb" into the terminal. I can only get it to work if I type in "source ~/.profile" after I start my terminal.



As far as I can tell, I have followed the installation guide pretty closely. My guess is that .profile isn't loaded every time I start the terminal. Is there anyway I can fix/automate this? .bash_profile and .bash_login doesn't exist on home directory, so I don't think that is interfering.



I'm also not familiar with terms like bash, gnome etc, would help if you guys are able to explain in a not-so-technical way.










share|improve this question























  • Bash and Its Startup File Execution Algorithm

    – DavidPostill
    Jan 22 at 9:17











  • Shell initialization files

    – DavidPostill
    Jan 22 at 9:18











  • superuser.com/questions/385766/…

    – user1330614
    Jan 22 at 18:45
















0















I am very new to being a developer, and I have just started using Ubuntu. I am currently trying to run elasticbeanstalk CLI on my terminal, but I always get "eb: command not found" error when I type "eb" into the terminal. I can only get it to work if I type in "source ~/.profile" after I start my terminal.



As far as I can tell, I have followed the installation guide pretty closely. My guess is that .profile isn't loaded every time I start the terminal. Is there anyway I can fix/automate this? .bash_profile and .bash_login doesn't exist on home directory, so I don't think that is interfering.



I'm also not familiar with terms like bash, gnome etc, would help if you guys are able to explain in a not-so-technical way.










share|improve this question























  • Bash and Its Startup File Execution Algorithm

    – DavidPostill
    Jan 22 at 9:17











  • Shell initialization files

    – DavidPostill
    Jan 22 at 9:18











  • superuser.com/questions/385766/…

    – user1330614
    Jan 22 at 18:45














0












0








0








I am very new to being a developer, and I have just started using Ubuntu. I am currently trying to run elasticbeanstalk CLI on my terminal, but I always get "eb: command not found" error when I type "eb" into the terminal. I can only get it to work if I type in "source ~/.profile" after I start my terminal.



As far as I can tell, I have followed the installation guide pretty closely. My guess is that .profile isn't loaded every time I start the terminal. Is there anyway I can fix/automate this? .bash_profile and .bash_login doesn't exist on home directory, so I don't think that is interfering.



I'm also not familiar with terms like bash, gnome etc, would help if you guys are able to explain in a not-so-technical way.










share|improve this question














I am very new to being a developer, and I have just started using Ubuntu. I am currently trying to run elasticbeanstalk CLI on my terminal, but I always get "eb: command not found" error when I type "eb" into the terminal. I can only get it to work if I type in "source ~/.profile" after I start my terminal.



As far as I can tell, I have followed the installation guide pretty closely. My guess is that .profile isn't loaded every time I start the terminal. Is there anyway I can fix/automate this? .bash_profile and .bash_login doesn't exist on home directory, so I don't think that is interfering.



I'm also not familiar with terms like bash, gnome etc, would help if you guys are able to explain in a not-so-technical way.







linux ubuntu bash terminal .profile






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Jan 22 at 7:07









Jeffrey SoongJeffrey Soong

1




1













  • Bash and Its Startup File Execution Algorithm

    – DavidPostill
    Jan 22 at 9:17











  • Shell initialization files

    – DavidPostill
    Jan 22 at 9:18











  • superuser.com/questions/385766/…

    – user1330614
    Jan 22 at 18:45



















  • Bash and Its Startup File Execution Algorithm

    – DavidPostill
    Jan 22 at 9:17











  • Shell initialization files

    – DavidPostill
    Jan 22 at 9:18











  • superuser.com/questions/385766/…

    – user1330614
    Jan 22 at 18:45

















Bash and Its Startup File Execution Algorithm

– DavidPostill
Jan 22 at 9:17





Bash and Its Startup File Execution Algorithm

– DavidPostill
Jan 22 at 9:17













Shell initialization files

– DavidPostill
Jan 22 at 9:18





Shell initialization files

– DavidPostill
Jan 22 at 9:18













superuser.com/questions/385766/…

– user1330614
Jan 22 at 18:45





superuser.com/questions/385766/…

– user1330614
Jan 22 at 18:45










1 Answer
1






active

oldest

votes


















3














~/.profile or ~/.bash_profile is the login script and is not supposed to be loaded for every interactive shell, only by the initial 'login' shell (if one exists). It's a good place to set session-wide environment variables or run one-time things.



To define aliases or set other shell-internal parameters, you should use ~/.bashrc instead.



(Note, you can't avoid having a source ~/.bashrc at the end of your ~/.bash_profile, because due to historical reasons the same 'login' shell that reads profile scripts actually doesn't read ~/.bashrc by default.)






share|improve this answer























    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "3"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1396903%2fwhy-doesnt-my-terminal-load-profile-when-i-launch-it%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    3














    ~/.profile or ~/.bash_profile is the login script and is not supposed to be loaded for every interactive shell, only by the initial 'login' shell (if one exists). It's a good place to set session-wide environment variables or run one-time things.



    To define aliases or set other shell-internal parameters, you should use ~/.bashrc instead.



    (Note, you can't avoid having a source ~/.bashrc at the end of your ~/.bash_profile, because due to historical reasons the same 'login' shell that reads profile scripts actually doesn't read ~/.bashrc by default.)






    share|improve this answer




























      3














      ~/.profile or ~/.bash_profile is the login script and is not supposed to be loaded for every interactive shell, only by the initial 'login' shell (if one exists). It's a good place to set session-wide environment variables or run one-time things.



      To define aliases or set other shell-internal parameters, you should use ~/.bashrc instead.



      (Note, you can't avoid having a source ~/.bashrc at the end of your ~/.bash_profile, because due to historical reasons the same 'login' shell that reads profile scripts actually doesn't read ~/.bashrc by default.)






      share|improve this answer


























        3












        3








        3







        ~/.profile or ~/.bash_profile is the login script and is not supposed to be loaded for every interactive shell, only by the initial 'login' shell (if one exists). It's a good place to set session-wide environment variables or run one-time things.



        To define aliases or set other shell-internal parameters, you should use ~/.bashrc instead.



        (Note, you can't avoid having a source ~/.bashrc at the end of your ~/.bash_profile, because due to historical reasons the same 'login' shell that reads profile scripts actually doesn't read ~/.bashrc by default.)






        share|improve this answer













        ~/.profile or ~/.bash_profile is the login script and is not supposed to be loaded for every interactive shell, only by the initial 'login' shell (if one exists). It's a good place to set session-wide environment variables or run one-time things.



        To define aliases or set other shell-internal parameters, you should use ~/.bashrc instead.



        (Note, you can't avoid having a source ~/.bashrc at the end of your ~/.bash_profile, because due to historical reasons the same 'login' shell that reads profile scripts actually doesn't read ~/.bashrc by default.)







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Jan 22 at 7:18









        grawitygrawity

        241k37508562




        241k37508562






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Super User!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1396903%2fwhy-doesnt-my-terminal-load-profile-when-i-launch-it%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            "Incorrect syntax near the keyword 'ON'. (on update cascade, on delete cascade,)

            Alcedinidae

            Origin of the phrase “under your belt”?