https://bugs.kde.org/show_bug.cgi?id=457335
tagwer...@innerjoin.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tagwer...@innerjoin.org
--- Comment #1 from tagwer...@innerjoin.org ---
For me, if I create SomeFileWithUppercase.txt and somefilewithuppercase.txt, I
see both:
$ baloosearch -i somefilewithuppercase
1404130000fc01 /home/test/somefilewithuppercase.txt
1403880000fc01 /home/test/SomeFileWithUppercase.txt
and I see, with balooshow, that the index contains the two files:
$ balooshow -x somefilewithuppercase.txt
1404130000fc01 64513 1311763 somefilewithuppercase.txt
[/home/test/somefilewithuppercase.txt]
Mtime: 1660941653 2022-08-19T22:40:53
Ctime: 1660941653 2022-08-19T22:40:53
Cached properties:
Line Count: 1
Internal Info
Terms: Mplain Mtext T5 T8 X20-1 hello penguin
File Name Terms: Fsomefilewithuppercase Ftxt
XAttr Terms:
lineCount: 1
$ balooshow -x SomeFileWithUppercase.txt
1403880000fc01 64513 1311624 SomeFileWithUppercase.txt
[/home/test/SomeFileWithUppercase.txt]
Mtime: 1660941644 2022-08-19T22:40:44
Ctime: 1660941644 2022-08-19T22:40:44
Cached properties:
Line Count: 1
Internal Info
Terms: Mplain Mtext T5 T8 X20-1 hello penguin
File Name Terms: Fsomefilewithuppercase Ftxt
XAttr Terms:
lineCount: 1
The "File Name Terms" for both are held in lower case - baloo squashes terms
down to lower case.
I did this test on Neon with ext4 filesystem, one that treats
SomeFileWithUppercase.txt and somefilewithuppercase.txt as distinct.
The question is what might happen with other filesystems; for vfat if you try
to create SomeFileWithUppercase.txt and then somefilewithuppercase.txt, you are
creating just the one file.
You are on an arch setup? What filesystem are you using? (I'm assuming your
files are on a local disc)
--
You are receiving this mail because:
You are watching all bug changes.
