Sure!
mdfind "kMDItemFSName == '*.py' && kMDItemTextContent == 'cat'" -0 |
xargs -0 grep -i -B 3 -A 2 "cat"
Didn't need to install an additional piece of software at all!
On Wed, 6 May 2026 13:34:55 -0700, Alan wrote:
Sure!
mdfind "kMDItemFSName == '*.py' && kMDItemTextContent == 'cat'" -0 |
xargs -0 grep -i -B 3 -A 2 "cat"
Didn't need to install an additional piece of software at all!
And this is easier than 'find . -name "*.py" | .....
On 2026-05-06 12:57, John Bokma wrote:
Can you show me how to use mdfind to:
search in all python only files for the word 'cat' showing the line
the word 'cat' is found on and the 3 lines before this line and 2 after?
Sure!
mdfind "kMDItemFSName == '*.py' && kMDItemTextContent == 'cat'" -0 |
xargs -0 grep -i -B 3 -A 2 "cat"
Didn't need to install an additional piece of software at all!
On 06/05/2026 22:34, Alan wrote:
On 2026-05-06 12:57, John Bokma wrote:
[..]
Can you show me how to use mdfind to:
search in all python only files for the word 'cat' showing the line
the word 'cat' is found on and the 3 lines before this line and 2 after? >>>
Sure!
mdfind "kMDItemFSName == '*.py' && kMDItemTextContent == 'cat'" -0 |
xargs -0 grep -i -B 3 -A 2 "cat"
Didn't need to install an additional piece of software at all!
Ok, fair enough, although you need extra commands.
ag --python -B3 -A2 '\bcat\b'
Easier to remember.
On 2026-05-06 18:34, rbowman wrote:
On Wed, 6 May 2026 13:34:55 -0700, Alan wrote:
Sure!
mdfind "kMDItemFSName == '*.py' && kMDItemTextContent == 'cat'" -0 |
xargs -0 grep -i -B 3 -A 2 "cat"
Didn't need to install an additional piece of software at all!
And this is easier than 'find . -name "*.py" | .....
Faster... ...like a LOT faster; impossibly faster.
On my drive with 2,711,067 files, running my command takes...
(Running it again now)
...1 second.
On 2026-05-07 03:08, John Bokma wrote:
On 06/05/2026 22:34, Alan wrote:
On 2026-05-06 12:57, John Bokma wrote:
[..]
Can you show me how to use mdfind to:Sure!
search in all python only files for the word 'cat' showing the line
the word 'cat' is found on and the 3 lines before this line and 2 after? >>>
mdfind "kMDItemFSName == '*.py' && kMDItemTextContent == 'cat'" -0 |
xargs -0 grep -i -B 3 -A 2 "cat"
Didn't need to install an additional piece of software at all!
Ok, fair enough, although you need extra commands.
ag --python -B3 -A2 '\bcat\b'
Easier to remember.
Given that the tools exist to "remember" for you, that hardly matters,
and I guarantee you that mdfind is orders of magnitude faster.
Alan wrote this screed in ALL-CAPS:Nope.
On 2026-05-06 18:34, rbowman wrote:
On Wed, 6 May 2026 13:34:55 -0700, Alan wrote:
Sure!
mdfind "kMDItemFSName == '*.py' && kMDItemTextContent == 'cat'" -0 |
xargs -0 grep -i -B 3 -A 2 "cat"
Didn't need to install an additional piece of software at all!
And this is easier than 'find . -name "*.py" | .....
Faster... ...like a LOT faster; impossibly faster.
On my drive with 2,711,067 files, running my command takes...
(Running it again now)
...1 second.
Cached, obviously :-D
Alan wrote this screed in ALL-CAPS:You need to learn a little more about how Apple implemented what in the
On 2026-05-07 03:08, John Bokma wrote:
On 06/05/2026 22:34, Alan wrote:
On 2026-05-06 12:57, John Bokma wrote:
[..]
Can you show me how to use mdfind to:Sure!
search in all python only files for the word 'cat' showing the line
the word 'cat' is found on and the 3 lines before this line and 2 after? >>>>
mdfind "kMDItemFSName == '*.py' && kMDItemTextContent == 'cat'" -0 |
xargs -0 grep -i -B 3 -A 2 "cat"
Didn't need to install an additional piece of software at all!
Ok, fair enough, although you need extra commands.
ag --python -B3 -A2 '\bcat\b'
Easier to remember.
Given that the tools exist to "remember" for you, that hardly matters,
and I guarantee you that mdfind is orders of magnitude faster.
Sounds a bit like UNIX locate/plocate.
On 2026-05-08 10:44, Chris Ahlstrom wrote:
Alan wrote this screed in ALL-CAPS:Nope.
On 2026-05-06 18:34, rbowman wrote:
On Wed, 6 May 2026 13:34:55 -0700, Alan wrote:
Sure!
mdfind "kMDItemFSName == '*.py' && kMDItemTextContent == 'cat'" -0 | >>>>> xargs -0 grep -i -B 3 -A 2 "cat"
Didn't need to install an additional piece of software at all!
And this is easier than 'find . -name "*.py" | .....
Faster... ...like a LOT faster; impossibly faster.
On my drive with 2,711,067 files, running my command takes...
(Running it again now)
...1 second.
Cached, obviously :-D
Indexed.
On 2026-05-08 10:52, Chris Ahlstrom wrote:
Alan wrote this screed in ALL-CAPS:You need to learn a little more about how Apple implemented what in the
On 2026-05-07 03:08, John Bokma wrote:
On 06/05/2026 22:34, Alan wrote:
On 2026-05-06 12:57, John Bokma wrote:
[..]
Can you show me how to use mdfind to:Sure!
search in all python only files for the word 'cat' showing the line >>>>>> the word 'cat' is found on and the 3 lines before this line and 2 after? >>>>>
mdfind "kMDItemFSName == '*.py' && kMDItemTextContent == 'cat'" -0 | >>>>> xargs -0 grep -i -B 3 -A 2 "cat"
Didn't need to install an additional piece of software at all!
Ok, fair enough, although you need extra commands.
ag --python -B3 -A2 '\bcat\b'
Easier to remember.
Given that the tools exist to "remember" for you, that hardly matters,
and I guarantee you that mdfind is orders of magnitude faster.
Sounds a bit like UNIX locate/plocate.
GUI part of the OS is called "Spotlight".
"mdfind" is just a command line tool that leverages the same index that
is created for Spotlight.
I just ran this:
agbaker@Alans-M3 / % time mdfind ahlstrom
The result:
2026-05-08 11:37:24.286 mdfind[57515:2714553] [UserQueryParser] Loading keywords and predicates for locale "en_CA"
2026-05-08 11:37:24.286 mdfind[57515:2714553] [UserQueryParser] Loading keywords and predicates for locale "en"
/Users/agbaker/Library/Group
Containers/UBF8T346G9.Office/Outlook/Outlook 15 Profiles/Main Profile/Data/Messages/109/6DCA995E-E984-4A01-8FEA-ECF490248F0B.olk15Message
mdfind ahlstrom 0.04s user 0.06s system 38% cpu 0.259 total
Alan wrote this screed in ALL-CAPS:
On 2026-05-08 10:44, Chris Ahlstrom wrote:
Alan wrote this screed in ALL-CAPS:Nope.
On 2026-05-06 18:34, rbowman wrote:
On Wed, 6 May 2026 13:34:55 -0700, Alan wrote:
Sure!
mdfind "kMDItemFSName == '*.py' && kMDItemTextContent == 'cat'" -0 | >>>>>> xargs -0 grep -i -B 3 -A 2 "cat"
Didn't need to install an additional piece of software at all!
And this is easier than 'find . -name "*.py" | .....
Faster... ...like a LOT faster; impossibly faster.
On my drive with 2,711,067 files, running my command takes...
(Running it again now)
...1 second.
Cached, obviously :-D
Indexed.
And cached.
Alan wrote this screed in ALL-CAPS:
On 2026-05-08 10:52, Chris Ahlstrom wrote:
Alan wrote this screed in ALL-CAPS:You need to learn a little more about how Apple implemented what in the
On 2026-05-07 03:08, John Bokma wrote:
On 06/05/2026 22:34, Alan wrote:
On 2026-05-06 12:57, John Bokma wrote:
[..]
Can you show me how to use mdfind to:
search in all python only files for the word 'cat' showing the line >>>>>>> the word 'cat' is found on and the 3 lines before this line and 2 after?
Sure!
mdfind "kMDItemFSName == '*.py' && kMDItemTextContent == 'cat'" -0 | >>>>>> xargs -0 grep -i -B 3 -A 2 "cat"
Didn't need to install an additional piece of software at all!
Ok, fair enough, although you need extra commands.
ag --python -B3 -A2 '\bcat\b'
Easier to remember.
Given that the tools exist to "remember" for you, that hardly matters, >>>> and I guarantee you that mdfind is orders of magnitude faster.
Sounds a bit like UNIX locate/plocate.
GUI part of the OS is called "Spotlight".
"mdfind" is just a command line tool that leverages the same index that
is created for Spotlight.
Duh-uh. I found that out on my own.
I just ran this:
agbaker@Alans-M3 / % time mdfind ahlstrom
The result:
2026-05-08 11:37:24.286 mdfind[57515:2714553] [UserQueryParser] Loading
keywords and predicates for locale "en_CA"
2026-05-08 11:37:24.286 mdfind[57515:2714553] [UserQueryParser] Loading
keywords and predicates for locale "en"
/Users/agbaker/Library/Group
Containers/UBF8T346G9.Office/Outlook/Outlook 15 Profiles/Main
Profile/Data/Messages/109/6DCA995E-E984-4A01-8FEA-ECF490248F0B.olk15Message >>
mdfind ahlstrom 0.04s user 0.06s system 38% cpu 0.259 total
Whoop de do.
$ time locate ahlstrom &> /dev/null
real 0m1.027s
user 0m0.927s
sys 0m0.141s
This is on my computer, and emits 442650 hits (as counted by
piping the command to wc -l.)
Another example, a more realistic use of locate:
$ time locate vim
real 0m0.043s
user 0m0.015s
sys 0m0.023s
On 2026-05-09 05:59, Chris Ahlstrom wrote:
Alan wrote this screed in ALL-CAPS:
On 2026-05-08 10:44, Chris Ahlstrom wrote:
Alan wrote this screed in ALL-CAPS:Nope.
On 2026-05-06 18:34, rbowman wrote:
On Wed, 6 May 2026 13:34:55 -0700, Alan wrote:
Sure!
mdfind "kMDItemFSName == '*.py' && kMDItemTextContent == 'cat'" -0 | >>>>>>> xargs -0 grep -i -B 3 -A 2 "cat"
Didn't need to install an additional piece of software at all!
And this is easier than 'find . -name "*.py" | .....
Faster... ...like a LOT faster; impossibly faster.
On my drive with 2,711,067 files, running my command takes...
(Running it again now)
...1 second.
Cached, obviously :-D
Indexed.
And cached.
Nope.
Yes, there is an index.
No, nothing was cached.
On 2026-05-09 06:06, Chris Ahlstrom wrote:
Alan wrote this screed in ALL-CAPS:
On 2026-05-08 10:52, Chris Ahlstrom wrote:
Alan wrote this screed in ALL-CAPS:You need to learn a little more about how Apple implemented what in the
On 2026-05-07 03:08, John Bokma wrote:
On 06/05/2026 22:34, Alan wrote:
On 2026-05-06 12:57, John Bokma wrote:
[..]
Can you show me how to use mdfind to:
search in all python only files for the word 'cat' showing the line >>>>>>>> the word 'cat' is found on and the 3 lines before this line and 2 after?
Sure!
mdfind "kMDItemFSName == '*.py' && kMDItemTextContent == 'cat'" -0 | >>>>>>> xargs -0 grep -i -B 3 -A 2 "cat"
Didn't need to install an additional piece of software at all!
Ok, fair enough, although you need extra commands.
ag --python -B3 -A2 '\bcat\b'
Easier to remember.
Given that the tools exist to "remember" for you, that hardly matters, >>>>> and I guarantee you that mdfind is orders of magnitude faster.
Sounds a bit like UNIX locate/plocate.
GUI part of the OS is called "Spotlight".
"mdfind" is just a command line tool that leverages the same index that
is created for Spotlight.
Duh-uh. I found that out on my own.
I just ran this:
agbaker@Alans-M3 / % time mdfind ahlstrom
The result:
2026-05-08 11:37:24.286 mdfind[57515:2714553] [UserQueryParser] Loading
keywords and predicates for locale "en_CA"
2026-05-08 11:37:24.286 mdfind[57515:2714553] [UserQueryParser] Loading
keywords and predicates for locale "en"
/Users/agbaker/Library/Group
Containers/UBF8T346G9.Office/Outlook/Outlook 15 Profiles/Main
Profile/Data/Messages/109/6DCA995E-E984-4A01-8FEA-ECF490248F0B.olk15Message >>>
mdfind ahlstrom 0.04s user 0.06s system 38% cpu 0.259 total
Whoop de do.
$ time locate ahlstrom &> /dev/null
real 0m1.027s
user 0m0.927s
sys 0m0.141s
This is on my computer, and emits 442650 hits (as counted by
piping the command to wc -l.)
Another example, a more realistic use of locate:
$ time locate vim
real 0m0.043s
user 0m0.015s
sys 0m0.023s
"locate" doesn't locate everything.
"mdfind" and the system it uses indexing everything.
Alan wrote this screed in ALL-CAPS:
On 2026-05-09 06:06, Chris Ahlstrom wrote:
Alan wrote this screed in ALL-CAPS:
On 2026-05-08 10:52, Chris Ahlstrom wrote:
Alan wrote this screed in ALL-CAPS:You need to learn a little more about how Apple implemented what in the >>>> GUI part of the OS is called "Spotlight".
On 2026-05-07 03:08, John Bokma wrote:
On 06/05/2026 22:34, Alan wrote:
On 2026-05-06 12:57, John Bokma wrote:
[..]
Can you show me how to use mdfind to:
search in all python only files for the word 'cat' showing the line >>>>>>>>> the word 'cat' is found on and the 3 lines before this line and 2 after?
Sure!
mdfind "kMDItemFSName == '*.py' && kMDItemTextContent == 'cat'" -0 | >>>>>>>> xargs -0 grep -i -B 3 -A 2 "cat"
Didn't need to install an additional piece of software at all!
Ok, fair enough, although you need extra commands.
ag --python -B3 -A2 '\bcat\b'
Easier to remember.
Given that the tools exist to "remember" for you, that hardly matters, >>>>>> and I guarantee you that mdfind is orders of magnitude faster.
Sounds a bit like UNIX locate/plocate.
"mdfind" is just a command line tool that leverages the same index that >>>> is created for Spotlight.
Duh-uh. I found that out on my own.
I just ran this:
agbaker@Alans-M3 / % time mdfind ahlstrom
The result:
2026-05-08 11:37:24.286 mdfind[57515:2714553] [UserQueryParser] Loading >>>> keywords and predicates for locale "en_CA"
2026-05-08 11:37:24.286 mdfind[57515:2714553] [UserQueryParser] Loading >>>> keywords and predicates for locale "en"
/Users/agbaker/Library/Group
Containers/UBF8T346G9.Office/Outlook/Outlook 15 Profiles/Main
Profile/Data/Messages/109/6DCA995E-E984-4A01-8FEA-ECF490248F0B.olk15Message
mdfind ahlstrom 0.04s user 0.06s system 38% cpu 0.259 total
Whoop de do.
$ time locate ahlstrom &> /dev/null
real 0m1.027s
user 0m0.927s
sys 0m0.141s
This is on my computer, and emits 442650 hits (as counted by
piping the command to wc -l.)
Another example, a more realistic use of locate:
$ time locate vim
real 0m0.043s
user 0m0.015s
sys 0m0.023s
"locate" doesn't locate everything.
Define "everything".
"mdfind" and the system it uses indexing everything.
You really need to be precise, because index all information on
a disk would be huge.
$ locate xyz
This finds about 20 files on this system.
Fwiw, /var/lib/plocate/plocate.db is about 22 Mb on this system.
Alan wrote this screed in ALL-CAPS:
On 2026-05-09 05:59, Chris Ahlstrom wrote:
Alan wrote this screed in ALL-CAPS:
On 2026-05-08 10:44, Chris Ahlstrom wrote:
Alan wrote this screed in ALL-CAPS:Nope.
On 2026-05-06 18:34, rbowman wrote:
On Wed, 6 May 2026 13:34:55 -0700, Alan wrote:
Sure!
mdfind "kMDItemFSName == '*.py' && kMDItemTextContent == 'cat'" -0 | >>>>>>>> xargs -0 grep -i -B 3 -A 2 "cat"
Didn't need to install an additional piece of software at all!
And this is easier than 'find . -name "*.py" | .....
Faster... ...like a LOT faster; impossibly faster.
On my drive with 2,711,067 files, running my command takes...
(Running it again now)
...1 second.
Cached, obviously :-D
Indexed.
And cached.
Nope.
Yes, there is an index.
No, nothing was cached.
Are you saying that MacOS does not cache data? Data such as... an
index?
Surely you're joking, Mr. Fine Man!
Alan wrote this screed in ALL-CAPS:
On 2026-05-09 06:06, Chris Ahlstrom wrote:
Alan wrote this screed in ALL-CAPS:
On 2026-05-08 10:52, Chris Ahlstrom wrote:
Alan wrote this screed in ALL-CAPS:You need to learn a little more about how Apple implemented what in the >>>> GUI part of the OS is called "Spotlight".
On 2026-05-07 03:08, John Bokma wrote:
On 06/05/2026 22:34, Alan wrote:
On 2026-05-06 12:57, John Bokma wrote:
[..]
Can you show me how to use mdfind to:
search in all python only files for the word 'cat' showing the line >>>>>>>>> the word 'cat' is found on and the 3 lines before this line and 2 after?
Sure!
mdfind "kMDItemFSName == '*.py' && kMDItemTextContent == 'cat'" -0 | >>>>>>>> xargs -0 grep -i -B 3 -A 2 "cat"
Didn't need to install an additional piece of software at all!
Ok, fair enough, although you need extra commands.
ag --python -B3 -A2 '\bcat\b'
Easier to remember.
Given that the tools exist to "remember" for you, that hardly matters, >>>>>> and I guarantee you that mdfind is orders of magnitude faster.
Sounds a bit like UNIX locate/plocate.
"mdfind" is just a command line tool that leverages the same index that >>>> is created for Spotlight.
Duh-uh. I found that out on my own.
I just ran this:
agbaker@Alans-M3 / % time mdfind ahlstrom
The result:
2026-05-08 11:37:24.286 mdfind[57515:2714553] [UserQueryParser] Loading >>>> keywords and predicates for locale "en_CA"
2026-05-08 11:37:24.286 mdfind[57515:2714553] [UserQueryParser] Loading >>>> keywords and predicates for locale "en"
/Users/agbaker/Library/Group
Containers/UBF8T346G9.Office/Outlook/Outlook 15 Profiles/Main
Profile/Data/Messages/109/6DCA995E-E984-4A01-8FEA-ECF490248F0B.olk15Message
mdfind ahlstrom 0.04s user 0.06s system 38% cpu 0.259 total
Whoop de do.
$ time locate ahlstrom &> /dev/null
real 0m1.027s
user 0m0.927s
sys 0m0.141s
This is on my computer, and emits 442650 hits (as counted by
piping the command to wc -l.)
Another example, a more realistic use of locate:
$ time locate vim
real 0m0.043s
user 0m0.015s
sys 0m0.023s
"locate" doesn't locate everything.
Define "everything".
"mdfind" and the system it uses indexing everything.
You really need to be precise, because index all information on
a disk would be huge.
$ locate xyz
This finds about 20 files on this system.
Fwiw, /var/lib/plocate/plocate.db is about 22 Mb on this system.
On 2026-05-10 05:06, Chris Ahlstrom wrote:
Alan wrote this screed in ALL-CAPS:
On 2026-05-09 05:59, Chris Ahlstrom wrote:
Alan wrote this screed in ALL-CAPS:
On 2026-05-08 10:44, Chris Ahlstrom wrote:
Alan wrote this screed in ALL-CAPS:Nope.
On 2026-05-06 18:34, rbowman wrote:
On Wed, 6 May 2026 13:34:55 -0700, Alan wrote:
Sure!And this is easier than 'find . -name "*.py" | .....
mdfind "kMDItemFSName == '*.py' && kMDItemTextContent == 'cat'" -0 | >>>>>>>>> xargs -0 grep -i -B 3 -A 2 "cat"
Didn't need to install an additional piece of software at all! >>>>>>>>
Faster... ...like a LOT faster; impossibly faster.
On my drive with 2,711,067 files, running my command takes...
(Running it again now)
...1 second.
Cached, obviously :-D
Indexed.
And cached.
Nope.
Yes, there is an index.
No, nothing was cached.
Are you saying that MacOS does not cache data? Data such as... an
index?
Surely you're joking, Mr. Fine Man!
An index is not a cache.
You were trying to imply that it ran fast because it had run immediately before.
Alan wrote this screed in ALL-CAPS:
On 2026-05-10 05:06, Chris Ahlstrom wrote:
Alan wrote this screed in ALL-CAPS:
On 2026-05-09 05:59, Chris Ahlstrom wrote:
Alan wrote this screed in ALL-CAPS:
On 2026-05-08 10:44, Chris Ahlstrom wrote:
Alan wrote this screed in ALL-CAPS:Nope.
On 2026-05-06 18:34, rbowman wrote:
On Wed, 6 May 2026 13:34:55 -0700, Alan wrote:
Sure!And this is easier than 'find . -name "*.py" | .....
mdfind "kMDItemFSName == '*.py' && kMDItemTextContent == 'cat'" -0 | >>>>>>>>>> xargs -0 grep -i -B 3 -A 2 "cat"
Didn't need to install an additional piece of software at all! >>>>>>>>>
Faster... ...like a LOT faster; impossibly faster.
On my drive with 2,711,067 files, running my command takes...
(Running it again now)
...1 second.
Cached, obviously :-D
Indexed.
And cached.
Nope.
Yes, there is an index.
No, nothing was cached.
Are you saying that MacOS does not cache data? Data such as... an
index?
Surely you're joking, Mr. Fine Man!
An index is not a cache.
Duh!
You were trying to imply that it ran fast because it had run immediately
before.
I'm done with you, so obtuse, on this topic.
On Sun, 10 May 2026 08:16:39 -0400, Chris Ahlstrom wrote:
$ locate xyz
This finds about 20 files on this system.
It finds 134 on mine :) That's what happens when you mess around with GIS stuff. There are a lot of Python and Node library files to handle tile requests. The plocate database is 40 MB.
rbowman wrote this screed in ALL-CAPS:
On Sun, 10 May 2026 08:16:39 -0400, Chris Ahlstrom wrote:
$ locate xyz
This finds about 20 files on this system.
It finds 134 on mine :) That's what happens when you mess around with GIS >> stuff. There are a lot of Python and Node library files to handle tile
requests. The plocate database is 40 MB.
Arguing with an Apple fanboi is like mud wrestling a pig.
Seems so. I explicitly noted that an index can be cached.
On 2026-05-11 04:33, Chris Ahlstrom wrote:
rbowman wrote this screed in ALL-CAPS:
On Sun, 10 May 2026 08:16:39 -0400, Chris Ahlstrom wrote:
$ locate xyz
This finds about 20 files on this system.
It finds 134 on mine :) That's what happens when you mess around
with GIS stuff. There are a lot of Python and Node library files to
handle tile requests. The plocate database is 40 MB.
Arguing with an Apple fanboi is like mud wrestling a pig.
Seems so. I explicitly noted that an index can be cached.
No. You made no such explicit claim...
...but good job running away to the safety of COLA.
:-)
Alan <nuh-uh@nope.com> wrote in news:10tt3h2$19gng$2@dont-email.me:
On 2026-05-11 04:33, Chris Ahlstrom wrote:
rbowman wrote this screed in ALL-CAPS:
On Sun, 10 May 2026 08:16:39 -0400, Chris Ahlstrom wrote:
$ locate xyz
This finds about 20 files on this system.
It finds 134 on mine :) That's what happens when you mess around
with GIS stuff. There are a lot of Python and Node library files to
handle tile requests. The plocate database is 40 MB.
Arguing with an Apple fanboi is like mud wrestling a pig.
Seems so. I explicitly noted that an index can be cached.
No. You made no such explicit claim...
...but good job running away to the safety of COLA.
:-)
How much is Apple paying you Alan to be an extreme fanboy?
Whatever it is, they are wasting their money because you are considered a joke. Nobody trusts your post. Most people ignore them.
So how much you making to spew this garbage?
Alan <nuh-uh@nope.com> wrote in news:10tt3h2$19gng$2@dont-email.me:
On 2026-05-11 04:33, Chris Ahlstrom wrote:
rbowman wrote this screed in ALL-CAPS:
On Sun, 10 May 2026 08:16:39 -0400, Chris Ahlstrom wrote:
$ locate xyz
This finds about 20 files on this system.
It finds 134 on mine :) That's what happens when you mess around
with GIS stuff. There are a lot of Python and Node library files to
handle tile requests. The plocate database is 40 MB.
Arguing with an Apple fanboi is like mud wrestling a pig.
Seems so. I explicitly noted that an index can be cached.
No. You made no such explicit claim...
...but good job running away to the safety of COLA.
:-)
How much is Apple paying you Alan to be an extreme fanboy?
Whatever it is, they are wasting their money because you are considered a joke. Nobody trusts your post. Most people ignore them.
So how much you making to spew this garbage?
<snip>
I realize that you Linux advocates have to sign a contract in blood with Linus Torvalds before they're allowed to use Linux, but seriously:
Spotlight works excellently, and you just look foolish when you try to compare it to something like "locate".
Alan wrote this screed in ALL-CAPS:
<snip>
I realize that you Linux advocates have to sign a contract in blood with
Linus Torvalds before they're allowed to use Linux, but seriously:
Asshole.
Spotlight works excellently, and you just look foolish when you try to
compare it to something like "locate".
No, we don't.
<snip>
Alan wrote this screed in ALL-CAPS:
<snip>
Meh.
Alan wrote this screed in ALL-CAPS:
<snip>
Meh.
On 2026-05-12 6:48 p.m., Chris Ahlstrom wrote:
Alan wrote this screed in ALL-CAPS:
<snip>
Meh.
You've done the right thing, Chris.
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 65 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 07:12:37 |
| Calls: | 862 |
| Files: | 1,311 |
| Messages: | 264,829 |