Replies: 2 comments
-
Use xdg tools to determine the mime type. Add it in the settings. Iirc something like octet stream. |
Beta Was this translation helpful? Give feedback.
-
I now have this working. To flesh the above response out a bit: At least as far as I can tell, a file with extension is indexed if its extension corresponds to one of the selected MIME types, regardless of its actual MIME type; a file with no extension is indexed if it is empty or its MIME type matches one of the selected MIME types. (On my system at least, empty files are MIME type inode/x-empty; they are indexed even if that MIME type is not in the MIME filter patterns.) That seems to be the behavior I see. To enable indexing of .txt files and of extensionless text files, in the Files plugin settings, select the directory to be indexed and under MIME types click "Advanced". (I missed seeing this earlier.) In the list of available MIME types you can find text/plain corresponding to *.txt. Add text/plain under MIME filter patterns. |
Beta Was this translation helpful? Give feedback.
-
It looks as though the Files plugin does not index *.txt files, or files that have no extension. On the other hand it does seem to index files with unknown extensions; I just created a file named "zom.fnog" and it indexed that, but not "groc.txt" in the same directory. So it appears it actively avoids indexing *.txt and extensionless files specifically. Can this behavior be modified? And are there other file extensions it does not index?
Beta Was this translation helpful? Give feedback.
All reactions