How to produce a PS1 prompt in bash or ksh93 similar to tcsh Announcing the arrival of Valued...

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

Assertions In A Mock Callout Test

Pointing to problems without suggesting solutions

Does traveling In The United States require a passport or can I use my green card if not a US citizen?

Can I take recommendation from someone I met at a conference?

2 sample t test for sample sizes - 30,000 and 150,000

How to ask rejected full-time candidates to apply to teach individual courses?

How to charge percentage of transaction cost?

Is there a verb for listening stealthily?

Protagonist's race is hidden - should I reveal it?

What were wait-states, and why was it only an issue for PCs?

Why does my GNOME settings mention "Moto C Plus"?

Why is one lightbulb in a string illuminated?

Can this water damage be explained by lack of gutters and grading issues?

Married in secret, can marital status in passport be changed at a later date?

How to mute a string and play another at the same time

Unix AIX passing variable and arguments to expect and spawn

What is the ongoing value of the Kanban board to the developers as opposed to management

Putting Ant-Man on house arrest

Why aren't road bike wheels tiny?

Will I be more secure with my own router behind my ISP's router?

How to leave only the following strings?

Kepler's 3rd law: ratios don't fit data

How to make an animal which can only breed for a certain number of generations?



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



Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 23, 2019 at 23:30 UTC (7:30pm US/Eastern)
2019 Community Moderator Election Results
Why I closed the “Why is Kali so hard” questionbash equivalent of this use of tcsh “sched” command?Bash overwrites the first line, PS1 bash promptHow can avoid these spurious characters in my bash prompt?Show only current and parent directory in bash promptExecute command within current shell before every promptAlias for “cd” which shows current directory each time I change directories?Parameters in bash $PS1 variableHow do I display only the current directory while using powerline in the terminal prompt.?what shell is used to run a scriptprompt (PS1) doesn't update on bound command





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







1















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































    1















    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



























      1












      1








      1


      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 2 hours ago









      steeldriver

      38.1k45489




      38.1k45489










      asked 2 hours ago









      Alun CarrAlun Carr

      6612




      6612






















          2 Answers
          2






          active

          oldest

          votes


















          1














          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































            1














            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[1] is needed:



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


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



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



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


            [1] there may be some consolation in the fact that ksh93 doesn't fork() another process for subshells which contain only builtins, like that $( ...; printf ...) ;-)






            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









              1














              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




























                1














                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


























                  1












                  1








                  1







                  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 1 hour ago









                  Jeff SchallerJeff Schaller

                  45.2k1164147




                  45.2k1164147

























                      1














                      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[1] is needed:



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


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



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



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


                      [1] there may be some consolation in the fact that ksh93 doesn't fork() another process for subshells which contain only builtins, like that $( ...; printf ...) ;-)






                      share|improve this answer






























                        1














                        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[1] is needed:



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


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



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



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


                        [1] there may be some consolation in the fact that ksh93 doesn't fork() another process for subshells which contain only builtins, like that $( ...; printf ...) ;-)






                        share|improve this answer




























                          1












                          1








                          1







                          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[1] is needed:



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


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



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



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


                          [1] there may be some consolation in the fact that ksh93 doesn't fork() another process for subshells which contain only builtins, like that $( ...; printf ...) ;-)






                          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[1] is needed:



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


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



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



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


                          [1] there may be some consolation in the fact that ksh93 doesn't fork() another process for subshells which contain only builtins, like that $( ...; printf ...) ;-)







                          share|improve this answer














                          share|improve this answer



                          share|improve this answer








                          edited 14 mins ago

























                          answered 1 hour 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

                              As a Security Precaution, the user account has been locked The Next CEO of Stack OverflowMS...

                              Список ссавців Італії Природоохоронні статуси | Список |...

                              Українські прізвища Зміст Історичні відомості |...