clear out all variables without closing terminal












9















I want to know how to clear all variables which I defined in command prompt without closing terminal ?



for example, if I set a variable in command prompt as:



$ a=1


now I want to delete the variable $a (and many other variables defined in similar way) without closing terminal. I could use unset but it will be hectic if there are large no. of variables






shell environment-variables







share|improve this question




















  • 2





    exec "$0"maybe - but it's hard to tell what you mean by global.

    – mikeserv
    Dec 10 '14 at 23:07






  • 3





    Why do you want to do that?

    – Hauke Laging
    Dec 10 '14 at 23:12






  • 1





    @HaukeLaging I am working with arrays using script. I sometimes add one element to it. because of which I cant run the script with old values(since array is changed). i have to close the terminal and start a new session again. I hope I made clear. if not please let me know :)

    – Edward Torvalds
    Dec 10 '14 at 23:18








  • 1





    @muru - he gets a list saved to a $var with var=$(declare -p +F); then passes that as an argument to a function which does echo "${2%%=*}". That answer has a few problems with sheer size - but it should work if your environment isn't huge.

    – mikeserv
    Dec 10 '14 at 23:34






  • 3





    I have no idea what you're trying to do. Are you talking about an interactive shell or a script? Variables set in a script executed from an interactive shell don't affect the parent shell. Tell us what you want to achieve, not which dead end you're pursuing.

    – Gilles
    Dec 10 '14 at 23:49
















9















I want to know how to clear all variables which I defined in command prompt without closing terminal ?



for example, if I set a variable in command prompt as:



$ a=1


now I want to delete the variable $a (and many other variables defined in similar way) without closing terminal. I could use unset but it will be hectic if there are large no. of variables






shell environment-variables







share|improve this question




















  • 2





    exec "$0"maybe - but it's hard to tell what you mean by global.

    – mikeserv
    Dec 10 '14 at 23:07






  • 3





    Why do you want to do that?

    – Hauke Laging
    Dec 10 '14 at 23:12






  • 1





    @HaukeLaging I am working with arrays using script. I sometimes add one element to it. because of which I cant run the script with old values(since array is changed). i have to close the terminal and start a new session again. I hope I made clear. if not please let me know :)

    – Edward Torvalds
    Dec 10 '14 at 23:18








  • 1





    @muru - he gets a list saved to a $var with var=$(declare -p +F); then passes that as an argument to a function which does echo "${2%%=*}". That answer has a few problems with sheer size - but it should work if your environment isn't huge.

    – mikeserv
    Dec 10 '14 at 23:34






  • 3





    I have no idea what you're trying to do. Are you talking about an interactive shell or a script? Variables set in a script executed from an interactive shell don't affect the parent shell. Tell us what you want to achieve, not which dead end you're pursuing.

    – Gilles
    Dec 10 '14 at 23:49














9












9








9


1






I want to know how to clear all variables which I defined in command prompt without closing terminal ?



for example, if I set a variable in command prompt as:



$ a=1


now I want to delete the variable $a (and many other variables defined in similar way) without closing terminal. I could use unset but it will be hectic if there are large no. of variables






shell environment-variables







share|improve this question
















I want to know how to clear all variables which I defined in command prompt without closing terminal ?



for example, if I set a variable in command prompt as:



$ a=1


now I want to delete the variable $a (and many other variables defined in similar way) without closing terminal. I could use unset but it will be hectic if there are large no. of variables






shell environment-variables




shell environment-variables






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Dec 11 '14 at 0:40









Braiam

23.6k2077140




23.6k2077140










asked Dec 10 '14 at 23:06









Edward TorvaldsEdward Torvalds

2,59373263




2,59373263








  • 2





    exec "$0"maybe - but it's hard to tell what you mean by global.

    – mikeserv
    Dec 10 '14 at 23:07






  • 3





    Why do you want to do that?

    – Hauke Laging
    Dec 10 '14 at 23:12






  • 1





    @HaukeLaging I am working with arrays using script. I sometimes add one element to it. because of which I cant run the script with old values(since array is changed). i have to close the terminal and start a new session again. I hope I made clear. if not please let me know :)

    – Edward Torvalds
    Dec 10 '14 at 23:18








  • 1





    @muru - he gets a list saved to a $var with var=$(declare -p +F); then passes that as an argument to a function which does echo "${2%%=*}". That answer has a few problems with sheer size - but it should work if your environment isn't huge.

    – mikeserv
    Dec 10 '14 at 23:34






  • 3





    I have no idea what you're trying to do. Are you talking about an interactive shell or a script? Variables set in a script executed from an interactive shell don't affect the parent shell. Tell us what you want to achieve, not which dead end you're pursuing.

    – Gilles
    Dec 10 '14 at 23:49














  • 2





    exec "$0"maybe - but it's hard to tell what you mean by global.

    – mikeserv
    Dec 10 '14 at 23:07






  • 3





    Why do you want to do that?

    – Hauke Laging
    Dec 10 '14 at 23:12






  • 1





    @HaukeLaging I am working with arrays using script. I sometimes add one element to it. because of which I cant run the script with old values(since array is changed). i have to close the terminal and start a new session again. I hope I made clear. if not please let me know :)

    – Edward Torvalds
    Dec 10 '14 at 23:18








  • 1





    @muru - he gets a list saved to a $var with var=$(declare -p +F); then passes that as an argument to a function which does echo "${2%%=*}". That answer has a few problems with sheer size - but it should work if your environment isn't huge.

    – mikeserv
    Dec 10 '14 at 23:34






  • 3





    I have no idea what you're trying to do. Are you talking about an interactive shell or a script? Variables set in a script executed from an interactive shell don't affect the parent shell. Tell us what you want to achieve, not which dead end you're pursuing.

    – Gilles
    Dec 10 '14 at 23:49








2




2





exec "$0"maybe - but it's hard to tell what you mean by global.

– mikeserv
Dec 10 '14 at 23:07





exec "$0"maybe - but it's hard to tell what you mean by global.

– mikeserv
Dec 10 '14 at 23:07




3




3





Why do you want to do that?

– Hauke Laging
Dec 10 '14 at 23:12





Why do you want to do that?

– Hauke Laging
Dec 10 '14 at 23:12




1




1





@HaukeLaging I am working with arrays using script. I sometimes add one element to it. because of which I cant run the script with old values(since array is changed). i have to close the terminal and start a new session again. I hope I made clear. if not please let me know :)

– Edward Torvalds
Dec 10 '14 at 23:18







@HaukeLaging I am working with arrays using script. I sometimes add one element to it. because of which I cant run the script with old values(since array is changed). i have to close the terminal and start a new session again. I hope I made clear. if not please let me know :)

– Edward Torvalds
Dec 10 '14 at 23:18






1




1





@muru - he gets a list saved to a $var with var=$(declare -p +F); then passes that as an argument to a function which does echo "${2%%=*}". That answer has a few problems with sheer size - but it should work if your environment isn't huge.

– mikeserv
Dec 10 '14 at 23:34





@muru - he gets a list saved to a $var with var=$(declare -p +F); then passes that as an argument to a function which does echo "${2%%=*}". That answer has a few problems with sheer size - but it should work if your environment isn't huge.

– mikeserv
Dec 10 '14 at 23:34




3




3





I have no idea what you're trying to do. Are you talking about an interactive shell or a script? Variables set in a script executed from an interactive shell don't affect the parent shell. Tell us what you want to achieve, not which dead end you're pursuing.

– Gilles
Dec 10 '14 at 23:49





I have no idea what you're trying to do. Are you talking about an interactive shell or a script? Variables set in a script executed from an interactive shell don't affect the parent shell. Tell us what you want to achieve, not which dead end you're pursuing.

– Gilles
Dec 10 '14 at 23:49










2 Answers
2






active

oldest

votes


















9














If you do



exec bash


you will use a fresh & new environnement






share|improve this answer
























  • what about exec "$0" ?

    – Edward Torvalds
    Dec 11 '14 at 21:04











  • @edwardtorvalds $0 is the zeroth argument to an executed shell. So, if you're running bash $0 is bash (probably - it might be -bash in a -login shell case depending on version). If you're running a script with a #!/bin/bash bangline, $0 is the path to the script. exec "$0" is probably more flexible, but exec bash is more explicit. If you enter that command at a terminal, bash should recognize it's in an interactive environment and do the equivalent of bash -i - which will get your ~/.bashrc file run as well.

    – mikeserv
    Dec 11 '14 at 21:32





















0














You could use env, which is provided by GNU coreutils (typically preinstalled on GNU/Linux systems):



exec env --ignore-environment "$0"



The exec system call is so that your current process is replaced in-place by the new, environment-less version of your shell.



This has the benefit to also clear any exported environment variables.






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%2f172655%2fclear-out-all-variables-without-closing-terminal%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    2 Answers
    2






    active

    oldest

    votes








    2 Answers
    2






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    9














    If you do



    exec bash


    you will use a fresh & new environnement






    share|improve this answer
























    • what about exec "$0" ?

      – Edward Torvalds
      Dec 11 '14 at 21:04











    • @edwardtorvalds $0 is the zeroth argument to an executed shell. So, if you're running bash $0 is bash (probably - it might be -bash in a -login shell case depending on version). If you're running a script with a #!/bin/bash bangline, $0 is the path to the script. exec "$0" is probably more flexible, but exec bash is more explicit. If you enter that command at a terminal, bash should recognize it's in an interactive environment and do the equivalent of bash -i - which will get your ~/.bashrc file run as well.

      – mikeserv
      Dec 11 '14 at 21:32


















    9














    If you do



    exec bash


    you will use a fresh & new environnement






    share|improve this answer
























    • what about exec "$0" ?

      – Edward Torvalds
      Dec 11 '14 at 21:04











    • @edwardtorvalds $0 is the zeroth argument to an executed shell. So, if you're running bash $0 is bash (probably - it might be -bash in a -login shell case depending on version). If you're running a script with a #!/bin/bash bangline, $0 is the path to the script. exec "$0" is probably more flexible, but exec bash is more explicit. If you enter that command at a terminal, bash should recognize it's in an interactive environment and do the equivalent of bash -i - which will get your ~/.bashrc file run as well.

      – mikeserv
      Dec 11 '14 at 21:32
















    9












    9








    9







    If you do



    exec bash


    you will use a fresh & new environnement






    share|improve this answer













    If you do



    exec bash


    you will use a fresh & new environnement







    share|improve this answer












    share|improve this answer



    share|improve this answer










    answered Dec 11 '14 at 19:46









    Gilles QuenotGilles Quenot

    16.2k13951




    16.2k13951













    • what about exec "$0" ?

      – Edward Torvalds
      Dec 11 '14 at 21:04











    • @edwardtorvalds $0 is the zeroth argument to an executed shell. So, if you're running bash $0 is bash (probably - it might be -bash in a -login shell case depending on version). If you're running a script with a #!/bin/bash bangline, $0 is the path to the script. exec "$0" is probably more flexible, but exec bash is more explicit. If you enter that command at a terminal, bash should recognize it's in an interactive environment and do the equivalent of bash -i - which will get your ~/.bashrc file run as well.

      – mikeserv
      Dec 11 '14 at 21:32





















    • what about exec "$0" ?

      – Edward Torvalds
      Dec 11 '14 at 21:04











    • @edwardtorvalds $0 is the zeroth argument to an executed shell. So, if you're running bash $0 is bash (probably - it might be -bash in a -login shell case depending on version). If you're running a script with a #!/bin/bash bangline, $0 is the path to the script. exec "$0" is probably more flexible, but exec bash is more explicit. If you enter that command at a terminal, bash should recognize it's in an interactive environment and do the equivalent of bash -i - which will get your ~/.bashrc file run as well.

      – mikeserv
      Dec 11 '14 at 21:32



















    what about exec "$0" ?

    – Edward Torvalds
    Dec 11 '14 at 21:04





    what about exec "$0" ?

    – Edward Torvalds
    Dec 11 '14 at 21:04













    @edwardtorvalds $0 is the zeroth argument to an executed shell. So, if you're running bash $0 is bash (probably - it might be -bash in a -login shell case depending on version). If you're running a script with a #!/bin/bash bangline, $0 is the path to the script. exec "$0" is probably more flexible, but exec bash is more explicit. If you enter that command at a terminal, bash should recognize it's in an interactive environment and do the equivalent of bash -i - which will get your ~/.bashrc file run as well.

    – mikeserv
    Dec 11 '14 at 21:32







    @edwardtorvalds $0 is the zeroth argument to an executed shell. So, if you're running bash $0 is bash (probably - it might be -bash in a -login shell case depending on version). If you're running a script with a #!/bin/bash bangline, $0 is the path to the script. exec "$0" is probably more flexible, but exec bash is more explicit. If you enter that command at a terminal, bash should recognize it's in an interactive environment and do the equivalent of bash -i - which will get your ~/.bashrc file run as well.

    – mikeserv
    Dec 11 '14 at 21:32















    0














    You could use env, which is provided by GNU coreutils (typically preinstalled on GNU/Linux systems):



    exec env --ignore-environment "$0"



    The exec system call is so that your current process is replaced in-place by the new, environment-less version of your shell.



    This has the benefit to also clear any exported environment variables.






    share|improve this answer




























      0














      You could use env, which is provided by GNU coreutils (typically preinstalled on GNU/Linux systems):



      exec env --ignore-environment "$0"



      The exec system call is so that your current process is replaced in-place by the new, environment-less version of your shell.



      This has the benefit to also clear any exported environment variables.






      share|improve this answer


























        0












        0








        0







        You could use env, which is provided by GNU coreutils (typically preinstalled on GNU/Linux systems):



        exec env --ignore-environment "$0"



        The exec system call is so that your current process is replaced in-place by the new, environment-less version of your shell.



        This has the benefit to also clear any exported environment variables.






        share|improve this answer













        You could use env, which is provided by GNU coreutils (typically preinstalled on GNU/Linux systems):



        exec env --ignore-environment "$0"



        The exec system call is so that your current process is replaced in-place by the new, environment-less version of your shell.



        This has the benefit to also clear any exported environment variables.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered 21 mins ago









        user30747user30747

        1212




        1212






























            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%2f172655%2fclear-out-all-variables-without-closing-terminal%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

            Loup dans la culture

            Image
            Loups sur une enluminure du Bestiaire d'Aberdeen Le loup est l'animal le plus emblématique de l'histoire de l'Eurasie, il était à l'honneur durant l'Antiquité chez la totalité des anciens peuples européens [ 1 ] . Sommaire 1 Le loup dans la mythologie 2 Les loups dans le folklore 2.1 L'évolution des mentalités 2.2 Le loup dans la psychanalyse 3 Le loup dans les œuvres culturelles 3.1 Le loup dans la littérature 3.1.1 Fables 3.1.2 Poésie 3.1.3 Romans 3.1.4 Littérature jeunesse 3.1.4.1 Quelques titres d'albums contemporains 3.1.5 Bande dessinée 3.2 Le loup à l'écran 3.2.1 Le cinéma et la télévision 3.2.2 Documentaires 3.2.3 Dessins animés 3.2.4 Jeux vidéo 3.3 Le loup en peinture et en sculpture 3.4 Le loup dans les œuvres musicales 4 Le loup et les noms propres 5 Bibliographie 6 Notes et références 7 Voir aussi 7.1 Articles connexes
            Read more

            How to solve the problem of ntp “Unable to contact time server” from KDE?

            Image
            1 0 I want to set date and time automatically but this error appears when I try to .. I'm using openSUSE, I tried different servers but it didn't work either, help please! It doesn't seem to be a network problem: $ ping pool.ntp.org 64 bytes from 41.78.128.17: icmp_seq=1 ttl=41 time=260 ms To the question of whether ntpd is installed and running: $ ps -C ntpd PID TTY TIME CMD i.e. there's no ntpd process running. $ rpm -qa | grep ntp yast2-ntp-client-3.1.12-1.7.noarch ntp-4.2.6p5-25.2.1.i586 Further information from the comments: $ sudo ntpdate pool.ntp.org 25 Sep 19:41:51 ntpdate[3162]: no server suitable for synchronization found networking kde opensuse ntp ntpd sh
            Read more

            ASUS Zenbook UX433/UX333 — Configure Touchpad-embedded numpad on Linux

            Image
            0 1 I have an ASUS Zenbook UX433,on which ASUS decided to innovate by embedding a Numpad inside the touchpad (see picture 1). Toggling between classic touchpad mode and numpad (also turns the touchpad LEDs on) can be done through the golden button in the top-right corner of the touchpad. However, on my Manjaro arch Linux config, this behavior does not work by default and I can only use the touchpad, no numpad. Has anyone been able to configure the numpad to work on Linux, or have any idea how this could be achieved? EDIT1: I have had a look at the official Windows drivers for the UX433FA TouchPad, but was not able to make anything of it. I tried installing them on Linux using tools like NDISWrapper, but they do not detect the TouchPad/Numpad hardware, and my understanding of drivers is too limited.
            Read more