Where can I find a good boilerplate bashrc? Announcing the arrival of Valued Associate #679:...

Significance of Cersei's obsession with elephants?

Can a new player join a group only when a new campaign starts?

Chinese Seal on silk painting - what does it mean?

Why should I vote and accept answers?

SF book about people trapped in a series of worlds they imagine

If Windows 7 doesn't support WSL, then what does Linux subsystem option mean?

Is there any word for a place full of confusion?

Morning, Afternoon, Night Kanji

Central Vacuuming: Is it worth it, and how does it compare to normal vacuuming?

Do I really need to have a message in a novel to appeal to readers?

When a candle burns, why does the top of wick glow if bottom of flame is hottest?

Sum letters are not two different

How come Sam didn't become Lord of Horn Hill?

An adverb for when you're not exaggerating

What order were files/directories outputted in dir?

Do wooden building fires get hotter than 600°C?

Maximum summed subsequences with non-adjacent items

Effects on objects due to a brief relocation of massive amounts of mass

Can anything be seen from the center of the Boötes void? How dark would it be?

What do you call the main part of a joke?

Take 2! Is this homebrew Lady of Pain warlock patron balanced?

How could we fake a moon landing now?

What is the difference between globalisation and imperialism?

How do I use the new nonlinear finite element in Mathematica 12 for this equation?



Where can I find a good boilerplate bashrc?



Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 23, 2019 at 00:00UTC (8:00pm US/Eastern)
2019 Community Moderator Election Results
Why I closed the “Why is Kali so hard” questionHow can I create a local function in my bashrc?bashrc that calls other bashrc depending on linux distroHow to call a “sub” .inputrc? (Like in .bashrc, where you can “source sub_script.sh”)bashrc lazy substitutionWhere is .bashrc file found in Linux?I can't find .bashrc on distro astroAny occasion where .bashrc is favorable to .bash_profile?.inputrc vs .bashrc settingsRefresh .profile and .bashrcHow can I add find exec command into bashrc?





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}







3















I've used unix/linux at work in the past, and recently started developing on a Mac. I'd always (lovingly) borrow co-workers' bashrc's for a good starting point, such as common aliasing and commands, but I'm a bit at a loss when it comes from building my own from scratch.



Is there a resource that has good "boilerplate" bashrc files (or other shell config files, for that matter) that will have most if not all of what I want -- even stuff I don't know I need yet? ;)










share|improve this question




















  • 1





    a lot of examples are at github, take look at the dotfiles.

    – user55518
    Mar 26 '14 at 17:04






  • 2





    I see, but bash is not markup and there is no such thing like boilerplate. rather public bashrc files and they are always different and depend on what you have installed. I also write this as comment, because it's possible someone has a good resource for you.

    – user55518
    Mar 26 '14 at 17:20






  • 1





    @bersch "boilerplate" does not necessarily, or even usually, refer to "markup" and the OP's terminology here is completely normative: en.wikipedia.org/wiki/Boilerplate_code E.g., the skeleton stuff your system uses to create a default .bashrc is boilerplate.

    – goldilocks
    Mar 26 '14 at 17:32








  • 1





    I keep all of my custom "dot files" in git and the first time I log into a new home directory I do a git init, and a git pull and then I have all my settings that I'm used to. I have branches for different OSes and shells.

    – functionvoid
    Mar 26 '14 at 18:01






  • 2





    @bersh Q.v. /etc/skel/.bashrc == bashrc-boilerplate. The system copies this into new home directories.

    – goldilocks
    Mar 26 '14 at 18:13




















3















I've used unix/linux at work in the past, and recently started developing on a Mac. I'd always (lovingly) borrow co-workers' bashrc's for a good starting point, such as common aliasing and commands, but I'm a bit at a loss when it comes from building my own from scratch.



Is there a resource that has good "boilerplate" bashrc files (or other shell config files, for that matter) that will have most if not all of what I want -- even stuff I don't know I need yet? ;)










share|improve this question




















  • 1





    a lot of examples are at github, take look at the dotfiles.

    – user55518
    Mar 26 '14 at 17:04






  • 2





    I see, but bash is not markup and there is no such thing like boilerplate. rather public bashrc files and they are always different and depend on what you have installed. I also write this as comment, because it's possible someone has a good resource for you.

    – user55518
    Mar 26 '14 at 17:20






  • 1





    @bersch "boilerplate" does not necessarily, or even usually, refer to "markup" and the OP's terminology here is completely normative: en.wikipedia.org/wiki/Boilerplate_code E.g., the skeleton stuff your system uses to create a default .bashrc is boilerplate.

    – goldilocks
    Mar 26 '14 at 17:32








  • 1





    I keep all of my custom "dot files" in git and the first time I log into a new home directory I do a git init, and a git pull and then I have all my settings that I'm used to. I have branches for different OSes and shells.

    – functionvoid
    Mar 26 '14 at 18:01






  • 2





    @bersh Q.v. /etc/skel/.bashrc == bashrc-boilerplate. The system copies this into new home directories.

    – goldilocks
    Mar 26 '14 at 18:13
















3












3








3


0






I've used unix/linux at work in the past, and recently started developing on a Mac. I'd always (lovingly) borrow co-workers' bashrc's for a good starting point, such as common aliasing and commands, but I'm a bit at a loss when it comes from building my own from scratch.



Is there a resource that has good "boilerplate" bashrc files (or other shell config files, for that matter) that will have most if not all of what I want -- even stuff I don't know I need yet? ;)










share|improve this question
















I've used unix/linux at work in the past, and recently started developing on a Mac. I'd always (lovingly) borrow co-workers' bashrc's for a good starting point, such as common aliasing and commands, but I'm a bit at a loss when it comes from building my own from scratch.



Is there a resource that has good "boilerplate" bashrc files (or other shell config files, for that matter) that will have most if not all of what I want -- even stuff I don't know I need yet? ;)







shell bashrc






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Mar 26 '14 at 16:55







pennstatephil

















asked Mar 26 '14 at 16:44









pennstatephilpennstatephil

1185




1185








  • 1





    a lot of examples are at github, take look at the dotfiles.

    – user55518
    Mar 26 '14 at 17:04






  • 2





    I see, but bash is not markup and there is no such thing like boilerplate. rather public bashrc files and they are always different and depend on what you have installed. I also write this as comment, because it's possible someone has a good resource for you.

    – user55518
    Mar 26 '14 at 17:20






  • 1





    @bersch "boilerplate" does not necessarily, or even usually, refer to "markup" and the OP's terminology here is completely normative: en.wikipedia.org/wiki/Boilerplate_code E.g., the skeleton stuff your system uses to create a default .bashrc is boilerplate.

    – goldilocks
    Mar 26 '14 at 17:32








  • 1





    I keep all of my custom "dot files" in git and the first time I log into a new home directory I do a git init, and a git pull and then I have all my settings that I'm used to. I have branches for different OSes and shells.

    – functionvoid
    Mar 26 '14 at 18:01






  • 2





    @bersh Q.v. /etc/skel/.bashrc == bashrc-boilerplate. The system copies this into new home directories.

    – goldilocks
    Mar 26 '14 at 18:13
















  • 1





    a lot of examples are at github, take look at the dotfiles.

    – user55518
    Mar 26 '14 at 17:04






  • 2





    I see, but bash is not markup and there is no such thing like boilerplate. rather public bashrc files and they are always different and depend on what you have installed. I also write this as comment, because it's possible someone has a good resource for you.

    – user55518
    Mar 26 '14 at 17:20






  • 1





    @bersch "boilerplate" does not necessarily, or even usually, refer to "markup" and the OP's terminology here is completely normative: en.wikipedia.org/wiki/Boilerplate_code E.g., the skeleton stuff your system uses to create a default .bashrc is boilerplate.

    – goldilocks
    Mar 26 '14 at 17:32








  • 1





    I keep all of my custom "dot files" in git and the first time I log into a new home directory I do a git init, and a git pull and then I have all my settings that I'm used to. I have branches for different OSes and shells.

    – functionvoid
    Mar 26 '14 at 18:01






  • 2





    @bersh Q.v. /etc/skel/.bashrc == bashrc-boilerplate. The system copies this into new home directories.

    – goldilocks
    Mar 26 '14 at 18:13










1




1





a lot of examples are at github, take look at the dotfiles.

– user55518
Mar 26 '14 at 17:04





a lot of examples are at github, take look at the dotfiles.

– user55518
Mar 26 '14 at 17:04




2




2





I see, but bash is not markup and there is no such thing like boilerplate. rather public bashrc files and they are always different and depend on what you have installed. I also write this as comment, because it's possible someone has a good resource for you.

– user55518
Mar 26 '14 at 17:20





I see, but bash is not markup and there is no such thing like boilerplate. rather public bashrc files and they are always different and depend on what you have installed. I also write this as comment, because it's possible someone has a good resource for you.

– user55518
Mar 26 '14 at 17:20




1




1





@bersch "boilerplate" does not necessarily, or even usually, refer to "markup" and the OP's terminology here is completely normative: en.wikipedia.org/wiki/Boilerplate_code E.g., the skeleton stuff your system uses to create a default .bashrc is boilerplate.

– goldilocks
Mar 26 '14 at 17:32







@bersch "boilerplate" does not necessarily, or even usually, refer to "markup" and the OP's terminology here is completely normative: en.wikipedia.org/wiki/Boilerplate_code E.g., the skeleton stuff your system uses to create a default .bashrc is boilerplate.

– goldilocks
Mar 26 '14 at 17:32






1




1





I keep all of my custom "dot files" in git and the first time I log into a new home directory I do a git init, and a git pull and then I have all my settings that I'm used to. I have branches for different OSes and shells.

– functionvoid
Mar 26 '14 at 18:01





I keep all of my custom "dot files" in git and the first time I log into a new home directory I do a git init, and a git pull and then I have all my settings that I'm used to. I have branches for different OSes and shells.

– functionvoid
Mar 26 '14 at 18:01




2




2





@bersh Q.v. /etc/skel/.bashrc == bashrc-boilerplate. The system copies this into new home directories.

– goldilocks
Mar 26 '14 at 18:13







@bersh Q.v. /etc/skel/.bashrc == bashrc-boilerplate. The system copies this into new home directories.

– goldilocks
Mar 26 '14 at 18:13












1 Answer
1






active

oldest

votes


















4














The Arch Wiki has some example aliases and generic commands that will work in the majority of .bashrc files providing you are using systemd and have sudo installed.



This highlights the problem with the approach you are seeking, and one of the undesirable side effects of copying and pasting someone else's idea of a standard configuration into your shell 's config. You run two risks: introducing material that is not suitable for your environment or, much worse, adding configuration options that are just plain wrong but that the person before you had added because they were similarly misinformed. As an example, look through some .bashrc files in git/hg repositories and note how many export a TERM...



You are much better off starting with whatever your distro ships and then adding options that are familiar and tested by you, documented in the man page or—if you do want to use options in other people's configs—add them one at a time and make sure they do what they are supposed to do.






share|improve this answer
























    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "106"
    };
    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: false,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    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%2funix.stackexchange.com%2fquestions%2f121620%2fwhere-can-i-find-a-good-boilerplate-bashrc%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









    4














    The Arch Wiki has some example aliases and generic commands that will work in the majority of .bashrc files providing you are using systemd and have sudo installed.



    This highlights the problem with the approach you are seeking, and one of the undesirable side effects of copying and pasting someone else's idea of a standard configuration into your shell 's config. You run two risks: introducing material that is not suitable for your environment or, much worse, adding configuration options that are just plain wrong but that the person before you had added because they were similarly misinformed. As an example, look through some .bashrc files in git/hg repositories and note how many export a TERM...



    You are much better off starting with whatever your distro ships and then adding options that are familiar and tested by you, documented in the man page or—if you do want to use options in other people's configs—add them one at a time and make sure they do what they are supposed to do.






    share|improve this answer




























      4














      The Arch Wiki has some example aliases and generic commands that will work in the majority of .bashrc files providing you are using systemd and have sudo installed.



      This highlights the problem with the approach you are seeking, and one of the undesirable side effects of copying and pasting someone else's idea of a standard configuration into your shell 's config. You run two risks: introducing material that is not suitable for your environment or, much worse, adding configuration options that are just plain wrong but that the person before you had added because they were similarly misinformed. As an example, look through some .bashrc files in git/hg repositories and note how many export a TERM...



      You are much better off starting with whatever your distro ships and then adding options that are familiar and tested by you, documented in the man page or—if you do want to use options in other people's configs—add them one at a time and make sure they do what they are supposed to do.






      share|improve this answer


























        4












        4








        4







        The Arch Wiki has some example aliases and generic commands that will work in the majority of .bashrc files providing you are using systemd and have sudo installed.



        This highlights the problem with the approach you are seeking, and one of the undesirable side effects of copying and pasting someone else's idea of a standard configuration into your shell 's config. You run two risks: introducing material that is not suitable for your environment or, much worse, adding configuration options that are just plain wrong but that the person before you had added because they were similarly misinformed. As an example, look through some .bashrc files in git/hg repositories and note how many export a TERM...



        You are much better off starting with whatever your distro ships and then adding options that are familiar and tested by you, documented in the man page or—if you do want to use options in other people's configs—add them one at a time and make sure they do what they are supposed to do.






        share|improve this answer













        The Arch Wiki has some example aliases and generic commands that will work in the majority of .bashrc files providing you are using systemd and have sudo installed.



        This highlights the problem with the approach you are seeking, and one of the undesirable side effects of copying and pasting someone else's idea of a standard configuration into your shell 's config. You run two risks: introducing material that is not suitable for your environment or, much worse, adding configuration options that are just plain wrong but that the person before you had added because they were similarly misinformed. As an example, look through some .bashrc files in git/hg repositories and note how many export a TERM...



        You are much better off starting with whatever your distro ships and then adding options that are familiar and tested by you, documented in the man page or—if you do want to use options in other people's configs—add them one at a time and make sure they do what they are supposed to do.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Mar 26 '14 at 17:38









        jasonwryanjasonwryan

        51k14135190




        51k14135190






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Unix & Linux Stack Exchange!


            • 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%2funix.stackexchange.com%2fquestions%2f121620%2fwhere-can-i-find-a-good-boilerplate-bashrc%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

            Taj Mahal Inhaltsverzeichnis Aufbau | Geschichte | 350-Jahr-Feier | Heutige Bedeutung | Siehe auch |...

            Baia Sprie Cuprins Etimologie | Istorie | Demografie | Politică și administrație | Arii naturale...

            Nicolae Petrescu-Găină Cuprins Biografie | Opera | In memoriam | Varia | Controverse, incertitudini...