CODESEARCH(1)

πŸ“¦
version 1.0.0 Β· 3 versions
, in debian trixie, ubuntu questing

🌸 CODESEARCH πŸ’…

okay bestie, gather round, because we're talking about codesearch β€” the Debian Codesearch CLI tool πŸŽ€ it lives in your terminal, it finds stuff, and it's lowkey iconic.


✨ DESCRIPTION ✨

here's the whole vibe, exactly as the tool spits it out when you summon it:

usage: codesearch [-h] [--max-results MAX_RESULTS] [-q] [-l] [--nocolor]
[-n]

       [-d] [-x EXCLUDE] [-m {literal,regexp}] [--per-package]
       searchstring

πŸ¦‹ positional arguments:

  • searchstring β€” yeah this is the thing you're looking for. that's it. that's the whole job. the search string. periodt.

🧚 options:

  • -h, --help β€” shows you this help message and then dips (exit). your little safety net 🫢
  • --max-results MAX_RESULTS β€” takes a value called MAX_RESULTS. and that is genuinely all the manpage says about it, bestie. no description, no elaboration, it's giving mysterious main character energy πŸ’€
  • -q, --quiet β€” quiet mode. again, the manpage just... leaves it there with no explanation. silence really is the point πŸ™ˆ
  • -l, --linenumber β€” linenumber. also undescribed. we love a flag that lets the name do the talking ✨
  • --nocolor β€” Do not colorize output. so no pretty rainbow text, just plain unseasoned output. sad but sometimes necessary 😭
  • -n, --print-filenames β€” Print only matching filenames, no contents. just the names, no receipts, no receipts-adjacent content. like a guest list, not the whole party πŸ‘‘
  • -d, --dedupe β€” amalgamate results for the same file in different packages. so if the same file keeps showing up in a bunch of different packages, it gets smooshed into one. obsessed. no more duplicate jumpscares πŸ”₯
  • -x EXCLUDE, --exclude EXCLUDE β€” list of path fragments to exclude from results. you hand it a list of path fragments and those get yeeted out of your results. not invited to the function 🚫
  • -m {literal,regexp}, --mode {literal,regexp} β€” search mode (literal or regexp). pick your fighter: literal or regexp. two options, one destiny ⭐
  • --per-package β€” group results per source package. so everything gets sorted by its source package instead of one big chaotic pile. organized. structured. slay 🌈
lowkey important: a few of these options come with zero description in the manpage itself. i'm not out here making stuff up about what they do β€” i'm just telling you they exist, exactly as written. fr fr πŸ’–

and that's the whole page, bestie!! this was codesearch version 1.0.0, dated June 2024 πŸŽ€ thanks for reading, go search something, mwah πŸ’…βœ¨

πŸ“¦ where this page comes from