GNOME Bugzilla – Bug 661768
[auto-move-windows] activate workspace after window was moved to it
Last modified: 2017-11-25 02:17:42 UTC
It makes sense to activate workspace after window was moved to it, and it looks convenient to me
Created attachment 199010 [details] [review] Patch to implement subj feature
I saw this patch in the mail, and I didn't reply immediately because I'm not convinced this is the right behavior. Yes, if you're launching an app, and you like on a specific workspace, it makes sense to activate it. But in that case, you can just use standard shell facilities (drag and drop). On the other hand, I believe auto-move-windows, beside preventing auto collection of workspaces, is designed for fixed workflows where you start apps from a terminal and want them out of sight immediately, or you start multiple apps using scripts, or you resume a saved session. In none of those cases it makes sense to me to activate a specific workspace (among many).
I usually use alt+f2 to launch apps, and I like to see app on necessary workspace when it's ready. Anyway, I'm OK with refusing to take this patch upstream, I can patch extension on my PCs easily :P Thanks for review ;)
(In reply to comment #2) > I saw this patch in the mail, and I didn't reply immediately because I'm not > convinced this is the right behavior. I was actually the one that mailed you about that. I'll attached my patch (very similar to Vasily's, except for the fact that I've made the feature configurable). > Yes, if you're launching an app, and you like on a specific workspace, it makes > sense to activate it. But in that case, you can just use standard shell > facilities (drag and drop). > On the other hand, I believe auto-move-windows, beside preventing auto > collection of workspaces, is designed for fixed workflows where you start apps > from a terminal and want them out of sight immediately, or you start multiple > apps using scripts, or you resume a saved session. In none of those cases it > makes sense to me to activate a specific workspace (among many). I see where you're coming from when it comes to the whole workflow thing. However, the way I have been using it is to actually force a workflow (i.e.: my browser gets moved to its own workspace, so it doesn't interfere with whatever I'm doing on the main workspace). But, once again, I can see why people wouldn't want this functionality, which is exactly why I thought it'd be better if it's configurable.
Created attachment 200062 [details] [review] Same functionality + configurability
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gnome-shell-extensions/issues/1.