On Sun, Oct 28, 2012 at 11:52:00AM +0100, Uli Schlachter wrote: > On 28.10.2012 11:14, Claudio Kozický wrote: > > On Sun, Oct 28, 2012 at 09:44:02AM +0100, Uli Schlachter wrote: > >> On 28.10.2012 09:19, Claudio Kozický wrote: > >>> I'm autorunning chromium and want the autorun window to be moved to tag > >>> 3. After the chromium window is moved to tag 3, all additionally opened > >>> chromium windows get moved to tag 3 as well (I don't want that). To > >>> solve the problem, I have to change chromium's instance after the > >>> autorun chromium gets moved to tag 3. > >> > >> So you autorun chromium and it starts up with instance "chromium-autorun", > >> right? And non-autorun chromiums have instance "chromium". At least the > >> rule > >> from your original mail suggests so. > >> > >> That means you can make a rule that just moves chromium-autorun to tag 3 > >> and > >> doesn't move other chromiums...? > > > > Yes I autorun chromium with instance set to "chromium-autorun". When I > > decide to open another chromium window on a tag different from tag 3, I > > execute "chromium" on that tag. But the problem is that when I execute > > "chromium", chromium opens a new window which inherits instance set to > > "chromium-autorun" and therefore gets moved from whatever tag I executed > > the "chromium" command to tag 3. > > Isn't it somehow possible to make chromium start a new process instead of > letting the already-running one handle the new page? :-/
I guess starting chromium with --temp-profile or another profile should do the trick, right? regards, Andre -- Andre Klärner
smime.p7s
Description: S/MIME cryptographic signature
