How to produce a PS1 prompt in bash or ksh93 similar to tcsh





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







2















In tcsh, I have the default:



prompt  [%m:%c3] %n%# 


which gives prompts like:



[woehler:hacking/c/hello] ajcarr% 


and



[woehler:~] ajcarr% 


In other words, the current directory and up to the next two above it in the path.



In ksh93 or bash, the substitution of $HOME by ~ is easy, as is extracting the name of just the current directory, but I have yet to find a way of replicating the %c3 behaviour of tcsh. At present in ksh93 I have:



[ajcarr@Woehler] hello $ 


and



[ajcarr@Woehler] ~ $ 


Does anyone have any suggestions about how to do this?










share|improve this question































    2















    In tcsh, I have the default:



    prompt  [%m:%c3] %n%# 


    which gives prompts like:



    [woehler:hacking/c/hello] ajcarr% 


    and



    [woehler:~] ajcarr% 


    In other words, the current directory and up to the next two above it in the path.



    In ksh93 or bash, the substitution of $HOME by ~ is easy, as is extracting the name of just the current directory, but I have yet to find a way of replicating the %c3 behaviour of tcsh. At present in ksh93 I have:



    [ajcarr@Woehler] hello $ 


    and



    [ajcarr@Woehler] ~ $ 


    Does anyone have any suggestions about how to do this?










    share|improve this question



























      2












      2








      2


      0






      In tcsh, I have the default:



      prompt  [%m:%c3] %n%# 


      which gives prompts like:



      [woehler:hacking/c/hello] ajcarr% 


      and



      [woehler:~] ajcarr% 


      In other words, the current directory and up to the next two above it in the path.



      In ksh93 or bash, the substitution of $HOME by ~ is easy, as is extracting the name of just the current directory, but I have yet to find a way of replicating the %c3 behaviour of tcsh. At present in ksh93 I have:



      [ajcarr@Woehler] hello $ 


      and



      [ajcarr@Woehler] ~ $ 


      Does anyone have any suggestions about how to do this?










      share|improve this question
















      In tcsh, I have the default:



      prompt  [%m:%c3] %n%# 


      which gives prompts like:



      [woehler:hacking/c/hello] ajcarr% 


      and



      [woehler:~] ajcarr% 


      In other words, the current directory and up to the next two above it in the path.



      In ksh93 or bash, the substitution of $HOME by ~ is easy, as is extracting the name of just the current directory, but I have yet to find a way of replicating the %c3 behaviour of tcsh. At present in ksh93 I have:



      [ajcarr@Woehler] hello $ 


      and



      [ajcarr@Woehler] ~ $ 


      Does anyone have any suggestions about how to do this?







      bash ksh prompt tcsh






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited 3 hours ago









      steeldriver

      38.1k45489




      38.1k45489










      asked 3 hours ago









      Alun CarrAlun Carr

      7112




      7112






















          2 Answers
          2






          active

          oldest

          votes


















          2














          For bash, you could achieve similar results by setting the PROMPT_DIRTRIM variable:



          $ PS1='[u@h] w$ '
          [schaller@r2d2] ~$ pwd
          /home/schaller
          [schaller@r2d2] ~$ PROMPT_DIRTRIM=3
          [schaller@r2d2] ~$ cd /home/schaller/tmp/513924/another/directory/here
          [schaller@r2d2] ~/.../another/directory/here$





          share|improve this answer































            2














            In ksh93:



            PS1='${PWD#${PWD%?/*/*/*}?/} $ '
            share/doc/libnl-3-dev $ _

            PS1='[${HOSTNAME%%.*}:${PWD#${PWD%?/*/*/*}?/}] $USER% '
            [host:share/doc/libnl-3-dev] user% _


            If you want it to also replace $HOME with ~, something nastier is needed:



            PS1='$(d=${PWD/#$HOME/"~"};printf %s "${d#${d%?/*/*/*}?/}") $ '
            ~/w/maemo $ cd sb2-pathmaps
            w/maemo/sb2-pathmaps $ _

            PS1='$(d=${PWD/#$HOME/"~"};printf %s "[${HOSTNAME%%.*}:${d#${d%?/*/*/*}?/}]") $USER% '
            [host:w/maemo/sb2-pathmaps] user% _




            All this should also work in bash, though bash has its own prompt escapes (eg. h for ${HOSTNAME%%.*}) and path shortening mechanism (with PROMPT_DIRTRIM).



            Also, the nastier variant will be really nasty, because bash, unlike ksh93, will fork() a separate process for each $(...; printf ...) command substitution, even if it contains only builtins. This also holds true for pdksh derived shells, like mksh.





            zsh has prompt escapes quite similar but not identical to tcsh:



            zsh$ PS1='[%m:%3c] %n%# '
            [host:share/doc/libnl-3-dev] user% _





            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%2f513924%2fhow-to-produce-a-ps1-prompt-in-bash-or-ksh93-similar-to-tcsh%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









              2














              For bash, you could achieve similar results by setting the PROMPT_DIRTRIM variable:



              $ PS1='[u@h] w$ '
              [schaller@r2d2] ~$ pwd
              /home/schaller
              [schaller@r2d2] ~$ PROMPT_DIRTRIM=3
              [schaller@r2d2] ~$ cd /home/schaller/tmp/513924/another/directory/here
              [schaller@r2d2] ~/.../another/directory/here$





              share|improve this answer




























                2














                For bash, you could achieve similar results by setting the PROMPT_DIRTRIM variable:



                $ PS1='[u@h] w$ '
                [schaller@r2d2] ~$ pwd
                /home/schaller
                [schaller@r2d2] ~$ PROMPT_DIRTRIM=3
                [schaller@r2d2] ~$ cd /home/schaller/tmp/513924/another/directory/here
                [schaller@r2d2] ~/.../another/directory/here$





                share|improve this answer


























                  2












                  2








                  2







                  For bash, you could achieve similar results by setting the PROMPT_DIRTRIM variable:



                  $ PS1='[u@h] w$ '
                  [schaller@r2d2] ~$ pwd
                  /home/schaller
                  [schaller@r2d2] ~$ PROMPT_DIRTRIM=3
                  [schaller@r2d2] ~$ cd /home/schaller/tmp/513924/another/directory/here
                  [schaller@r2d2] ~/.../another/directory/here$





                  share|improve this answer













                  For bash, you could achieve similar results by setting the PROMPT_DIRTRIM variable:



                  $ PS1='[u@h] w$ '
                  [schaller@r2d2] ~$ pwd
                  /home/schaller
                  [schaller@r2d2] ~$ PROMPT_DIRTRIM=3
                  [schaller@r2d2] ~$ cd /home/schaller/tmp/513924/another/directory/here
                  [schaller@r2d2] ~/.../another/directory/here$






                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered 2 hours ago









                  Jeff SchallerJeff Schaller

                  45.2k1164147




                  45.2k1164147

























                      2














                      In ksh93:



                      PS1='${PWD#${PWD%?/*/*/*}?/} $ '
                      share/doc/libnl-3-dev $ _

                      PS1='[${HOSTNAME%%.*}:${PWD#${PWD%?/*/*/*}?/}] $USER% '
                      [host:share/doc/libnl-3-dev] user% _


                      If you want it to also replace $HOME with ~, something nastier is needed:



                      PS1='$(d=${PWD/#$HOME/"~"};printf %s "${d#${d%?/*/*/*}?/}") $ '
                      ~/w/maemo $ cd sb2-pathmaps
                      w/maemo/sb2-pathmaps $ _

                      PS1='$(d=${PWD/#$HOME/"~"};printf %s "[${HOSTNAME%%.*}:${d#${d%?/*/*/*}?/}]") $USER% '
                      [host:w/maemo/sb2-pathmaps] user% _




                      All this should also work in bash, though bash has its own prompt escapes (eg. h for ${HOSTNAME%%.*}) and path shortening mechanism (with PROMPT_DIRTRIM).



                      Also, the nastier variant will be really nasty, because bash, unlike ksh93, will fork() a separate process for each $(...; printf ...) command substitution, even if it contains only builtins. This also holds true for pdksh derived shells, like mksh.





                      zsh has prompt escapes quite similar but not identical to tcsh:



                      zsh$ PS1='[%m:%3c] %n%# '
                      [host:share/doc/libnl-3-dev] user% _





                      share|improve this answer






























                        2














                        In ksh93:



                        PS1='${PWD#${PWD%?/*/*/*}?/} $ '
                        share/doc/libnl-3-dev $ _

                        PS1='[${HOSTNAME%%.*}:${PWD#${PWD%?/*/*/*}?/}] $USER% '
                        [host:share/doc/libnl-3-dev] user% _


                        If you want it to also replace $HOME with ~, something nastier is needed:



                        PS1='$(d=${PWD/#$HOME/"~"};printf %s "${d#${d%?/*/*/*}?/}") $ '
                        ~/w/maemo $ cd sb2-pathmaps
                        w/maemo/sb2-pathmaps $ _

                        PS1='$(d=${PWD/#$HOME/"~"};printf %s "[${HOSTNAME%%.*}:${d#${d%?/*/*/*}?/}]") $USER% '
                        [host:w/maemo/sb2-pathmaps] user% _




                        All this should also work in bash, though bash has its own prompt escapes (eg. h for ${HOSTNAME%%.*}) and path shortening mechanism (with PROMPT_DIRTRIM).



                        Also, the nastier variant will be really nasty, because bash, unlike ksh93, will fork() a separate process for each $(...; printf ...) command substitution, even if it contains only builtins. This also holds true for pdksh derived shells, like mksh.





                        zsh has prompt escapes quite similar but not identical to tcsh:



                        zsh$ PS1='[%m:%3c] %n%# '
                        [host:share/doc/libnl-3-dev] user% _





                        share|improve this answer




























                          2












                          2








                          2







                          In ksh93:



                          PS1='${PWD#${PWD%?/*/*/*}?/} $ '
                          share/doc/libnl-3-dev $ _

                          PS1='[${HOSTNAME%%.*}:${PWD#${PWD%?/*/*/*}?/}] $USER% '
                          [host:share/doc/libnl-3-dev] user% _


                          If you want it to also replace $HOME with ~, something nastier is needed:



                          PS1='$(d=${PWD/#$HOME/"~"};printf %s "${d#${d%?/*/*/*}?/}") $ '
                          ~/w/maemo $ cd sb2-pathmaps
                          w/maemo/sb2-pathmaps $ _

                          PS1='$(d=${PWD/#$HOME/"~"};printf %s "[${HOSTNAME%%.*}:${d#${d%?/*/*/*}?/}]") $USER% '
                          [host:w/maemo/sb2-pathmaps] user% _




                          All this should also work in bash, though bash has its own prompt escapes (eg. h for ${HOSTNAME%%.*}) and path shortening mechanism (with PROMPT_DIRTRIM).



                          Also, the nastier variant will be really nasty, because bash, unlike ksh93, will fork() a separate process for each $(...; printf ...) command substitution, even if it contains only builtins. This also holds true for pdksh derived shells, like mksh.





                          zsh has prompt escapes quite similar but not identical to tcsh:



                          zsh$ PS1='[%m:%3c] %n%# '
                          [host:share/doc/libnl-3-dev] user% _





                          share|improve this answer















                          In ksh93:



                          PS1='${PWD#${PWD%?/*/*/*}?/} $ '
                          share/doc/libnl-3-dev $ _

                          PS1='[${HOSTNAME%%.*}:${PWD#${PWD%?/*/*/*}?/}] $USER% '
                          [host:share/doc/libnl-3-dev] user% _


                          If you want it to also replace $HOME with ~, something nastier is needed:



                          PS1='$(d=${PWD/#$HOME/"~"};printf %s "${d#${d%?/*/*/*}?/}") $ '
                          ~/w/maemo $ cd sb2-pathmaps
                          w/maemo/sb2-pathmaps $ _

                          PS1='$(d=${PWD/#$HOME/"~"};printf %s "[${HOSTNAME%%.*}:${d#${d%?/*/*/*}?/}]") $USER% '
                          [host:w/maemo/sb2-pathmaps] user% _




                          All this should also work in bash, though bash has its own prompt escapes (eg. h for ${HOSTNAME%%.*}) and path shortening mechanism (with PROMPT_DIRTRIM).



                          Also, the nastier variant will be really nasty, because bash, unlike ksh93, will fork() a separate process for each $(...; printf ...) command substitution, even if it contains only builtins. This also holds true for pdksh derived shells, like mksh.





                          zsh has prompt escapes quite similar but not identical to tcsh:



                          zsh$ PS1='[%m:%3c] %n%# '
                          [host:share/doc/libnl-3-dev] user% _






                          share|improve this answer














                          share|improve this answer



                          share|improve this answer








                          edited 21 mins ago

























                          answered 2 hours ago









                          mosvymosvy

                          10.6k11338




                          10.6k11338






























                              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%2f513924%2fhow-to-produce-a-ps1-prompt-in-bash-or-ksh93-similar-to-tcsh%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

                              GameSpot

                              日野市

                              Tu-95轟炸機