Workspace-specific guake

[kikecalpe]

Workspace-specific guake http://guake.org/ticket/543 Reported by: PietroB Owned by: somebody Priority: major Milestone: 0.5.0 Component: guake Version: 0.4.4 Keywords: Cc: me@… Description

I just discovered guake, and I felt in love with it: it's nice and fast (and well documented Python code too!).

But I have another love: workspaces. And it clearly makes no sense that the same shell which I just used to batch rename some songs in my "Free time" workspace comes out in my "University" workspace. I want another one.

Please put an option so that guake can be ran as workspace-specific.

This requires two steps: - guake should not run on all workspaces - when re-run, it should trigger via dbus the existing instance only if it's in the same workspace

Actually, I'm willing to try to produce a patch. But I feel very stupid: looking at guake's code (and glade file!), I wasn't able to understand how it sets its presence on all workscreens.

An alternative, maybe nicer, is that the instance is single, but guake shows different terminals depending on the workspace. Nicer, but probably harder (at least, I would have to dig more in guakes' internals).

[kikecalpe]

Changed by PietroB

cc me@… added

(I did find how to set presence on all workscreens - "stick()". Still interested in knowing if the nicer design - a single instance, workspace-dependent tabs - seems plausible.)

Changed by PietroB

OK, here: https://github.com/toobaz/guake/commits/master I introduced workspaces-dependence (in a single instance - in fact, it wasn't that hard).

It is currently impossible to switch it on/off, so consider it just as a proof of concept: if you don't dislike the approach, I'll proceed to: - create (and use) a preferences item to switch on/off - also remember the shown/not shown state on a per-workspace basis (currently if you hide/show on workspace 1 you will find it hidden/shown on workspace 2)

Please let me know if you're interested.

[kikecalpe]

Related -> http://guake.org/ticket/30

[toobaz]

Just for clarity: this bug has nothing to do with that one, though I do refer to it in reply to one particular comment: http://guake.org/ticket/30#comment:5

(my bad for having supported that ticket hijacking with my comment!)

Concerning the issue of workspaces, I have ported my patch to the Gtk3 version, I'm currently testing it and I will soon polish it and push it in my repo.

[gsemet]

triage. Good feature, but post 0.6.0

[cikaRadule]

Hi, guys what has happened with this feature request? Seems it's dead in the water for more than two years now. :/ I could try to pick it up, but can't seem to find any current work on this issue...

[gsemet]

no found time to work on it. Would be part of next rework of guake with gtk3, but it does not have advanced that much sadly :(

[toobaz]

I have been using my version modified with workspaces until recently, but it diverged since long, not sure when I'll find the time to rebase. Anyway, it still had some bugs (apart from the fact that the functionality could not be switched on/off).

[cikaRadule]

Is there any chance I can take a look at your work, at least to try to make it run on my machine? And if possible to try to see if it can be prepared for some future releases...

[gsemet]

work has not much advanced... there are two attempt on (guake3 and gtk3 branches). But you can rebase on master and submit a pull request on the current version

[toobaz]

@cikaRadule see #820

[cikaRadule]

@toobaz thanks, I'll take a look and hopefully manage to make some progress. I'll leave status update here....

[AlexWayfer]

Any updates? :sweat:

[candoz]

I want to believe

[gsemet]

I unplan this feature, no time to work on it. I am open to pull request for some that wants to dig it :)

[helix84]

See also: #604 (could help back this feature)