https://bugs.kde.org/show_bug.cgi?id=410680
tagwer...@innerjoin.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
CC| |tagwer...@innerjoin.org
Status|REPORTED |RESOLVED
--- Comment #1 from tagwer...@innerjoin.org ---
Looks like it's fixed along the way...
I can run a bash script
for i in {1..1000000}; do echo "$i" >> largefile.txt; done
echo "9999999" >> largefile.txt
wait for a few seconds and then
baloosearch 9999999
which finds "largefile.txt"
For an html, the equiv:
echo "<HTML><BODY>" > largefile.html
for i in {1..1000000}; do echo "<P>$i</P>" >> largefile.html; done
echo "<P>9999999</P>" >> largefile.html
echo "</BODY></HTML>" >> largefile.html
and try
baloosearch 9999999
again - shows largefile.html
It's possible that committing the changes from memory to disc takes time after
"Balooctl monitor" says the file has been indexed. For the million-line-file,
the baloo index is about 14 Mbyte.
Checked on
Neon Unstable
Plasma: 5.22.80
Frameworks: 5.84.0
Qt: 5.15.3
--
You are receiving this mail because:
You are watching all bug changes.
