cd ~ is possible but why can't we cd ~“$USER” or cd ~$USER

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











up vote
8
down vote

favorite
2












I am curious why can't we switch to a user's home director with either



$ cd ~"$USER"


or



$ cd ~$USER






share|improve this question

















  • 4




    Because it's so much simpler just to type "cd"?
    – jamesqf
    May 17 at 18:11






  • 7




    @jamesqf, we all know what can be done.. the question here is about what can not be done and why?
    – Neo_Returns
    May 17 at 18:52















up vote
8
down vote

favorite
2












I am curious why can't we switch to a user's home director with either



$ cd ~"$USER"


or



$ cd ~$USER






share|improve this question

















  • 4




    Because it's so much simpler just to type "cd"?
    – jamesqf
    May 17 at 18:11






  • 7




    @jamesqf, we all know what can be done.. the question here is about what can not be done and why?
    – Neo_Returns
    May 17 at 18:52













up vote
8
down vote

favorite
2









up vote
8
down vote

favorite
2






2





I am curious why can't we switch to a user's home director with either



$ cd ~"$USER"


or



$ cd ~$USER






share|improve this question













I am curious why can't we switch to a user's home director with either



$ cd ~"$USER"


or



$ cd ~$USER








share|improve this question












share|improve this question




share|improve this question








edited May 17 at 14:43









ilkkachu

48.1k669133




48.1k669133









asked May 17 at 14:14









Neo_Returns

17311




17311







  • 4




    Because it's so much simpler just to type "cd"?
    – jamesqf
    May 17 at 18:11






  • 7




    @jamesqf, we all know what can be done.. the question here is about what can not be done and why?
    – Neo_Returns
    May 17 at 18:52













  • 4




    Because it's so much simpler just to type "cd"?
    – jamesqf
    May 17 at 18:11






  • 7




    @jamesqf, we all know what can be done.. the question here is about what can not be done and why?
    – Neo_Returns
    May 17 at 18:52








4




4




Because it's so much simpler just to type "cd"?
– jamesqf
May 17 at 18:11




Because it's so much simpler just to type "cd"?
– jamesqf
May 17 at 18:11




7




7




@jamesqf, we all know what can be done.. the question here is about what can not be done and why?
– Neo_Returns
May 17 at 18:52





@jamesqf, we all know what can be done.. the question here is about what can not be done and why?
– Neo_Returns
May 17 at 18:52











5 Answers
5






active

oldest

votes

















up vote
20
down vote



accepted










That very much depends on the shell and the order the expansions are done in those shells.



~$user expands to the home directory of the user whose name is stored in $user in csh (where that ~user feature comes from), AT&T ksh, zsh, fish.



Note however these variations:



$ u=daemon/xxx csh -c 'echo ~$u'
/usr/sbin/xxx # same in zsh/fish
$ u=daemon/xxx ksh93 -c 'echo ~$u'
~daemon/xxx

$ u=daemon/xxx csh -c 'echo ~"$u"'
Unknown user: daemon/xxx.
$ u=daemon/xxx zsh -c 'echo ~"$u"'
/usr/sbin/x # same in fish

$ u=" daemon" csh -c 'echo ~$u'
/home/stephane daemon
$ u=" daemon" zsh -c 'echo ~$u'
~ daemon # same in ksh/fish

$ u="/daemon" csh -c 'echo ~$u'
/home/stephane/daemon # same in zsh
$ u="/daemon" fish -c 'echo ~$u'
~/daemon # same in ksh


It expands to the home directory of the user named literally $user in bash (provided that user exists, which is very unlikely of course).



And to neither in pdksh, dash, yash, presumably because they don't consider $user to be a valid user name.






share|improve this answer























  • Can you please suggest me where can I learn more about expansion in various shells.
    – Neo_Returns
    May 17 at 14:30







  • 6




    @Neo_Returns, their respective manuals, and when that's not clearly documented, with trial and error and the source code for those where it's available...
    – Stéphane Chazelas
    May 17 at 14:37

















up vote
10
down vote













Tilde expansion is a separate step in the processing of the command line. It happens just before variable expansion.



If the tilde is followed by something other than a slash, it will expand to the home directory of the user whose name is following the tilde, as in, for example, ~otheruser. Since $USER is not expanded at that point and since it's unlikely to correspond to a valid username, the tilde is left unexpanded.



$USER is likely to be the username of the current user, so your expression could probably be replaced by just ~.






share|improve this answer




























    up vote
    6
    down vote













    As other answers have pointed out the behavior depends on which order the shell does ~ and $ expansions and whether it will even do both for the same word.



    The behavior you were looking for is possible to achieve in bash by a very small change to your command. Simply prefix the command with eval.



    eval "cd ~$USER"


    will change to the home directory of the user given by the username in the variable USER, provided $USER doesn't contain characters special to the shell (if there's a remote chance that it might, you should not pass it as argument to eval as that would be dangerous) or / characters and that there's an entry for that user in the system's user database.






    share|improve this answer






























      up vote
      3
      down vote













      An alternative way to look up a variable user's home directory, if you are using one of the shells where tilde expansion happens before variable expansion, is with getent. This tool exists on at least Linux, Solaris, and FreeBSD; I'm not sure how universal it is.



      $ USER=bloggs
      $ getent passwd "$USER" | cut -d: -f6
      /home/b/bloggs


      As with tilde expansion, this might not give you the same thing that su - $USER -c 'echo $HOME' would print if you had the privileges to do that.






      share|improve this answer

















      • 1




        See also perl -le 'print((getpwnam shift)[7])' -- "$USER" as potentially slightly more portable.
        – Stéphane Chazelas
        May 18 at 10:37

















      up vote
      -1
      down vote













      Since the OP insists on an answer, here it is.



      The behavior of those commands (and many other things) depends on the particular shell you happen to be using. Unless you specifiy which particular shell you use, it is probably not possible to give a simple answer.



      As a matter of fact, if you use tcsh, as I do, both of the expressions in the OP's question (as it is written as I write this - I take no responsibility for future edits!) work perfectly well. I don't know what other shells will do, since I don't use them. So perhaps the OP doesn't know quite as much about what can be done as s/he thinks :-)






      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',
        convertImagesToLinks: false,
        noModals: false,
        showLowRepImageUploadWarning: true,
        reputationToPostImages: null,
        bindNavPrevention: true,
        postfix: "",
        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%2f444383%2fcd-user-is-possible-but-why-cant-we-cd-user-or-cd-user%23new-answer', 'question_page');

        );

        Post as a guest






























        5 Answers
        5






        active

        oldest

        votes








        5 Answers
        5






        active

        oldest

        votes









        active

        oldest

        votes






        active

        oldest

        votes








        up vote
        20
        down vote



        accepted










        That very much depends on the shell and the order the expansions are done in those shells.



        ~$user expands to the home directory of the user whose name is stored in $user in csh (where that ~user feature comes from), AT&T ksh, zsh, fish.



        Note however these variations:



        $ u=daemon/xxx csh -c 'echo ~$u'
        /usr/sbin/xxx # same in zsh/fish
        $ u=daemon/xxx ksh93 -c 'echo ~$u'
        ~daemon/xxx

        $ u=daemon/xxx csh -c 'echo ~"$u"'
        Unknown user: daemon/xxx.
        $ u=daemon/xxx zsh -c 'echo ~"$u"'
        /usr/sbin/x # same in fish

        $ u=" daemon" csh -c 'echo ~$u'
        /home/stephane daemon
        $ u=" daemon" zsh -c 'echo ~$u'
        ~ daemon # same in ksh/fish

        $ u="/daemon" csh -c 'echo ~$u'
        /home/stephane/daemon # same in zsh
        $ u="/daemon" fish -c 'echo ~$u'
        ~/daemon # same in ksh


        It expands to the home directory of the user named literally $user in bash (provided that user exists, which is very unlikely of course).



        And to neither in pdksh, dash, yash, presumably because they don't consider $user to be a valid user name.






        share|improve this answer























        • Can you please suggest me where can I learn more about expansion in various shells.
          – Neo_Returns
          May 17 at 14:30







        • 6




          @Neo_Returns, their respective manuals, and when that's not clearly documented, with trial and error and the source code for those where it's available...
          – Stéphane Chazelas
          May 17 at 14:37














        up vote
        20
        down vote



        accepted










        That very much depends on the shell and the order the expansions are done in those shells.



        ~$user expands to the home directory of the user whose name is stored in $user in csh (where that ~user feature comes from), AT&T ksh, zsh, fish.



        Note however these variations:



        $ u=daemon/xxx csh -c 'echo ~$u'
        /usr/sbin/xxx # same in zsh/fish
        $ u=daemon/xxx ksh93 -c 'echo ~$u'
        ~daemon/xxx

        $ u=daemon/xxx csh -c 'echo ~"$u"'
        Unknown user: daemon/xxx.
        $ u=daemon/xxx zsh -c 'echo ~"$u"'
        /usr/sbin/x # same in fish

        $ u=" daemon" csh -c 'echo ~$u'
        /home/stephane daemon
        $ u=" daemon" zsh -c 'echo ~$u'
        ~ daemon # same in ksh/fish

        $ u="/daemon" csh -c 'echo ~$u'
        /home/stephane/daemon # same in zsh
        $ u="/daemon" fish -c 'echo ~$u'
        ~/daemon # same in ksh


        It expands to the home directory of the user named literally $user in bash (provided that user exists, which is very unlikely of course).



        And to neither in pdksh, dash, yash, presumably because they don't consider $user to be a valid user name.






        share|improve this answer























        • Can you please suggest me where can I learn more about expansion in various shells.
          – Neo_Returns
          May 17 at 14:30







        • 6




          @Neo_Returns, their respective manuals, and when that's not clearly documented, with trial and error and the source code for those where it's available...
          – Stéphane Chazelas
          May 17 at 14:37












        up vote
        20
        down vote



        accepted







        up vote
        20
        down vote



        accepted






        That very much depends on the shell and the order the expansions are done in those shells.



        ~$user expands to the home directory of the user whose name is stored in $user in csh (where that ~user feature comes from), AT&T ksh, zsh, fish.



        Note however these variations:



        $ u=daemon/xxx csh -c 'echo ~$u'
        /usr/sbin/xxx # same in zsh/fish
        $ u=daemon/xxx ksh93 -c 'echo ~$u'
        ~daemon/xxx

        $ u=daemon/xxx csh -c 'echo ~"$u"'
        Unknown user: daemon/xxx.
        $ u=daemon/xxx zsh -c 'echo ~"$u"'
        /usr/sbin/x # same in fish

        $ u=" daemon" csh -c 'echo ~$u'
        /home/stephane daemon
        $ u=" daemon" zsh -c 'echo ~$u'
        ~ daemon # same in ksh/fish

        $ u="/daemon" csh -c 'echo ~$u'
        /home/stephane/daemon # same in zsh
        $ u="/daemon" fish -c 'echo ~$u'
        ~/daemon # same in ksh


        It expands to the home directory of the user named literally $user in bash (provided that user exists, which is very unlikely of course).



        And to neither in pdksh, dash, yash, presumably because they don't consider $user to be a valid user name.






        share|improve this answer















        That very much depends on the shell and the order the expansions are done in those shells.



        ~$user expands to the home directory of the user whose name is stored in $user in csh (where that ~user feature comes from), AT&T ksh, zsh, fish.



        Note however these variations:



        $ u=daemon/xxx csh -c 'echo ~$u'
        /usr/sbin/xxx # same in zsh/fish
        $ u=daemon/xxx ksh93 -c 'echo ~$u'
        ~daemon/xxx

        $ u=daemon/xxx csh -c 'echo ~"$u"'
        Unknown user: daemon/xxx.
        $ u=daemon/xxx zsh -c 'echo ~"$u"'
        /usr/sbin/x # same in fish

        $ u=" daemon" csh -c 'echo ~$u'
        /home/stephane daemon
        $ u=" daemon" zsh -c 'echo ~$u'
        ~ daemon # same in ksh/fish

        $ u="/daemon" csh -c 'echo ~$u'
        /home/stephane/daemon # same in zsh
        $ u="/daemon" fish -c 'echo ~$u'
        ~/daemon # same in ksh


        It expands to the home directory of the user named literally $user in bash (provided that user exists, which is very unlikely of course).



        And to neither in pdksh, dash, yash, presumably because they don't consider $user to be a valid user name.







        share|improve this answer















        share|improve this answer



        share|improve this answer








        edited May 20 at 19:16


























        answered May 17 at 14:24









        Stéphane Chazelas

        279k53513845




        279k53513845











        • Can you please suggest me where can I learn more about expansion in various shells.
          – Neo_Returns
          May 17 at 14:30







        • 6




          @Neo_Returns, their respective manuals, and when that's not clearly documented, with trial and error and the source code for those where it's available...
          – Stéphane Chazelas
          May 17 at 14:37
















        • Can you please suggest me where can I learn more about expansion in various shells.
          – Neo_Returns
          May 17 at 14:30







        • 6




          @Neo_Returns, their respective manuals, and when that's not clearly documented, with trial and error and the source code for those where it's available...
          – Stéphane Chazelas
          May 17 at 14:37















        Can you please suggest me where can I learn more about expansion in various shells.
        – Neo_Returns
        May 17 at 14:30





        Can you please suggest me where can I learn more about expansion in various shells.
        – Neo_Returns
        May 17 at 14:30





        6




        6




        @Neo_Returns, their respective manuals, and when that's not clearly documented, with trial and error and the source code for those where it's available...
        – Stéphane Chazelas
        May 17 at 14:37




        @Neo_Returns, their respective manuals, and when that's not clearly documented, with trial and error and the source code for those where it's available...
        – Stéphane Chazelas
        May 17 at 14:37












        up vote
        10
        down vote













        Tilde expansion is a separate step in the processing of the command line. It happens just before variable expansion.



        If the tilde is followed by something other than a slash, it will expand to the home directory of the user whose name is following the tilde, as in, for example, ~otheruser. Since $USER is not expanded at that point and since it's unlikely to correspond to a valid username, the tilde is left unexpanded.



        $USER is likely to be the username of the current user, so your expression could probably be replaced by just ~.






        share|improve this answer

























          up vote
          10
          down vote













          Tilde expansion is a separate step in the processing of the command line. It happens just before variable expansion.



          If the tilde is followed by something other than a slash, it will expand to the home directory of the user whose name is following the tilde, as in, for example, ~otheruser. Since $USER is not expanded at that point and since it's unlikely to correspond to a valid username, the tilde is left unexpanded.



          $USER is likely to be the username of the current user, so your expression could probably be replaced by just ~.






          share|improve this answer























            up vote
            10
            down vote










            up vote
            10
            down vote









            Tilde expansion is a separate step in the processing of the command line. It happens just before variable expansion.



            If the tilde is followed by something other than a slash, it will expand to the home directory of the user whose name is following the tilde, as in, for example, ~otheruser. Since $USER is not expanded at that point and since it's unlikely to correspond to a valid username, the tilde is left unexpanded.



            $USER is likely to be the username of the current user, so your expression could probably be replaced by just ~.






            share|improve this answer













            Tilde expansion is a separate step in the processing of the command line. It happens just before variable expansion.



            If the tilde is followed by something other than a slash, it will expand to the home directory of the user whose name is following the tilde, as in, for example, ~otheruser. Since $USER is not expanded at that point and since it's unlikely to correspond to a valid username, the tilde is left unexpanded.



            $USER is likely to be the username of the current user, so your expression could probably be replaced by just ~.







            share|improve this answer













            share|improve this answer



            share|improve this answer











            answered May 17 at 14:21









            Kusalananda

            102k13199314




            102k13199314




















                up vote
                6
                down vote













                As other answers have pointed out the behavior depends on which order the shell does ~ and $ expansions and whether it will even do both for the same word.



                The behavior you were looking for is possible to achieve in bash by a very small change to your command. Simply prefix the command with eval.



                eval "cd ~$USER"


                will change to the home directory of the user given by the username in the variable USER, provided $USER doesn't contain characters special to the shell (if there's a remote chance that it might, you should not pass it as argument to eval as that would be dangerous) or / characters and that there's an entry for that user in the system's user database.






                share|improve this answer



























                  up vote
                  6
                  down vote













                  As other answers have pointed out the behavior depends on which order the shell does ~ and $ expansions and whether it will even do both for the same word.



                  The behavior you were looking for is possible to achieve in bash by a very small change to your command. Simply prefix the command with eval.



                  eval "cd ~$USER"


                  will change to the home directory of the user given by the username in the variable USER, provided $USER doesn't contain characters special to the shell (if there's a remote chance that it might, you should not pass it as argument to eval as that would be dangerous) or / characters and that there's an entry for that user in the system's user database.






                  share|improve this answer

























                    up vote
                    6
                    down vote










                    up vote
                    6
                    down vote









                    As other answers have pointed out the behavior depends on which order the shell does ~ and $ expansions and whether it will even do both for the same word.



                    The behavior you were looking for is possible to achieve in bash by a very small change to your command. Simply prefix the command with eval.



                    eval "cd ~$USER"


                    will change to the home directory of the user given by the username in the variable USER, provided $USER doesn't contain characters special to the shell (if there's a remote chance that it might, you should not pass it as argument to eval as that would be dangerous) or / characters and that there's an entry for that user in the system's user database.






                    share|improve this answer















                    As other answers have pointed out the behavior depends on which order the shell does ~ and $ expansions and whether it will even do both for the same word.



                    The behavior you were looking for is possible to achieve in bash by a very small change to your command. Simply prefix the command with eval.



                    eval "cd ~$USER"


                    will change to the home directory of the user given by the username in the variable USER, provided $USER doesn't contain characters special to the shell (if there's a remote chance that it might, you should not pass it as argument to eval as that would be dangerous) or / characters and that there's an entry for that user in the system's user database.







                    share|improve this answer















                    share|improve this answer



                    share|improve this answer








                    edited May 18 at 10:34









                    Stéphane Chazelas

                    279k53513845




                    279k53513845











                    answered May 17 at 22:23









                    kasperd

                    2,1691925




                    2,1691925




















                        up vote
                        3
                        down vote













                        An alternative way to look up a variable user's home directory, if you are using one of the shells where tilde expansion happens before variable expansion, is with getent. This tool exists on at least Linux, Solaris, and FreeBSD; I'm not sure how universal it is.



                        $ USER=bloggs
                        $ getent passwd "$USER" | cut -d: -f6
                        /home/b/bloggs


                        As with tilde expansion, this might not give you the same thing that su - $USER -c 'echo $HOME' would print if you had the privileges to do that.






                        share|improve this answer

















                        • 1




                          See also perl -le 'print((getpwnam shift)[7])' -- "$USER" as potentially slightly more portable.
                          – Stéphane Chazelas
                          May 18 at 10:37














                        up vote
                        3
                        down vote













                        An alternative way to look up a variable user's home directory, if you are using one of the shells where tilde expansion happens before variable expansion, is with getent. This tool exists on at least Linux, Solaris, and FreeBSD; I'm not sure how universal it is.



                        $ USER=bloggs
                        $ getent passwd "$USER" | cut -d: -f6
                        /home/b/bloggs


                        As with tilde expansion, this might not give you the same thing that su - $USER -c 'echo $HOME' would print if you had the privileges to do that.






                        share|improve this answer

















                        • 1




                          See also perl -le 'print((getpwnam shift)[7])' -- "$USER" as potentially slightly more portable.
                          – Stéphane Chazelas
                          May 18 at 10:37












                        up vote
                        3
                        down vote










                        up vote
                        3
                        down vote









                        An alternative way to look up a variable user's home directory, if you are using one of the shells where tilde expansion happens before variable expansion, is with getent. This tool exists on at least Linux, Solaris, and FreeBSD; I'm not sure how universal it is.



                        $ USER=bloggs
                        $ getent passwd "$USER" | cut -d: -f6
                        /home/b/bloggs


                        As with tilde expansion, this might not give you the same thing that su - $USER -c 'echo $HOME' would print if you had the privileges to do that.






                        share|improve this answer













                        An alternative way to look up a variable user's home directory, if you are using one of the shells where tilde expansion happens before variable expansion, is with getent. This tool exists on at least Linux, Solaris, and FreeBSD; I'm not sure how universal it is.



                        $ USER=bloggs
                        $ getent passwd "$USER" | cut -d: -f6
                        /home/b/bloggs


                        As with tilde expansion, this might not give you the same thing that su - $USER -c 'echo $HOME' would print if you had the privileges to do that.







                        share|improve this answer













                        share|improve this answer



                        share|improve this answer











                        answered May 17 at 16:09









                        zwol

                        4,95821424




                        4,95821424







                        • 1




                          See also perl -le 'print((getpwnam shift)[7])' -- "$USER" as potentially slightly more portable.
                          – Stéphane Chazelas
                          May 18 at 10:37












                        • 1




                          See also perl -le 'print((getpwnam shift)[7])' -- "$USER" as potentially slightly more portable.
                          – Stéphane Chazelas
                          May 18 at 10:37







                        1




                        1




                        See also perl -le 'print((getpwnam shift)[7])' -- "$USER" as potentially slightly more portable.
                        – Stéphane Chazelas
                        May 18 at 10:37




                        See also perl -le 'print((getpwnam shift)[7])' -- "$USER" as potentially slightly more portable.
                        – Stéphane Chazelas
                        May 18 at 10:37










                        up vote
                        -1
                        down vote













                        Since the OP insists on an answer, here it is.



                        The behavior of those commands (and many other things) depends on the particular shell you happen to be using. Unless you specifiy which particular shell you use, it is probably not possible to give a simple answer.



                        As a matter of fact, if you use tcsh, as I do, both of the expressions in the OP's question (as it is written as I write this - I take no responsibility for future edits!) work perfectly well. I don't know what other shells will do, since I don't use them. So perhaps the OP doesn't know quite as much about what can be done as s/he thinks :-)






                        share|improve this answer

























                          up vote
                          -1
                          down vote













                          Since the OP insists on an answer, here it is.



                          The behavior of those commands (and many other things) depends on the particular shell you happen to be using. Unless you specifiy which particular shell you use, it is probably not possible to give a simple answer.



                          As a matter of fact, if you use tcsh, as I do, both of the expressions in the OP's question (as it is written as I write this - I take no responsibility for future edits!) work perfectly well. I don't know what other shells will do, since I don't use them. So perhaps the OP doesn't know quite as much about what can be done as s/he thinks :-)






                          share|improve this answer























                            up vote
                            -1
                            down vote










                            up vote
                            -1
                            down vote









                            Since the OP insists on an answer, here it is.



                            The behavior of those commands (and many other things) depends on the particular shell you happen to be using. Unless you specifiy which particular shell you use, it is probably not possible to give a simple answer.



                            As a matter of fact, if you use tcsh, as I do, both of the expressions in the OP's question (as it is written as I write this - I take no responsibility for future edits!) work perfectly well. I don't know what other shells will do, since I don't use them. So perhaps the OP doesn't know quite as much about what can be done as s/he thinks :-)






                            share|improve this answer













                            Since the OP insists on an answer, here it is.



                            The behavior of those commands (and many other things) depends on the particular shell you happen to be using. Unless you specifiy which particular shell you use, it is probably not possible to give a simple answer.



                            As a matter of fact, if you use tcsh, as I do, both of the expressions in the OP's question (as it is written as I write this - I take no responsibility for future edits!) work perfectly well. I don't know what other shells will do, since I don't use them. So perhaps the OP doesn't know quite as much about what can be done as s/he thinks :-)







                            share|improve this answer













                            share|improve this answer



                            share|improve this answer











                            answered May 19 at 1:50









                            jamesqf

                            1275




                            1275






















                                 

                                draft saved


                                draft discarded


























                                 


                                draft saved


                                draft discarded














                                StackExchange.ready(
                                function ()
                                StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f444383%2fcd-user-is-possible-but-why-cant-we-cd-user-or-cd-user%23new-answer', 'question_page');

                                );

                                Post as a guest













































































                                Popular posts from this blog

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

                                Displaying single band from multi-band raster using QGIS

                                How many registers does an x86_64 CPU actually have?