Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: rbowman Newsgroups: comp.os.linux.misc Subject: Re: =?UTF-8?B?SeKAmW0=?= A Linux Expert, And Here Are 6 Commands I =?UTF-8?B?Q2Fu4oCZdA==?= Live Without Date: 13 Aug 2025 02:40:11 GMT Lines: 14 Message-ID: References: <107gp14$3ko4l$1@dont-email.me> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Trace: individual.net IjIDZMSpTHIqBCjsFl3ROg44NXueFeZcpcBGuZBuZhjtOFu2vL Cancel-Lock: sha1:Wd1FQmH4p8RUc+abT6fy1uYDtP8= sha256:cH8kfy821SNyPj0+bj3DeSwNaFEXAkf0lXtEZojRcV4= User-Agent: Pan/0.162 (Pokrosvk) Xref: csiph.com comp.os.linux.misc:70883 On Wed, 13 Aug 2025 01:16:20 -0000 (UTC), Lawrence D'Oliveiro wrote: > > > What’s an obvious omission from his list? To me, it’s the “find” > command. I have millions of files on my main machine (quite literally, > I would say), and it is the most convenient and powerful way of finding > something I might have worked on years ago, and mostly forgotten about > since then. It's very annoying when I have a senior moment and try to use find on a Windows box. While I have ls, grep, cat, and so forth 'find' finds the lame Windows command. I suppose I should fix that.