After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 712692 - server: Add a mechanism to make it persistent
server: Add a mechanism to make it persistent
Status: RESOLVED WONTFIX
Product: gnome-terminal
Classification: Core
Component: general
git master
Other All
: Normal normal
: ---
Assigned To: GNOME Terminal Maintainers
GNOME Terminal Maintainers
Depends on:
Blocks:
 
 
Reported: 2013-11-19 16:00 UTC by Debarshi Ray
Modified: 2014-01-27 14:30 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
server: Add a mechanism to make it persistent (1.09 KB, patch)
2013-11-19 16:02 UTC, Debarshi Ray 		rejected Details | Review

Description Debarshi Ray 2013-11-19 16:00:40 UTC 
Unless there are some clients connected to it, the server quits immediately when it becomes idle. This is a good thing. However, sometimes, usually during development, it is convenient to be able to turn this off. eg., empathy, telepathy and gnome-online-miners use *_PERSIST environment variables to disable this.

Since gnome-terminal already uses command line arguments for such development options maybe we can use them instead.
Comment 1 Debarshi Ray 2013-11-19 16:02:48 UTC 
Created attachment 260257 [details] [review]
server: Add a mechanism to make it persistent
Comment 2 Christian Persch 2013-11-19 20:56:16 UTC 
How about an option for setting g_application_set_inactivity_timeout() instead, would that work for your usecase?
Comment 3 Debarshi Ray 2013-11-20 13:00:00 UTC 
(In reply to comment #2)
> How about an option for setting g_application_set_inactivity_timeout() instead,
> would that work for your usecase?

That would not let us add an infinite timeout, because I want to control the lifetime of the server by hitting Ctrl+C and restarting it whenever needed.

However, I don't really have a strong opinion on this. I can live with locally adding the persistence as some kind of throw away debug code when I need to.
Comment 4 Debarshi Ray 2014-01-27 14:29:54 UTC 
Given that GApplication waits up to 10 seconds for the first activation message to arrive, this isn't that big a problem in practice. With time I have learnt that I do not really need an infinite timeout.