KDE System Administration/Configuration Files - Revision history

AnneW at 15:43, 13 July 2012

2012-07-13T15:43:37Z

Neverendingo: Text replace - "" to ""

2011-06-29T20:57:16Z

Text replace - "</code>" to "</syntaxhighlight>"

Neverendingo: Text replace - "`" to ""`


2011-06-29T20:47:49Z
Text replace - "<code>" to "<syntaxhighlight lang="text">"

				
				
				
				
			
			← Older revision
			Revision as of 20:47, 29 June 2011
			
Line 159:
Line 159:
  down. All entries in the "<tt>Mail Settings</tt>" group have been   down. All entries in the "<tt>Mail Settings</tt>" group have been
  locked down as well.   locked down as well.
− <code> + <syntaxhighlight lang="text">
  [Preview Image]   [Preview Image]
  Caption[$i]=My Caption   Caption[$i]=My Caption
Line 189:
Line 189:
  For scripts or modifying files from the command line, the command line app <tt>kwriteconfig</tt> is very useful. <tt>kwriteconfig</tt> expects a configuration file name, a group, a key, an optional type and a value, such as:   For scripts or modifying files from the command line, the command line app <tt>kwriteconfig</tt> is very useful. <tt>kwriteconfig</tt> expects a configuration file name, a group, a key, an optional type and a value, such as:
    
− <code>kwriteconfig --file kickerrc \ + <syntaxhighlight lang="text">kwriteconfig --file kickerrc \
                --group General \                 --group General \
                --key AutoHidePanel \                 --key AutoHidePanel \
                --type bool \                 --type bool \
                true</code>                 true</code>



Neverendingo: Text replace - "" to ""

2011-06-29T20:38:04Z
Text replace - "<code ini>" to "<syntaxhighlight lang="ini">"

				
				
				
				
			
			← Older revision
			Revision as of 20:38, 29 June 2011
			
Line 18:
Line 18:
  "<tt>SingleClick</tt>", the second group contains the keys   "<tt>SingleClick</tt>", the second group contains the keys
  "<tt>Show hidden files</tt>" and "<tt>Sort by</tt>".   "<tt>Show hidden files</tt>" and "<tt>Sort by</tt>".
− <code ini> + <syntaxhighlight lang="ini">
  [KDE]   [KDE]
  LargeCursor=false   LargeCursor=false
Line 49:
Line 49:
  The following config file fragment is equivalent to the one in the   The following config file fragment is equivalent to the one in the
  previous example. Whitespace surrounding the key and value is ignored.   previous example. Whitespace surrounding the key and value is ignored.
− <code ini> + <syntaxhighlight lang="ini">
  [KDE]   [KDE]
  LargeCursor=          false   LargeCursor=          false
Line 63:
Line 63:
  with two spaces while the "<tt>Description</tt>" entry contains three lines   with two spaces while the "<tt>Description</tt>" entry contains three lines
  of text. Linefeeds in backslash notation are used to separate the different lines.   of text. Linefeeds in backslash notation are used to separate the different lines.
− <code ini> + <syntaxhighlight lang="ini">
  [Preview Image]   [Preview Image]
  Caption=\s My Caption   Caption=\s My Caption
Line 121:
Line 121:
  "<tt>joe@joes_host</tt>". The setting is not locked down.   "<tt>joe@joes_host</tt>". The setting is not locked down.
    
− <code ini> + <syntaxhighlight lang="ini">
  [Mail Settings]   [Mail Settings]
  Host[$ie]=$(hostname)   Host[$ie]=$(hostname)
Line 140:
Line 140:
  code <tt>fr</tt>) the value of the entry will be "<tt>Ma Légende</tt>".   code <tt>fr</tt>) the value of the entry will be "<tt>Ma Légende</tt>".
  In all other cases the value "<tt>My Caption</tt>" will be used.   In all other cases the value "<tt>My Caption</tt>" will be used.
− <code ini> + <syntaxhighlight lang="ini">
  [Preview Image]   [Preview Image]
  Caption=My Caption   Caption=My Caption





Tampakrap: Fix encoding issues with "é"
2009-03-18T11:25:25Z
Fix encoding issues with "é"

				
				
				
				
			
			← Older revision
			Revision as of 11:25, 18 March 2009
			
Line 138:
Line 138:
  In the following example the value of the "<tt>Caption</tt>" entry   In the following example the value of the "<tt>Caption</tt>" entry
  depends on the language. If the user has selected french as language (language   depends on the language. If the user has selected french as language (language
− code <tt>fr</tt>) the value of the entry will be "<tt>Ma LÃ©gende</tt>". + code <tt>fr</tt>) the value of the entry will be "<tt>Ma Légende</tt>".
  In all other cases the value "<tt>My Caption</tt>" will be used.   In all other cases the value "<tt>My Caption</tt>" will be used.
  <code ini>   <code ini>
  [Preview Image]   [Preview Image]
  Caption=My Caption   Caption=My Caption
− Caption[fr]=Ma LÃ©gende + Caption[fr]=Ma Légende
  </code>   </code>
    



Sbishop: Just added a few missing punctuation marks and corrected a misspelled word.
2007-10-12T18:46:41Z
Just added a few missing punctuation marks and corrected a misspelled word.

				
				
				
				
			
			← Older revision
			Revision as of 18:46, 12 October 2007
			
Line 1:
Line 1:
  {{Template:I18n/Language Navigation Bar|KDE System Administration/Configuration Files}}   {{Template:I18n/Language Navigation Bar|KDE System Administration/Configuration Files}}
  == File Format ==   == File Format ==
− KDE uses a simple text based file format for all its configuration files. + KDE uses a simple text-based file format for all its configuration files.
  It consists of key-value pairs that are placed in groups. All KDE   It consists of key-value pairs that are placed in groups. All KDE
  configuration files use UTF-8 encoding for text outside the ASCII range.   configuration files use UTF-8 encoding for text outside the ASCII range.
Line 62:
Line 62:
  In the following example the value of the "<tt>Caption</tt>" entry starts   In the following example the value of the "<tt>Caption</tt>" entry starts
  with two spaces while the "<tt>Description</tt>" entry contains three lines   with two spaces while the "<tt>Description</tt>" entry contains three lines
− of text. Linefeeds in backslash notation are used to seperate the different lines. + of text. Linefeeds in backslash notation are used to separate the different lines.
  <code ini>   <code ini>
  [Preview Image]   [Preview Image]
Line 80:
Line 80:
  [[../KDE Filesystem Hierarchy#Location_of_the_Directory_Trees|KDE Directory Trees]].   [[../KDE Filesystem Hierarchy#Location_of_the_Directory_Trees|KDE Directory Trees]].
  In that case the information of all these configuration files is combined   In that case the information of all these configuration files is combined
− on a key by key basis. If the same key within a certain group is defined + on a key-by-key basis. If the same key within a certain group is defined
  in more than one place, the key value read from the directory tree with   in more than one place, the key value read from the directory tree with
  the highest precedence will be used.   the highest precedence will be used.
Line 88:
Line 88:
    
  KDE's cascading configuration scheme can be used to provide users with   KDE's cascading configuration scheme can be used to provide users with
− system or organisation wide default settings while still allowing the users + system or organisation-wide default settings while still allowing the users
  to make individual changes to these settings. KDE will not write entries to   to make individual changes to these settings. KDE will not write entries to
− the users configuration file under $KDEHOME that match any default settings + the user's configuration file under $KDEHOME that match any default settings
  provided this way. This way changes made to the default settings will   provided this way. This way changes made to the default settings will
  immediately be propagated to the user. Note that differs from the traditional   immediately be propagated to the user. Note that differs from the traditional
Line 135:
Line 135:
  the key entry without index is used.   the key entry without index is used.
    
− ==== Example: UTF8 In Keys ==== + ==== Example: UTF-8 In Keys ====
  In the following example the value of the "<tt>Caption</tt>" entry   In the following example the value of the "<tt>Caption</tt>" entry
  depends on the language. If the user has selected french as language (language   depends on the language. If the user has selected french as language (language
Line 173:
Line 173:
  Any changes that applications make to settings that have been locked   Any changes that applications make to settings that have been locked
  down will be silently dropped. Applications may respond differently to locked down settings. Some applications   down will be silently dropped. Applications may respond differently to locked down settings. Some applications
− recognize when a setting has been locked down, and will remove the + recognize when a setting has been locked down and will remove the
− elements from its user interface that would otherwise allow the user + elements from its user interface. Other applications will continue
− to make changes to these settings. Other applications will continue + 
  to offer these options in their user interface even though the option   to offer these options in their user interface even though the option
  does not have any effect any more. It is also possible that it is actually   does not have any effect any more. It is also possible that it is actually
  still possible to change the setting in the running program. In that case the   still possible to change the setting in the running program. In that case the
  changed setting will be effective for the time the program remains running.   changed setting will be effective for the time the program remains running.
− When the program is restarted it will then return to the locked down default + When the program is restarted it will then return to the locked-down default
  settings.   settings.
    





Dhaumann: adapt langbar
2007-09-09T21:36:30Z
adapt langbar

				
				
				
				
			
			← Older revision
			Revision as of 21:36, 9 September 2007
			
Line 1:
Line 1:
− {{Template:I18n/Language Navigation Bar|SysAdmin/Configuration Files}} + {{Template:I18n/Language Navigation Bar|KDE System Administration/Configuration Files}}
  == File Format ==   == File Format ==
  KDE uses a simple text based file format for all its configuration files.   KDE uses a simple text based file format for all its configuration files.



Logixoul: SysAdmin/Configuration Files moved to KDE System Administration/Configuration Files
2007-09-09T17:59:25Z
SysAdmin/Configuration Files moved to KDE System Administration/Configuration Files

			
			← Older revision
			Revision as of 17:59, 9 September 2007
			


Dhaumann: lang bar
2007-07-31T16:47:59Z
lang bar

				
				
				
				
			
			← Older revision
			Revision as of 16:47, 31 July 2007
			
Line 1:
Line 1:
  + {{Template:I18n/Language Navigation Bar|SysAdmin/Configuration Files}}
  == File Format ==   == File Format ==
  KDE uses a simple text based file format for all its configuration files.   KDE uses a simple text based file format for all its configuration files.



Pino: 

2007-06-12T14:41:27Z
<code ini>

				
				
				
				
			
			← Older revision
			Revision as of 14:41, 12 June 2007
			
Line 17:
Line 17:
  "<tt>SingleClick</tt>", the second group contains the keys   "<tt>SingleClick</tt>", the second group contains the keys
  "<tt>Show hidden files</tt>" and "<tt>Sort by</tt>".   "<tt>Show hidden files</tt>" and "<tt>Sort by</tt>".
− <code> + <code ini>
  [KDE]   [KDE]
  LargeCursor=false   LargeCursor=false
Line 48:
Line 48:
  The following config file fragment is equivalent to the one in the   The following config file fragment is equivalent to the one in the
  previous example. Whitespace surrounding the key and value is ignored.   previous example. Whitespace surrounding the key and value is ignored.
− <code> + <code ini>
  [KDE]   [KDE]
  LargeCursor=          false   LargeCursor=          false
Line 62:
Line 62:
  with two spaces while the "<tt>Description</tt>" entry contains three lines   with two spaces while the "<tt>Description</tt>" entry contains three lines
  of text. Linefeeds in backslash notation are used to seperate the different lines.   of text. Linefeeds in backslash notation are used to seperate the different lines.
− <code> + <code ini>
  [Preview Image]   [Preview Image]
  Caption=\s My Caption   Caption=\s My Caption
Line 120:
Line 120:
  "<tt>joe@joes_host</tt>". The setting is not locked down.   "<tt>joe@joes_host</tt>". The setting is not locked down.
    
− <code> + <code ini>
  [Mail Settings]   [Mail Settings]
  Host[$ie]=$(hostname)   Host[$ie]=$(hostname)
Line 139:
Line 139:
  code <tt>fr</tt>) the value of the entry will be "<tt>Ma LÃ©gende</tt>".   code <tt>fr</tt>) the value of the entry will be "<tt>Ma LÃ©gende</tt>".
  In all other cases the value "<tt>My Caption</tt>" will be used.   In all other cases the value "<tt>My Caption</tt>" will be used.
− <code> + <code ini>
  [Preview Image]   [Preview Image]
  Caption=My Caption   Caption=My Caption

@@ Line 26: / Line 26: @@
 Show hidden files=false
 Sort by=Name
-</code>
+</syntaxhighlight>
 Entries in a group consists of a key and value separated by an equal sign.
@@ Line 57: / Line 57: @@
     Show hidden files   = false
 Sort by =Name
-</code>
+</syntaxhighlight>
 ==== Example: Preserving Whitespace ====
@@ Line 67: / Line 67: @@
 Caption=\s My Caption
 Description=This is\na very long\ndescription.
-</code>
+</syntaxhighlight>
 Empty lines in configuration files are ignored, just as lines that
@@ Line 125: / Line 125: @@
 Host[$ie]=$(hostname)
 Email[$e]=${USER}@${HOST}
-</code>
+</syntaxhighlight>
 == Localization ==
@@ Line 144: / Line 144: @@
 Caption=My Caption
 Caption[fr]=Ma Légende
-</code>
+</syntaxhighlight>
 == Lock Down ==
@@ Line 166: / Line 166: @@
 Host[$e]=$(hostname)
 Email=wal&#100;o&#x40;&#00107;&#x64;e&#x2e;or&#x67;
-</code>
+</syntaxhighlight>
 If an entry has been locked down, entries that would otherwise take
@@ Line 193: / Line 193: @@
               --key AutoHidePanel \
               --type bool \
-              true</code>
+              true</syntaxhighlight>

← Older revision		Revision as of 16:47, 31 July 2007
Line 1:		Line 1:
		+	{{Template:I18n/Language Navigation Bar\|SysAdmin/Configuration Files}}
	== File Format ==		== File Format ==
	KDE uses a simple text based file format for all its configuration files.		KDE uses a simple text based file format for all its configuration files.