From: Ryan Lortie Date: Thu, 24 Jun 2010 06:21:58 +0000 (-0400) Subject: g_keyfile_settings_backend_new doc improvement X-Git-Tag: 2.25.10~3 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=887d9d83aa232058b8446eafb7f0681db4219a77;p=platform%2Fupstream%2Fglib.git g_keyfile_settings_backend_new doc improvement --- diff --git a/gio/gkeyfilesettingsbackend.c b/gio/gkeyfilesettingsbackend.c index a53777f..94ccced 100644 --- a/gio/gkeyfilesettingsbackend.c +++ b/gio/gkeyfilesettingsbackend.c @@ -591,10 +591,10 @@ dir_changed (GFileMonitor *monitor, * "toplevel", then settings the key "/apps/example/enabled" to a value * of %TRUE will cause the following to appear in the keyfile: * - * + * |[ * [toplevel] - * foo=true - * + * enabled=true + * ]| * * If @root_group is %NULL then it is not permitted to store keys * directly below the @root_path. @@ -602,13 +602,13 @@ dir_changed (GFileMonitor *monitor, * For keys not stored directly below @root_path (ie: in a sub-path), * the name of the subpath (with the final slash stripped) is used as * the name of the keyfile group. To continue the example, if - * were stored in "/apps/example/profiles/default/font-size" were set to + * "/apps/example/profiles/default/font-size" were set to * 12 then the following would appear in the keyfile: * - * + * |[ * [profiles/default] * font-size=12 - * + * ]| * * The backend will refuse writes (and return writability as being * %FALSE) for keys outside of @root_path and, in the event that @@ -616,6 +616,11 @@ dir_changed (GFileMonitor *monitor, * Writes will also be refused if the backend detects that it has the * inability to rewrite the keyfile (ie: the containing directory is not * writable). + * + * There is no checking done for your key namespace clashing with the + * syntax of the key file format. For example, if you have '[' or ']' + * characters in your path names or '=' in your key names you may be in + * trouble. **/ GSettingsBackend * g_keyfile_settings_backend_new (const gchar *filename,