SUPER SAIYAN@lemmy.world to memes@lemmy.world · edit-226 天前I suck at naming anythinglemmy.worldimagemessage-square36linkfedilinkarrow-up1259arrow-down120
arrow-up1239arrow-down1imageI suck at naming anythinglemmy.worldSUPER SAIYAN@lemmy.world to memes@lemmy.world · edit-226 天前message-square36linkfedilink
minus-squareBeigeAgenda@lemmy.calinkfedilinkarrow-up5·edit-225 天前Or like me obliviously spending cycles trawling through everything. find dir/ -iname "*John*Cena*" or grep -rIi "John.*Cena" dir/
minus-squaremarcos@lemmy.worldlinkfedilinkarrow-up3·25 天前 spending cycles trawling through everything Beats spending cycles indexing everything and never search them.
minus-squareqjkxbmwvz@startrek.websitelinkfedilinkarrow-up2·25 天前 grep -rIi “John.*Cena” dir/ I have this sort of thing aliased, with some added --include flags to filter file type (e.g., only match source/script files). Super useful!
minus-square[object Object]@lemmy.worldlinkfedilinkarrow-up1·25 天前Use fd and ripgrep at least. It’s not the stone age.
minus-squareBeigeAgenda@lemmy.calinkfedilinkarrow-up1·25 天前I’m probably using them already if they are aliased to find and grep.
minus-square[object Object]@lemmy.worldlinkfedilinkarrow-up3·25 天前Btw, while I’m here: you might also want to look into eza, fzf, bat, and maybe delta (or icdiff for side-by-side comparison). I’m pretty conservative regarding replacement for classic utils, but these are worth it.
minus-square[object Object]@lemmy.worldlinkfedilinkarrow-up1·25 天前They use different arguments, so unlikely. Though idk if there are wrappers or anything like that. They’re both easier to use and faster, so it’s worth making sure to switch.
minus-squareMonkderVierte@lemmy.ziplinkfedilinkarrow-up1·25 天前 obliviously spending cycles trawling through everything. Once vs. every time the db gets updated. Database for faster file searching is a HDD relict, imo.
minus-squareMeron35@lemmy.worldlinkfedilinkarrow-up1·25 天前plocate is much faster and requires less resources. macOS users should use mdfind instead
minus-squareMonkderVierte@lemmy.ziplinkfedilinkarrow-up1·edit-225 天前$ time fd -t f locate /usr /usr/bin/fallocate /usr/include/clang/AST/ASTContextAllocate.h /usr/include/qt6/QtQmlCompiler/6.10.0/QtQmlCompiler/private/qresourcerelocater_p.h /usr/include/qt6/QtQml/6.10.0/QtQml/private/qlazilyallocated_p.h /usr/share/doc/libdc1394/html/structfw__cdev__allocate.html ... /usr/share/xml/docbook/xsl-stylesheets-1.79.2-nons/params/htmlhelp.button.locate.xml /usr/lib/ruby/gems/3.4.0/doc/racc-1.8.1/ri/Racc/Grammar/compute_locate-i.ri /usr/lib/ruby/gems/3.4.0/doc/racc-1.8.1/ri/Racc/Sym/locate-i.ri real 0m0.209s user 0m0.283s sys 0m0.663s Cut by me, because of qr size limit. fd is from here. Disk is NVME on PCIe3.
And mlocate for Linux.
Or like me obliviously spending cycles trawling through everything.
or
Beats spending cycles indexing everything and never search them.
I have this sort of thing aliased, with some added
--includeflags to filter file type (e.g., only match source/script files). Super useful!Use
fdand ripgrep at least. It’s not the stone age.I’m probably using them already if they are aliased to
findandgrep.Btw, while I’m here: you might also want to look into
eza,fzf,bat, and maybedelta(oricdifffor side-by-side comparison). I’m pretty conservative regarding replacement for classic utils, but these are worth it.They use different arguments, so unlikely. Though idk if there are wrappers or anything like that.
They’re both easier to use and faster, so it’s worth making sure to switch.
Once vs. every time the db gets updated. Database for faster file searching is a HDD relict, imo.
plocate is much faster and requires less resources. macOS users should use mdfind instead
Cut by me, because of qr size limit. fd is from here. Disk is NVME on PCIe3.