Something that has long puzzled me back into the early KDE 3.x days is why the user's kmailrc config file appears in Konqueror as file type unknown.
I would be grateful for somebody shedding light on this and where in the source code that is configured.
Thanks!
Darrell
On Friday 18 November 2011 21:59:53 Darrell Anderson wrote:
Something that has long puzzled me back into the early KDE 3.x days is why the user's kmailrc config file appears in Konqueror as file type unknown.
that seems strange. here, all config files appear as mime type x-c++hdr, that is, c++ source code headers, which is not exactly true :) but as such konqueror opens them with a text editor (kate, kwrite..) - ok. I think there mst be something wrong on your system w.regard to mime-type recognition. note that on linux, this is done by looking into the file content, not just stupidly based upon file name extension (e.g. .doc) as in windoze...
werner
Le 18/11/2011 21:59, Darrell Anderson a écrit :
Something that has long puzzled me back into the early KDE 3.x days is why the user's kmailrc config file appears in Konqueror as file type unknown.
I would be grateful for somebody shedding light on this and where in the source code that is configured.
For me: same thing with amarokrc krunnerrc and kwriterc.
It happens with a lot of different files elsewhere.
This bug was reported here: http://bugs.kde.org/143100 http://bugs.kde.org/116272 It was closed but never solved.
I saw discussions about the old bugs of KDE 3.5.10, it would be useful to have a full list of known bugs. I didn't find it on the web.
Something that has long puzzled me back into the early
KDE 3.x days is why the user's kmailrc config file appears in Konqueror as file type unknown.
I would be grateful for somebody shedding light on
this and where in the source code that is configured.
For me: same thing with amarokrc krunnerrc and kwriterc.
It happens with a lot of different files elsewhere.
This bug was reported here: http://bugs.kde.org/143100 http://bugs.kde.org/116272 It was closed but never solved.
I saw discussions about the old bugs of KDE 3.5.10, it would be useful to have a full list of known bugs. I didn't find it on the web.
Odd. All of the *rc files are plain text files. I have a couple of *rc files listed in Konqueror as Desktop Config Files.
With no file extension how does Trinity detect or determine the file contents?
I'm guessing there is a flaw in the detection algorithms inherited from KDE3. Where are these detection schemes located in the sources? Somewhere in kdelibs? kdebase?
Darrell
Le 19/11/2011 00:07, Darrell Anderson a écrit :
I'm guessing there is a flaw in the detection algorithms inherited from KDE3. Where are these detection schemes located in the sources? Somewhere in kdelibs? kdebase?
kdelibs/kio/kmime* ?
Le 19/11/2011 00:07, Darrell Anderson a écrit :
I have a couple of *rc files listed in Konqueror as Desktop Config Files.
While listing remaining problems, I noticed these are really desktop files...
I would be grateful for somebody shedding light on
this and where in the source code that is configured.
For me: same thing with amarokrc krunnerrc and kwriterc.
It happens with a lot of different files elsewhere.
You have a krunnerrc config file? Has your TDE profile directory been contaminated by KDE4? Or perhaps you migrated a contaminated KDE3 profile to Trinity? I don't have any such file for any of my KDE3/TDE user accounts.
Darrell
Le 19/11/2011 06:30, Darrell Anderson a écrit :
You have a krunnerrc config file? Has your TDE profile directory been contaminated by KDE4? Or perhaps you migrated a contaminated KDE3 profile to Trinity? I don't have any such file for any of my KDE3/TDE user accounts.
Alt+F2 launch /usr/bin/krunner (from KDE4). When changing settings, it changes ~/.trinity/share/config/krunnerrc...
(And yes, I copied files from ~/.kde in ~/.trinity.)
-
Darrell Anderson -
Laurent Dard -
Werner Joss