https://bugs.kde.org/show_bug.cgi?id=457522
tagwer...@innerjoin.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tagwer...@innerjoin.org
--- Comment #8 from tagwer...@innerjoin.org ---
There's an extra twist...
You did a:
touch myfile.foobar
balooshow -x myfile.foobar
and got
Terms: Mapplication Moctet Mstream
If I try this (on Neon), I get:
Terms: Mapplication Mx Mzerosize
If I do the same for myfile.txt
touch myfile.txt
balooshow -x myfile.txt
I still get:
Terms: Mapplication Mx Mzerosize
The "twist" seems to be if baloo is doing content indexing it flags all(?)
empty files as "application/x-zerosize". If I purge and reindex without
content, I get "application/octet-stream" for the empty myfile.foobar (and
"text/plain" for myfile.txt)
If I look a bit closer with kmimetypefinder, I get:
$ kmimetypefinder myfile.txt
text/plain
$ kmimetypefinder myfile.foobar
application/x-zerosize
and also:
$ echo "Hello Penguin" > myfile.foobar
$ kmimetypefinder myfile.foobar
text/plain
and that seems reasonable: For an empty file, if the filename indicates a
mimetype, use it; if not, say application/x-zerosize.
I'd say baloo ought to give the same results here irrespective of whether it is
content indexing or not and it would probably make sense if it follows
kmimetypefinder logic, so:
"text/plain" for an empty myfile.txt
"application/x-zerosize" for an empty unrecognised filetype (myfile.foobar,
in this case)
"text/plain" for an unrecognised filetype with (text) content
Krunner would then list an empty myfile.txt but not an empty myfile.foobar.
Maybe this is good enough? or am I missing something?
--
You are receiving this mail because:
You are watching all bug changes.
