How do I "ls -R | cat | grep print" ?

Comments

• geekworking@lemmy.world ⁨9⁩ ⁨months⁩ ago

  Use find instead.

  source

  • caseyweederman@lemmy.ca ⁨9⁩ ⁨months⁩ ago

    Seconded, but I always have to look up the syntax. --type=file --name=“string”?

    source
  • sighofannoyance@lemmy.world ⁨9⁩ ⁨months⁩ ago

    Thank you! 🤩

    source
• JTskulk@lemmy.world ⁨9⁩ ⁨months⁩ ago

  Bro you can just run find

  source

  • sighofannoyance@lemmy.world ⁨9⁩ ⁨months⁩ ago

    thanks dude

    source
• Shadow@lemmy.ca ⁨9⁩ ⁨months⁩ ago

  To answer your og question since it is a valuable tool to know about, xargs.

  ls | xargs cat | grep print

  Should do what you want. Unless your file names have spaces, then you should probably not use this.

  source

  • 018118055@sopuli.xyz ⁨9⁩ ⁨months⁩ ago

    find -print0 | xargs -0 can handle spaces

    source
  • sighofannoyance@lemmy.world ⁨9⁩ ⁨months⁩ ago

    thank you

    source
• bjoern_tantau@swg-empire.de ⁨9⁩ ⁨months⁩ ago

  Note, you almost never have to use cat. Just leaving it out would have been enough to find your file (although find is still better).

  When you want to find a string in a file it’s also enough to use grep string file instead of cat file | grep string. You can even search through multiple files with grep string file1 file2 file* and grep will tell you in which file the string was found.

  source

  • litchralee@sh.itjust.works ⁨9⁩ ⁨months⁩ ago

    Obligatory link to the Useless Use of Cat Awards

    source

    • FuglyDuck@lemmy.world ⁨9⁩ ⁨months⁩ ago

      for a moment, I thought OP was looking for cat photos or something.

      source
  • sighofannoyance@lemmy.world ⁨9⁩ ⁨months⁩ ago

    So I could use something like grep string -R * to find any occurrence of the string in any files in the folder and sub-folders.

    thank you!

    source

    • JoeyJoeJoeJr@lemmy.ml ⁨9⁩ ⁨months⁩ ago

      grep -r string .

      The flag should go before the pattern.

      -r to search recursively, . refers to the current directory.

      Why use . instead of *? Because on it’s own, * will (typically) not match hidden files. See the last paragraph of the ‘Origin’ section of: en.m.wikipedia.org/wiki/Glob_(programming). Technically your ls command (lacking the -a) flag would also skip hidden files, but since your comment mentions finding the string in ‘any files,’ I figured hidden files should also be covered (the find commands listed would also find the hidden files).

      source

      • -> View More Comments
• shrugal@lemm.ee ⁨9⁩ ⁨months⁩ ago

  I think you can just do grep print **/*.

  source

  • sighofannoyance@lemmy.world ⁨9⁩ ⁨months⁩ ago

    ty

    source
• surewhynotlem@lemmy.world ⁨9⁩ ⁨months⁩ ago

  It’s valuable to learn how to do an inline loop

  ls | while read A; do cat $A | grep print; done

  This will read each line of ls into variable A, then it’ll get and grep each one.

  source

  • sighofannoyance@lemmy.world ⁨9⁩ ⁨months⁩ ago

    thank you

    source
• muix@lemmy.sdf.org ⁨9⁩ ⁨months⁩ ago

  ripgrep does exactly what you want

  source
• visnae@lemmy.world ⁨9⁩ ⁨months⁩ ago

  grep -r print .

  I.e. Grep on print recursively from . (current directory)

  source

  • sighofannoyance@lemmy.world ⁨9⁩ ⁨months⁩ ago

    this is great ty!

    source
• Toes@ani.social ⁨9⁩ ⁨months⁩ ago

  I just pipe to more and filter with /

  source
• notfromhere@lemmy.ml ⁨9⁩ ⁨months⁩ ago

  [deleted]

  source

  • sighofannoyance@lemmy.world ⁨9⁩ ⁨months⁩ ago

    ty

    source