Bash while loop read from colon-delimited list of paths using IFSWhy not use “which”? What to use then?Why is using a shell loop to process text considered bad practice?Understanding “IFS= read -r line”Bash: why isn't “set” behaving like I expect it to?Reading lines from a file with bash: for vs. whileHow given script makes executables in /usr/local/bin/$PATH duplication issuesRead longest line in file using while read loop?How to prevent the caller's shell from being used in sudobash while/read loop behaves differently in a mips/musl/busybox based VMBash script works via terminal but not via main menuHow to loop over ever-increasing list of files in bash?what shell is used to run a script

Why is this clock signal connected to a capacitor to gnd?

Short story with a alien planet, government officials must wear exploding medallions

If human space travel is limited by the G force vulnerability, is there a way to counter G forces?

Should I cover my bicycle overnight while bikepacking?

What method can I use to design a dungeon difficult enough that the PCs can't make it through without killing them?

Method Does Not Exist error message

Why was the shrinking from 8″ made only to 5.25″ and not smaller (4″ or less)?

What type of content (depth/breadth) is expected for a short presentation for Asst Professor interview in the UK?

iPad being using in wall mount battery swollen

Can compressed videos be decoded back to their uncompresed original format?

Apex Framework / library for consuming REST services

Why can't we play rap on piano?

How could indestructible materials be used in power generation?

How does a predictive coding aid in lossless compression?

Is it inappropriate for a student to attend their mentor's dissertation defense?

How to tell a function to use the default argument values?

How dangerous is XSS?

Bullying boss launched a smear campaign and made me unemployable

How to prevent "they're falling in love" trope

How can saying a song's name be a copyright violation?

Why do bosons tend to occupy the same state?

Why is consensus so controversial in Britain?

What exploit Are these user agents trying to use?

In 'Revenger,' what does 'cove' come from?



Bash while loop read from colon-delimited list of paths using IFS


Why not use “which”? What to use then?Why is using a shell loop to process text considered bad practice?Understanding “IFS= read -r line”Bash: why isn't “set” behaving like I expect it to?Reading lines from a file with bash: for vs. whileHow given script makes executables in /usr/local/bin/$PATH duplication issuesRead longest line in file using while read loop?How to prevent the caller's shell from being used in sudobash while/read loop behaves differently in a mips/musl/busybox based VMBash script works via terminal but not via main menuHow to loop over ever-increasing list of files in bash?what shell is used to run a script













4















I am trying to write a bash function that behaves similarly to the where builtin in tcsh. In tcsh, where lists all the builtins, aliases, and the absolute paths to executables on the PATH with a given name, even if they are shadowed, e.g.



tcsh> where tcsh
/usr/bin/tcsh
/bin/tcsh


As part of this I want to loop over everything in the $PATH and see if an executable file with the appropriate name exists.



The following bash snippet is intended to loop over a colon-delimited list of paths and print each component followed by a newline, however, it just seems to print the entire contents of $PATH all on one line



#!/bin/bash
while IFS=':' read -r line; do
printf "%sn" "$line"
done <<< "$PATH"


As is stands now, bash where and ./where just print /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games



So, how do I set up my while loop so that the value of the loop variable is each segment of the colon-separated list of paths in turn?










share|improve this question



















  • 6





    Why not use type -a?

    – Stéphane Chazelas
    Apr 15 '16 at 3:41











  • @StéphaneChazelas because I didn't know it existed. :/

    – Gregory Nisbet
    Apr 15 '16 at 3:43






  • 2





    See also Debian's which script for how to loop over $PATH properly.

    – Stéphane Chazelas
    Apr 15 '16 at 3:44











  • @StéphaneChazelas I see so if you use IFS=':' ; for x in $PATH ; do echo "$x" ; done, then the loop variable will be set to each element of $PATH in turn. Why do the for and while loop treat IFS differently?

    – Gregory Nisbet
    Apr 15 '16 at 4:44







  • 2





    @GregoryNisbet it's not while that's doing anything with IFS in this case, it's read, which reads a whole line at once, regardless of IFS—as Stephane explained, actually.

    – Wildcard
    Apr 15 '16 at 4:49















4















I am trying to write a bash function that behaves similarly to the where builtin in tcsh. In tcsh, where lists all the builtins, aliases, and the absolute paths to executables on the PATH with a given name, even if they are shadowed, e.g.



tcsh> where tcsh
/usr/bin/tcsh
/bin/tcsh


As part of this I want to loop over everything in the $PATH and see if an executable file with the appropriate name exists.



The following bash snippet is intended to loop over a colon-delimited list of paths and print each component followed by a newline, however, it just seems to print the entire contents of $PATH all on one line



#!/bin/bash
while IFS=':' read -r line; do
printf "%sn" "$line"
done <<< "$PATH"


As is stands now, bash where and ./where just print /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games



So, how do I set up my while loop so that the value of the loop variable is each segment of the colon-separated list of paths in turn?










share|improve this question



















  • 6





    Why not use type -a?

    – Stéphane Chazelas
    Apr 15 '16 at 3:41











  • @StéphaneChazelas because I didn't know it existed. :/

    – Gregory Nisbet
    Apr 15 '16 at 3:43






  • 2





    See also Debian's which script for how to loop over $PATH properly.

    – Stéphane Chazelas
    Apr 15 '16 at 3:44











  • @StéphaneChazelas I see so if you use IFS=':' ; for x in $PATH ; do echo "$x" ; done, then the loop variable will be set to each element of $PATH in turn. Why do the for and while loop treat IFS differently?

    – Gregory Nisbet
    Apr 15 '16 at 4:44







  • 2





    @GregoryNisbet it's not while that's doing anything with IFS in this case, it's read, which reads a whole line at once, regardless of IFS—as Stephane explained, actually.

    – Wildcard
    Apr 15 '16 at 4:49













4












4








4








I am trying to write a bash function that behaves similarly to the where builtin in tcsh. In tcsh, where lists all the builtins, aliases, and the absolute paths to executables on the PATH with a given name, even if they are shadowed, e.g.



tcsh> where tcsh
/usr/bin/tcsh
/bin/tcsh


As part of this I want to loop over everything in the $PATH and see if an executable file with the appropriate name exists.



The following bash snippet is intended to loop over a colon-delimited list of paths and print each component followed by a newline, however, it just seems to print the entire contents of $PATH all on one line



#!/bin/bash
while IFS=':' read -r line; do
printf "%sn" "$line"
done <<< "$PATH"


As is stands now, bash where and ./where just print /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games



So, how do I set up my while loop so that the value of the loop variable is each segment of the colon-separated list of paths in turn?










share|improve this question
















I am trying to write a bash function that behaves similarly to the where builtin in tcsh. In tcsh, where lists all the builtins, aliases, and the absolute paths to executables on the PATH with a given name, even if they are shadowed, e.g.



tcsh> where tcsh
/usr/bin/tcsh
/bin/tcsh


As part of this I want to loop over everything in the $PATH and see if an executable file with the appropriate name exists.



The following bash snippet is intended to loop over a colon-delimited list of paths and print each component followed by a newline, however, it just seems to print the entire contents of $PATH all on one line



#!/bin/bash
while IFS=':' read -r line; do
printf "%sn" "$line"
done <<< "$PATH"


As is stands now, bash where and ./where just print /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games



So, how do I set up my while loop so that the value of the loop variable is each segment of the colon-separated list of paths in turn?







bash shell string






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jun 28 '17 at 14:19







Gregory Nisbet

















asked Apr 15 '16 at 3:25









Gregory NisbetGregory Nisbet

1,4981020




1,4981020







  • 6





    Why not use type -a?

    – Stéphane Chazelas
    Apr 15 '16 at 3:41











  • @StéphaneChazelas because I didn't know it existed. :/

    – Gregory Nisbet
    Apr 15 '16 at 3:43






  • 2





    See also Debian's which script for how to loop over $PATH properly.

    – Stéphane Chazelas
    Apr 15 '16 at 3:44











  • @StéphaneChazelas I see so if you use IFS=':' ; for x in $PATH ; do echo "$x" ; done, then the loop variable will be set to each element of $PATH in turn. Why do the for and while loop treat IFS differently?

    – Gregory Nisbet
    Apr 15 '16 at 4:44







  • 2





    @GregoryNisbet it's not while that's doing anything with IFS in this case, it's read, which reads a whole line at once, regardless of IFS—as Stephane explained, actually.

    – Wildcard
    Apr 15 '16 at 4:49












  • 6





    Why not use type -a?

    – Stéphane Chazelas
    Apr 15 '16 at 3:41











  • @StéphaneChazelas because I didn't know it existed. :/

    – Gregory Nisbet
    Apr 15 '16 at 3:43






  • 2





    See also Debian's which script for how to loop over $PATH properly.

    – Stéphane Chazelas
    Apr 15 '16 at 3:44











  • @StéphaneChazelas I see so if you use IFS=':' ; for x in $PATH ; do echo "$x" ; done, then the loop variable will be set to each element of $PATH in turn. Why do the for and while loop treat IFS differently?

    – Gregory Nisbet
    Apr 15 '16 at 4:44







  • 2





    @GregoryNisbet it's not while that's doing anything with IFS in this case, it's read, which reads a whole line at once, regardless of IFS—as Stephane explained, actually.

    – Wildcard
    Apr 15 '16 at 4:49







6




6





Why not use type -a?

– Stéphane Chazelas
Apr 15 '16 at 3:41





Why not use type -a?

– Stéphane Chazelas
Apr 15 '16 at 3:41













@StéphaneChazelas because I didn't know it existed. :/

– Gregory Nisbet
Apr 15 '16 at 3:43





@StéphaneChazelas because I didn't know it existed. :/

– Gregory Nisbet
Apr 15 '16 at 3:43




2




2





See also Debian's which script for how to loop over $PATH properly.

– Stéphane Chazelas
Apr 15 '16 at 3:44





See also Debian's which script for how to loop over $PATH properly.

– Stéphane Chazelas
Apr 15 '16 at 3:44













@StéphaneChazelas I see so if you use IFS=':' ; for x in $PATH ; do echo "$x" ; done, then the loop variable will be set to each element of $PATH in turn. Why do the for and while loop treat IFS differently?

– Gregory Nisbet
Apr 15 '16 at 4:44






@StéphaneChazelas I see so if you use IFS=':' ; for x in $PATH ; do echo "$x" ; done, then the loop variable will be set to each element of $PATH in turn. Why do the for and while loop treat IFS differently?

– Gregory Nisbet
Apr 15 '16 at 4:44





2




2





@GregoryNisbet it's not while that's doing anything with IFS in this case, it's read, which reads a whole line at once, regardless of IFS—as Stephane explained, actually.

– Wildcard
Apr 15 '16 at 4:49





@GregoryNisbet it's not while that's doing anything with IFS in this case, it's read, which reads a whole line at once, regardless of IFS—as Stephane explained, actually.

– Wildcard
Apr 15 '16 at 4:49










5 Answers
5






active

oldest

votes


















6














read uses IFS to separate the words in the line it reads, it doesn't tell read to read until the first occurrence of any of the characters in it.



IFS=: read -r a b


Would read one line, put the part before the first : in $a, and the rest in $b.



IFS=: read -r a


would put the whole line (the rest) in $a (except if that line contains only one : and it's the last character on the line).



If you wanted to read until the first :, you'd use read -d: instead (ksh93, zsh or bash only).



printf %s "$PATH" | while IFS= read -rd: dir || [ -n "$dir" ]; do
...
done


(we're not using <<< as that adds an extra newline character).



Or you could use standard word splitting:



IFS=:; set -o noglob
for dir in $PATH""; do
...
done


Now beware of few caveats:



  • An empty $PATH component means the current directory.

  • An empty $PATH means the current directory (that is, $PATH contains one component which is the current directory, so the while read -d: loop would be wrong in that case).


  • //file is not necessary the same as /file on some system, so if $PATH contains /, you need to be careful with things like $dir/$file.

  • An unset $PATH means a default search path is to be used, it's not the same as a set but empty $PATH.

Now, if it's only the equivalent of tcsh/zsh's where command, you could use bash's type -a.



More reading:



  • What's a safe and portable way to split a string in shell programming?

  • Understanding "IFS= read -r line"

  • Why not use "which"? What to use then?





share|improve this answer
































    3














    Don't use shell loops to process text.



    Instead, use awk, or tr, or even sed.



    printf %s\n "$PATH" | tr ':' 'n'

    printf %s "$PATH" | awk 'BEGIN RS=":"; 1'


    Or, since this is a shell variable you are processing, just use bash pattern substitution:



    echo "$PATH//:/
    "


    (See LESS=+/parameter/pattern man bash.)






    share|improve this answer




















    • 2





      Why the downvote? I see three other answers have been given downvotes just now with no comments...why?

      – Wildcard
      Apr 15 '16 at 19:34


















    0














    This script works similar to the command where



    #!/bin/bash
    fn="foo"
    for i in `echo $PATH|tr ':' 'n'`
    do
    if [[ -e "$i/$fn" ]] ; then
    echo $i
    fi
    done


    $fn is something you want to find.



    $i/$fn may be $i$fn sometimes.






    share|improve this answer
































      0














      Pure bash, it's the same thing as Wildcard's 2nd method, but this is on one line:



      echo -e "$PATH//:/"n""





      share|improve this answer
































        -1














        Shell utils:



        echo $PATH | tr ':' 'n'





        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%2f276614%2fbash-while-loop-read-from-colon-delimited-list-of-paths-using-ifs%23new-answer', 'question_page');

          );

          Post as a guest















          Required, but never shown

























          5 Answers
          5






          active

          oldest

          votes








          5 Answers
          5






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          6














          read uses IFS to separate the words in the line it reads, it doesn't tell read to read until the first occurrence of any of the characters in it.



          IFS=: read -r a b


          Would read one line, put the part before the first : in $a, and the rest in $b.



          IFS=: read -r a


          would put the whole line (the rest) in $a (except if that line contains only one : and it's the last character on the line).



          If you wanted to read until the first :, you'd use read -d: instead (ksh93, zsh or bash only).



          printf %s "$PATH" | while IFS= read -rd: dir || [ -n "$dir" ]; do
          ...
          done


          (we're not using <<< as that adds an extra newline character).



          Or you could use standard word splitting:



          IFS=:; set -o noglob
          for dir in $PATH""; do
          ...
          done


          Now beware of few caveats:



          • An empty $PATH component means the current directory.

          • An empty $PATH means the current directory (that is, $PATH contains one component which is the current directory, so the while read -d: loop would be wrong in that case).


          • //file is not necessary the same as /file on some system, so if $PATH contains /, you need to be careful with things like $dir/$file.

          • An unset $PATH means a default search path is to be used, it's not the same as a set but empty $PATH.

          Now, if it's only the equivalent of tcsh/zsh's where command, you could use bash's type -a.



          More reading:



          • What's a safe and portable way to split a string in shell programming?

          • Understanding "IFS= read -r line"

          • Why not use "which"? What to use then?





          share|improve this answer





























            6














            read uses IFS to separate the words in the line it reads, it doesn't tell read to read until the first occurrence of any of the characters in it.



            IFS=: read -r a b


            Would read one line, put the part before the first : in $a, and the rest in $b.



            IFS=: read -r a


            would put the whole line (the rest) in $a (except if that line contains only one : and it's the last character on the line).



            If you wanted to read until the first :, you'd use read -d: instead (ksh93, zsh or bash only).



            printf %s "$PATH" | while IFS= read -rd: dir || [ -n "$dir" ]; do
            ...
            done


            (we're not using <<< as that adds an extra newline character).



            Or you could use standard word splitting:



            IFS=:; set -o noglob
            for dir in $PATH""; do
            ...
            done


            Now beware of few caveats:



            • An empty $PATH component means the current directory.

            • An empty $PATH means the current directory (that is, $PATH contains one component which is the current directory, so the while read -d: loop would be wrong in that case).


            • //file is not necessary the same as /file on some system, so if $PATH contains /, you need to be careful with things like $dir/$file.

            • An unset $PATH means a default search path is to be used, it's not the same as a set but empty $PATH.

            Now, if it's only the equivalent of tcsh/zsh's where command, you could use bash's type -a.



            More reading:



            • What's a safe and portable way to split a string in shell programming?

            • Understanding "IFS= read -r line"

            • Why not use "which"? What to use then?





            share|improve this answer



























              6












              6








              6







              read uses IFS to separate the words in the line it reads, it doesn't tell read to read until the first occurrence of any of the characters in it.



              IFS=: read -r a b


              Would read one line, put the part before the first : in $a, and the rest in $b.



              IFS=: read -r a


              would put the whole line (the rest) in $a (except if that line contains only one : and it's the last character on the line).



              If you wanted to read until the first :, you'd use read -d: instead (ksh93, zsh or bash only).



              printf %s "$PATH" | while IFS= read -rd: dir || [ -n "$dir" ]; do
              ...
              done


              (we're not using <<< as that adds an extra newline character).



              Or you could use standard word splitting:



              IFS=:; set -o noglob
              for dir in $PATH""; do
              ...
              done


              Now beware of few caveats:



              • An empty $PATH component means the current directory.

              • An empty $PATH means the current directory (that is, $PATH contains one component which is the current directory, so the while read -d: loop would be wrong in that case).


              • //file is not necessary the same as /file on some system, so if $PATH contains /, you need to be careful with things like $dir/$file.

              • An unset $PATH means a default search path is to be used, it's not the same as a set but empty $PATH.

              Now, if it's only the equivalent of tcsh/zsh's where command, you could use bash's type -a.



              More reading:



              • What's a safe and portable way to split a string in shell programming?

              • Understanding "IFS= read -r line"

              • Why not use "which"? What to use then?





              share|improve this answer















              read uses IFS to separate the words in the line it reads, it doesn't tell read to read until the first occurrence of any of the characters in it.



              IFS=: read -r a b


              Would read one line, put the part before the first : in $a, and the rest in $b.



              IFS=: read -r a


              would put the whole line (the rest) in $a (except if that line contains only one : and it's the last character on the line).



              If you wanted to read until the first :, you'd use read -d: instead (ksh93, zsh or bash only).



              printf %s "$PATH" | while IFS= read -rd: dir || [ -n "$dir" ]; do
              ...
              done


              (we're not using <<< as that adds an extra newline character).



              Or you could use standard word splitting:



              IFS=:; set -o noglob
              for dir in $PATH""; do
              ...
              done


              Now beware of few caveats:



              • An empty $PATH component means the current directory.

              • An empty $PATH means the current directory (that is, $PATH contains one component which is the current directory, so the while read -d: loop would be wrong in that case).


              • //file is not necessary the same as /file on some system, so if $PATH contains /, you need to be careful with things like $dir/$file.

              • An unset $PATH means a default search path is to be used, it's not the same as a set but empty $PATH.

              Now, if it's only the equivalent of tcsh/zsh's where command, you could use bash's type -a.



              More reading:



              • What's a safe and portable way to split a string in shell programming?

              • Understanding "IFS= read -r line"

              • Why not use "which"? What to use then?






              share|improve this answer














              share|improve this answer



              share|improve this answer








              edited Sep 11 '18 at 16:26

























              answered Apr 15 '16 at 4:00









              Stéphane ChazelasStéphane Chazelas

              312k57592948




              312k57592948























                  3














                  Don't use shell loops to process text.



                  Instead, use awk, or tr, or even sed.



                  printf %s\n "$PATH" | tr ':' 'n'

                  printf %s "$PATH" | awk 'BEGIN RS=":"; 1'


                  Or, since this is a shell variable you are processing, just use bash pattern substitution:



                  echo "$PATH//:/
                  "


                  (See LESS=+/parameter/pattern man bash.)






                  share|improve this answer




















                  • 2





                    Why the downvote? I see three other answers have been given downvotes just now with no comments...why?

                    – Wildcard
                    Apr 15 '16 at 19:34















                  3














                  Don't use shell loops to process text.



                  Instead, use awk, or tr, or even sed.



                  printf %s\n "$PATH" | tr ':' 'n'

                  printf %s "$PATH" | awk 'BEGIN RS=":"; 1'


                  Or, since this is a shell variable you are processing, just use bash pattern substitution:



                  echo "$PATH//:/
                  "


                  (See LESS=+/parameter/pattern man bash.)






                  share|improve this answer




















                  • 2





                    Why the downvote? I see three other answers have been given downvotes just now with no comments...why?

                    – Wildcard
                    Apr 15 '16 at 19:34













                  3












                  3








                  3







                  Don't use shell loops to process text.



                  Instead, use awk, or tr, or even sed.



                  printf %s\n "$PATH" | tr ':' 'n'

                  printf %s "$PATH" | awk 'BEGIN RS=":"; 1'


                  Or, since this is a shell variable you are processing, just use bash pattern substitution:



                  echo "$PATH//:/
                  "


                  (See LESS=+/parameter/pattern man bash.)






                  share|improve this answer















                  Don't use shell loops to process text.



                  Instead, use awk, or tr, or even sed.



                  printf %s\n "$PATH" | tr ':' 'n'

                  printf %s "$PATH" | awk 'BEGIN RS=":"; 1'


                  Or, since this is a shell variable you are processing, just use bash pattern substitution:



                  echo "$PATH//:/
                  "


                  (See LESS=+/parameter/pattern man bash.)







                  share|improve this answer














                  share|improve this answer



                  share|improve this answer








                  edited Apr 13 '17 at 12:37









                  Community

                  1




                  1










                  answered Apr 15 '16 at 3:39









                  WildcardWildcard

                  23.3k1067171




                  23.3k1067171







                  • 2





                    Why the downvote? I see three other answers have been given downvotes just now with no comments...why?

                    – Wildcard
                    Apr 15 '16 at 19:34












                  • 2





                    Why the downvote? I see three other answers have been given downvotes just now with no comments...why?

                    – Wildcard
                    Apr 15 '16 at 19:34







                  2




                  2





                  Why the downvote? I see three other answers have been given downvotes just now with no comments...why?

                  – Wildcard
                  Apr 15 '16 at 19:34





                  Why the downvote? I see three other answers have been given downvotes just now with no comments...why?

                  – Wildcard
                  Apr 15 '16 at 19:34











                  0














                  This script works similar to the command where



                  #!/bin/bash
                  fn="foo"
                  for i in `echo $PATH|tr ':' 'n'`
                  do
                  if [[ -e "$i/$fn" ]] ; then
                  echo $i
                  fi
                  done


                  $fn is something you want to find.



                  $i/$fn may be $i$fn sometimes.






                  share|improve this answer





























                    0














                    This script works similar to the command where



                    #!/bin/bash
                    fn="foo"
                    for i in `echo $PATH|tr ':' 'n'`
                    do
                    if [[ -e "$i/$fn" ]] ; then
                    echo $i
                    fi
                    done


                    $fn is something you want to find.



                    $i/$fn may be $i$fn sometimes.






                    share|improve this answer



























                      0












                      0








                      0







                      This script works similar to the command where



                      #!/bin/bash
                      fn="foo"
                      for i in `echo $PATH|tr ':' 'n'`
                      do
                      if [[ -e "$i/$fn" ]] ; then
                      echo $i
                      fi
                      done


                      $fn is something you want to find.



                      $i/$fn may be $i$fn sometimes.






                      share|improve this answer















                      This script works similar to the command where



                      #!/bin/bash
                      fn="foo"
                      for i in `echo $PATH|tr ':' 'n'`
                      do
                      if [[ -e "$i/$fn" ]] ; then
                      echo $i
                      fi
                      done


                      $fn is something you want to find.



                      $i/$fn may be $i$fn sometimes.







                      share|improve this answer














                      share|improve this answer



                      share|improve this answer








                      edited Apr 15 '16 at 4:42









                      Lucas

                      2,033818




                      2,033818










                      answered Apr 15 '16 at 4:05









                      framsframs

                      383217




                      383217





















                          0














                          Pure bash, it's the same thing as Wildcard's 2nd method, but this is on one line:



                          echo -e "$PATH//:/"n""





                          share|improve this answer





























                            0














                            Pure bash, it's the same thing as Wildcard's 2nd method, but this is on one line:



                            echo -e "$PATH//:/"n""





                            share|improve this answer



























                              0












                              0








                              0







                              Pure bash, it's the same thing as Wildcard's 2nd method, but this is on one line:



                              echo -e "$PATH//:/"n""





                              share|improve this answer















                              Pure bash, it's the same thing as Wildcard's 2nd method, but this is on one line:



                              echo -e "$PATH//:/"n""






                              share|improve this answer














                              share|improve this answer



                              share|improve this answer








                              edited 2 days ago

























                              answered Apr 15 '16 at 4:05









                              agcagc

                              4,75711138




                              4,75711138





















                                  -1














                                  Shell utils:



                                  echo $PATH | tr ':' 'n'





                                  share|improve this answer



























                                    -1














                                    Shell utils:



                                    echo $PATH | tr ':' 'n'





                                    share|improve this answer

























                                      -1












                                      -1








                                      -1







                                      Shell utils:



                                      echo $PATH | tr ':' 'n'





                                      share|improve this answer













                                      Shell utils:



                                      echo $PATH | tr ':' 'n'






                                      share|improve this answer












                                      share|improve this answer



                                      share|improve this answer










                                      answered Apr 15 '16 at 3:44









                                      agcagc

                                      4,75711138




                                      4,75711138



























                                          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%2f276614%2fbash-while-loop-read-from-colon-delimited-list-of-paths-using-ifs%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

                                          Àrd-bhaile Cathair chruinne/Baile mòr cruinne | Artagailean ceangailte | Clàr-taice na seòladaireachd

                                          대한민국 목차 국명 지리 역사 정치 국방 경제 사회 문화 국제 순위 관련 항목 각주 외부 링크 둘러보기 메뉴북위 37° 34′ 08″ 동경 126° 58′ 36″ / 북위 37.568889° 동경 126.976667°  / 37.568889; 126.976667ehThe Korean Repository문단을 편집문단을 편집추가해Clarkson PLC 사Report for Selected Countries and Subjects-Korea“Human Development Index and its components: P.198”“http://www.law.go.kr/%EB%B2%95%EB%A0%B9/%EB%8C%80%ED%95%9C%EB%AF%BC%EA%B5%AD%EA%B5%AD%EA%B8%B0%EB%B2%95”"한국은 국제법상 한반도 유일 합법정부 아니다" - 오마이뉴스 모바일Report for Selected Countries and Subjects: South Korea격동의 역사와 함께한 조선일보 90년 : 조선일보 인수해 혁신시킨 신석우, 임시정부 때는 '대한민국' 국호(國號) 정해《우리가 몰랐던 우리 역사: 나라 이름의 비밀을 찾아가는 역사 여행》“남북 공식호칭 ‘남한’‘북한’으로 쓴다”“Corea 대 Korea, 누가 이긴 거야?”국내기후자료 - 한국[김대중 前 대통령 서거] 과감한 구조개혁 'DJ노믹스'로 최단기간 환란극복 :: 네이버 뉴스“이라크 "韓-쿠르드 유전개발 MOU 승인 안해"(종합)”“해외 우리국민 추방사례 43%가 일본”차기전차 K2'흑표'의 세계 최고 전력 분석, 쿠키뉴스 엄기영, 2007-03-02두산인프라, 헬기잡는 장갑차 'K21'...내년부터 공급, 고뉴스 이대준, 2008-10-30과거 내용 찾기mk 뉴스 - 구매력 기준으로 보면 한국 1인당 소득 3만弗과거 내용 찾기"The N-11: More Than an Acronym"Archived조선일보 최우석, 2008-11-01Global 500 2008: Countries - South Korea“몇년째 '시한폭탄'... 가계부채, 올해는 터질까”가구당 부채 5000만원 처음 넘어서“‘빚’으로 내몰리는 사회.. 위기의 가계대출”“[경제365] 공공부문 부채 급증…800조 육박”“"소득 양극화 다소 완화...불평등은 여전"”“공정사회·공생발전 한참 멀었네”iSuppli,08年2QのDRAMシェア・ランキングを発表(08/8/11)South Korea dominates shipbuilding industry | Stock Market News & Stocks to Watch from StraightStocks한국 자동차 생산, 3년 연속 세계 5위자동차수출 '현대-삼성 웃고 기아-대우-쌍용은 울고' 과거 내용 찾기동반성장위 창립 1주년 맞아Archived"중기적합 3개업종 합의 무시한 채 선정"李대통령, 사업 무분별 확장 소상공인 생계 위협 질타삼성-LG, 서민업종인 빵·분식사업 잇따라 철수상생은 뒷전…SSM ‘몸집 불리기’ 혈안Archived“경부고속도에 '아시안하이웨이' 표지판”'철의 실크로드' 앞서 '말(言)의 실크로드'부터, 프레시안 정창현, 2008-10-01“'서울 지하철은 안전한가?'”“서울시 “올해 안에 모든 지하철역 스크린도어 설치””“부산지하철 1,2호선 승강장 안전펜스 설치 완료”“전교조, 정부 노조 통계서 처음 빠져”“[Weekly BIZ] 도요타 '제로 이사회'가 리콜 사태 불러들였다”“S Korea slams high tuition costs”““정치가 여론 양극화 부채질… 합리주의 절실””“〈"`촛불집회'는 민주주의의 질적 변화 상징"〉”““촛불집회가 민주주의 왜곡 초래””“국민 65%, "한국 노사관계 대립적"”“한국 국가경쟁력 27위‥노사관계 '꼴찌'”“제대로 형성되지 않은 대한민국 이념지형”“[신년기획-갈등의 시대] 갈등지수 OECD 4위…사회적 손실 GDP 27% 무려 300조”“2012 총선-대선의 키워드는 '국민과 소통'”“한국 삶의 질 27위, 2000년과 2008년 연속 하위권 머물러”“[해피 코리아] 행복점수 68점…해외 평가선 '낙제점'”“한국 어린이·청소년 행복지수 3년 연속 OECD ‘꼴찌’”“한국 이혼율 OECD중 8위”“[통계청] 한국 이혼율 OECD 4위”“오피니언 [이렇게 생각한다] `부부의 날` 에 돌아본 이혼율 1위 한국”“Suicide Rates by Country, Global Health Observatory Data Repository.”“1. 또 다른 차별”“오피니언 [편집자에게] '왕따'와 '패거리 정치' 심리는 닮은꼴”“[미래한국리포트] 무한경쟁에 빠진 대한민국”“대학생 98% "외모가 경쟁력이라는 말 동의"”“특급호텔 웨딩·200만원대 유모차… "남보다 더…" 호화病, 고질병 됐다”“[스트레스 공화국] ① 경쟁사회, 스트레스 쌓인다”““매일 30여명 자살 한국, 의사보다 무속인에…””“"자살 부르는 '우울증', 환자 중 85% 치료 안 받아"”“정신병원을 가다”“대한민국도 ‘묻지마 범죄’,안전지대 아니다”“유엔 "학생 '성적 지향'에 따른 차별 금지하라"”“유엔아동권리위원회 보고서 및 번역본 원문”“고졸 성공스토리 담은 '제빵왕 김탁구' 드라마 나온다”“‘빛 좋은 개살구’ 고졸 취업…실습 대신 착취”원본 문서“정신건강, 사회적 편견부터 고쳐드립니다”‘소통’과 ‘행복’에 목 마른 사회가 잠들어 있던 ‘심리학’ 깨웠다“[포토] 사유리-곽금주 교수의 유쾌한 심리상담”“"올해 한국인 평균 영화관람횟수 세계 1위"(종합)”“[게임연중기획] 게임은 문화다-여가활동 1순위 게임”“영화속 ‘영어 지상주의’ …“왠지 씁쓸한데””“2월 `신문 부수 인증기관` 지정..방송법 후속작업”“무료신문 성장동력 ‘차별성’과 ‘갈등해소’”대한민국 국회 법률지식정보시스템"Pew Research Center's Religion & Public Life Project: South Korea"“amp;vwcd=MT_ZTITLE&path=인구·가구%20>%20인구총조사%20>%20인구부문%20>%20 총조사인구(2005)%20>%20전수부문&oper_YN=Y&item=&keyword=종교별%20인구& amp;lang_mode=kor&list_id= 2005년 통계청 인구 총조사”원본 문서“한국인이 좋아하는 취미와 운동 (2004-2009)”“한국인이 좋아하는 취미와 운동 (2004-2014)”Archived“한국, `부분적 언론자유국' 강등〈프리덤하우스〉”“국경없는기자회 "한국, 인터넷감시 대상국"”“한국, 조선산업 1위 유지(S. Korea Stays Top Shipbuilding Nation) RZD-Partner Portal”원본 문서“한국, 4년 만에 ‘선박건조 1위’”“옛 마산시,인터넷속도 세계 1위”“"한국 초고속 인터넷망 세계1위"”“인터넷·휴대폰 요금, 외국보다 훨씬 비싸”“한국 관세행정 6년 연속 세계 '1위'”“한국 교통사고 사망자 수 OECD 회원국 중 2위”“결핵 후진국' 한국, 환자가 급증한 이유는”“수술은 신중해야… 자칫하면 생명 위협”대한민국분류대한민국의 지도대한민국 정부대표 다국어포털대한민국 전자정부대한민국 국회한국방송공사about korea and information korea브리태니커 백과사전(한국편)론리플래닛의 정보(한국편)CIA의 세계 정보(한국편)마리암 부디아 (Mariam Budia),『한국: 하늘이 내린 한 폭의 그림』, 서울: 트랜스라틴 19호 (2012년 3월)대한민국ehehehehehehehehehehehehehehWorldCat132441370n791268020000 0001 2308 81034078029-6026373548cb11863345f(데이터)00573706ge128495

                                          Cannot Extend partition with GParted The 2019 Stack Overflow Developer Survey Results Are In Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern) 2019 Community Moderator Election ResultsCan't increase partition size with GParted?GParted doesn't recognize the unallocated space after my current partitionWhat is the best way to add unallocated space located before to Ubuntu 12.04 partition with GParted live?I can't figure out how to extend my Arch home partition into free spaceGparted Linux Mint 18.1 issueTrying to extend but swap partition is showing as Unknown in Gparted, shows proper from fdiskRearrange partitions in gparted to extend a partitionUnable to extend partition even though unallocated space is next to it using GPartedAllocate free space to root partitiongparted: how to merge unallocated space with a partition