1. 20 Sep, 2017 2 commits
  2. 10 Aug, 2017 1 commit
  3. 11 Jun, 2017 3 commits
  4. 06 Jun, 2017 2 commits
  5. 30 May, 2017 1 commit
  6. 29 May, 2017 2 commits
  7. 17 Jan, 2016 1 commit
  8. 28 Aug, 2015 1 commit
  9. 18 May, 2015 1 commit
  10. 17 Sep, 2014 1 commit
  11. 10 Sep, 2013 1 commit
  12. 04 Sep, 2013 1 commit
    • Alex Muñoz's avatar
      Improve search results · 4bcfa7aa
      Alex Muñoz authored
      * When using tweaks where we have defined our own
        name and descriptions also consider the gsettings
        schema summary and description if present.
      
      * Include gsettings enum values in those tweaks
      4bcfa7aa
  13. 28 Aug, 2013 1 commit
  14. 24 Aug, 2013 1 commit
  15. 21 Aug, 2013 4 commits
  16. 18 Aug, 2013 11 commits
  17. 17 Jul, 2013 3 commits
  18. 13 Jul, 2013 1 commit
  19. 07 Jun, 2013 1 commit
    • Florian Müllner's avatar
      Generalize support for shell's schema overrides · 559b222e
      Florian Müllner authored
      GNOME Shell overrides some settings to use different default values
      than standalone mutter. With the introduction of classic mode, things
      got a little more complicated, as some of the overrides were reverted
      again by extensions - to support either mode, we needed to pick the
      right schema for all affected settings.
      The shell has now introduced mode-specific overrides, and classic mode
      started to use that instead of extensions; this means we will now need
      to adapt all settings that *both* normal and classic mode override.
      However rather than adjusting the affected settings, the new approach
      allows us to generalize the support for schema overrides depending on
      the current mode - this should allow us to handle future changes to
      overrides in either normal or classic mode automatically.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=701760
      559b222e
  20. 06 Dec, 2012 1 commit