The Picard Maneuver@lemmy.worldM to Lemmy Shitpost@lemmy.world · 1 day agoHappy to helplemmy.worldimagemessage-square38fedilinkarrow-up1683
arrow-up1683imageHappy to helplemmy.worldThe Picard Maneuver@lemmy.worldM to Lemmy Shitpost@lemmy.world · 1 day agomessage-square38fedilink
minus-squareGreenKnight23@lemmy.worldlinkfedilinkarrow-up1·1 day agocould you not open a console and use find or grep?
minus-squareThe Picard Maneuver@lemmy.worldOPMlinkfedilinkarrow-up2·1 day agoI don’t have much experience searching like that yet and still default to using the gui for navigating directories… I’m still a relative linux noob.
minus-squareGreenKnight23@lemmy.worldlinkfedilinkarrow-up2·1 day agoah. makes sense. find is really easy. find -type f -name "*wildcard_filename*" find -type d -name "*wildcard_directoryname*"
minus-squareThe Picard Maneuver@lemmy.worldOPMlinkfedilinkarrow-up2·1 day agoI’ll have to remember this, thanks.
minus-squarevillage604@adultswim.fanlinkfedilinkEnglisharrow-up2·1 day agoIt’s best to not run it on your root folder, because you’ll be greeted with a wall of errors from /proc or other system directories. The main ones I check are: /usr /var /opt /etc /home /lib (usually only when troubleshooting compile errors)
could you not open a console and use find or grep?
I don’t have much experience searching like that yet and still default to using the gui for navigating directories… I’m still a relative linux noob.
ah. makes sense.
find is really easy.
find -type f -name "*wildcard_filename*"find -type d -name "*wildcard_directoryname*"I’ll have to remember this, thanks.
It’s best to not run it on your root folder, because you’ll be greeted with a wall of errors from /proc or other system directories.
The main ones I check are: