On Thu, Jan 29, 2015 at 2:04 PM, Erick Pérez Castellanos
eric...@gnome.org wrote:
My idea was to have them (the app, which provides search at the same
time) running all the time in the background, but that feels like
using the resources of the CPU without the user knowing
That is what GNOME
On Thu, 2015-01-29 at 10:03 +0100, Jens Georg wrote:
There’s a bit of discussion going on at the DX hackfest about personal
branches of other people’s modules.
People here agree that it would be pretty good if we standardised on:
wip/$nick/$branch_name
as the name for your
Hey,
I'm wondering if there are distros/platforms that are planning on
using 3.16 and ConsoleKit together.
I know there's LoginKit, systemd-shim and systembsd now that try to
provide logind compatible interfaces for non-systemd systems, so I'd
really like to get rid of the ConsoleKit code in
On Fri, Jan 30, 2015 at 02:25:20PM -0500, Ray Strode wrote:
Hey,
I'm wondering if there are distros/platforms that are planning on
using 3.16 and ConsoleKit together.
I know there's LoginKit, systemd-shim and systembsd now that try to
provide logind compatible interfaces for non-systemd
Hi:
You could get the best of both worlds by doing what gnome-documents
does (ie. use an inactivity-timeout):
https://git.gnome.org/browse/gnome-documents/tree/src/application.js#n133
That way, your process does not linger for ever, but it stays around
long enough to cache a quick series of
On Fri, 2015-01-30 at 09:43 -0500, Erick Pérez Castellanos wrote:
You could get the best of both worlds by doing what gnome-documents
does (ie. use an inactivity-timeout):
https://git.gnome.org/browse/gnome-documents/tree/src/application.js#n133
That way, your process does not linger for
