~/.kde/share/config/kdev-must-begin-the-string

Steven T. Hatton hattons at globalsymmetry.com
Tue Jun 1 19:44:03 UTC 2004


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I have a sincere aversion to arrangements such as the flat structure of the 
~/.kde/share/config/ directory.  It makes it difficult to determine what 
files belong together, as well as to identify which files might be associated 
with a particular program.  One approach to mitigating that problem is to use 
naming conventions such as starting all files that involve kdevelop with the 
same string.  My preference would be kdevelop-3.0.3.  I suspect that might be 
a hard sell.  I had been under the impression all configuration file for 
KDevelop began with kdev.  That is until I did a grep -ri kdevdocument * and 
found dockdevtocpluginrc.  Fortunately I knew a parameter to grep for.  
Perhaps there is some compelling reason to start the dockdevtocpluginrc with 
a different character sequence than the other KDevelop configuration files.  
If not, I strongly urge that informal convention of beginning the file name 
with kdev be adhered to. I also suggest with emphasis that a formal naming 
system that will clearly map config files to their respective programs be 
established.
- -- 
Regards,
Steven
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQFAvMBowX61+IL0QsMRAuZBAKDJV2TftzK2ty4mad28RVAmU8eipACguJjY
OonAUb6tXoUsUyd55NiqNMY=
=DtpG
-----END PGP SIGNATURE-----




More information about the KDevelop-devel mailing list