1. 19 Jul, 2013 1 commit
  2. 04 Apr, 2013 1 commit
  3. 09 Mar, 2013 1 commit
  4. 15 Nov, 2012 1 commit
  5. 16 Oct, 2012 1 commit
  6. 28 Aug, 2012 1 commit
  7. 02 Feb, 2012 1 commit
  8. 20 Jan, 2012 1 commit
    • Matthias Clasen's avatar
      Fix a refcounting error · 8852d4e9
      Matthias Clasen authored
      'new' is created floating, therefore it is consumed by
      g_settings_set, and unreffing it after that call is not right.
      8852d4e9
  9. 19 Dec, 2011 1 commit
  10. 07 Jun, 2011 1 commit
  11. 23 May, 2011 1 commit
  12. 18 May, 2011 1 commit
  13. 17 May, 2011 1 commit
  14. 12 Apr, 2011 2 commits
  15. 09 Apr, 2011 1 commit
  16. 23 Feb, 2011 1 commit
    • Matthias Clasen's avatar
      Allow to list keys in all schemas · 766d7072
      Matthias Clasen authored
      Make the schema argument to gsettings list-recursively optional.
      This allows to search for not exactly known keys by going
      
      gsettings list-recursively | grep 'font'
      766d7072
  17. 12 Feb, 2011 1 commit
  18. 21 Jan, 2011 1 commit
  19. 12 Dec, 2010 1 commit
  20. 01 Nov, 2010 1 commit
  21. 30 Oct, 2010 3 commits
  22. 04 Oct, 2010 2 commits
  23. 03 Oct, 2010 1 commit
    • Allison Karlitskaya's avatar
      gsettings-tool: Rewrite · 2d6f8a8e
      Allison Karlitskaya authored
      Rewrite the GSettings tool.
      
      Improvements/changes:
      
       - simplify the code by performing common actions (like creating a
         schema) in only one place instead of one per-command
      
       - new features (list schemas, list keys, monitor multiple, etc)
      
       - factor-out bash completion and implement in shellscript
      
       - input validation: should never abort due to invalid inputs
      
      Still to do:
      
       - proper error checking for ranges/choices
      
       - support for querying range/choice information
      
       - bash completion support for enums
      
      Closes bug #629289, possibly among others.
      2d6f8a8e
  24. 22 Sep, 2010 1 commit
  25. 09 Sep, 2010 1 commit
  26. 22 Jul, 2010 1 commit
  27. 30 Jun, 2010 1 commit
  28. 27 Jun, 2010 3 commits
  29. 19 Jun, 2010 2 commits
    • Milan Bouchet-Valat's avatar
      Fix gsettings tool crash, part 2 · a558e460
      Milan Bouchet-Valat authored
      Same as previous commit, but for two other functions it missed.
      a558e460
    • Milan Bouchet-Valat's avatar
      Fix gsettings tool crash · 62939f5e
      Milan Bouchet-Valat authored
      When no path is provided for the schema, we have call
      g_settings_new() instead of g_settings_new_with_path()
      passing a NULL path.
      
      This was crashing the tool on start since an assertion was
      recently added to g_settings_new_with_path() to refuse NULL.
      62939f5e
  30. 17 Jun, 2010 1 commit
  31. 11 Jun, 2010 1 commit
  32. 24 May, 2010 1 commit
    • Allison Karlitskaya's avatar
      GDBusConnection.call(): add 'reply_type' argument · 3160bcad
      Allison Karlitskaya authored
      This allows the caller to specify the reply type that they are expecting
      for this call.  If the reply comes back with the wrong type, GDBus will
      generate an appropriate error internally.
      
        - add a GVariantType * argument to g_dbus_connection_call() and
          _call_sync().
      
        - move the internal API for computing message types from introspection
          data to be based on GVariantType instead of strings.  Update users
          of this code.
      
        - have GDBusProxy pass this calculated GVariantType into
          g_dbus_connection_call().  Remove the checks done in GDBusProxy.
      
        - Update other users of the code (test cases, gdbus-tool, GSettings
          tool, etc).  In some cases, remove redundant checks; in some other
          cases, we are fixing bugs because no checking was done where it
          should have been.
      
      Closes bug #619391.
      3160bcad
  33. 17 May, 2010 1 commit
    • Allison Karlitskaya's avatar
      GSettings tool: work-around GDBus issue · 849684e5
      Allison Karlitskaya authored
      There is currently no way (near as I can tell) to ensure that a message
      has been sent when using GDBus.  If we exit() before we are sure, then
      it is very possible that the message isn't sent at all.  This behaviour
      was observed when using the GSettings commandline tool with dconf.
      
      A quick and dirty workaround for now.
      849684e5