Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #170648 > unrolled thread

Chromium jumps to any workspace it likes.......

Back to article view | Back to linux.debian.user

Contents

  Chromium jumps to any workspace it likes....... Charlie <ariestao1@ipstarmail.com.au> - 2016-08-03 03:20 +0200
    Re: Chromium jumps to any workspace it likes....... Lisi Reisz <lisi.reisz@gmail.com> - 2016-08-03 11:00 +0200
      Re: Chromium jumps to any workspace it likes....... Charlie <ariestao1@ipstarmail.com.au> - 2016-08-03 15:20 +0200
        Re: Chromium jumps to any workspace it likes....... Reco <recoverym4n@gmail.com> - 2016-08-03 17:50 +0200
          Re: Chromium jumps to any workspace it likes....... Charlie <ariestao1@ipstarmail.com.au> - 2016-08-04 01:00 +0200
        Re: Re: Chromium jumps to any workspace it likes....... Rodary Jacques <rodaryj@free.fr> - 2016-08-12 00:20 +0200
          Re: Chromium jumps to any workspace it likes....... Charlie <ariestao1@ipstarmail.com.au> - 2016-08-12 01:30 +0200
            Re: Chromium jumps to any workspace it likes....... Curt <curty@free.fr> - 2016-08-12 16:50 +0200
            Re: Chromium jumps to any workspace it likes....... Lisi Reisz <lisi.reisz@gmail.com> - 2016-08-12 17:40 +0200
              Re: Chromium jumps to any workspace it likes....... Charlie <ariestao1@ipstarmail.com.au> - 2016-08-13 01:30 +0200
      Re: Chromium jumps to any workspace it likes....... Glenn English <ghe@slsware.net> - 2016-08-03 22:10 +0200
        Re: Chromium jumps to any workspace it likes....... Lisi Reisz <lisi.reisz@gmail.com> - 2016-08-03 23:20 +0200
        Re: Re: Chromium jumps to any workspace it likes....... Rodary Jacques <rodaryj@free.fr> - 2016-08-12 01:40 +0200
          Re: Chromium jumps to any workspace it likes....... Lisi Reisz <lisi.reisz@gmail.com> - 2016-08-12 17:40 +0200
    Re: Chromium jumps to any workspace it likes....... David Wright <deblis@lionunicorn.co.uk> - 2016-08-03 16:00 +0200
      Re: Chromium jumps to any workspace it likes....... Lisi Reisz <lisi.reisz@gmail.com> - 2016-08-03 16:40 +0200
        Re: Chromium jumps to any workspace it likes....... David Wright <deblis@lionunicorn.co.uk> - 2016-08-03 22:00 +0200
          Re: Chromium jumps to any workspace it likes....... Lisi Reisz <lisi.reisz@gmail.com> - 2016-08-03 23:10 +0200
            Re: Chromium jumps to any workspace it likes....... David Wright <deblis@lionunicorn.co.uk> - 2016-08-04 04:30 +0200
              Re: Chromium jumps to any workspace it likes....... Lisi Reisz <lisi.reisz@gmail.com> - 2016-08-04 10:00 +0200
                Re: Chromium jumps to any workspace it likes....... Charlie <ariestao1@ipstarmail.com.au> - 2016-08-04 15:00 +0200
                  Re: Chromium jumps to any workspace it likes....... John Hasler <jhasler@newsguy.com> - 2016-08-04 17:50 +0200
                Re: Chromium jumps to any workspace it likes....... John Hasler <jhasler@newsguy.com> - 2016-08-04 17:10 +0200
          Re: Chromium jumps to any workspace it likes....... John Hasler <jhasler@newsguy.com> - 2016-08-04 14:40 +0200
            Re: Chromium jumps to any workspace it likes....... Charlie <ariestao1@ipstarmail.com.au> - 2016-08-04 15:10 +0200
              Re: Chromium jumps to any workspace it likes....... Lisi Reisz <lisi.reisz@gmail.com> - 2016-08-04 15:50 +0200
                Re: Chromium jumps to any workspace it likes....... Gene Heskett <gheskett@shentel.net> - 2016-08-04 16:50 +0200
                Re: Chromium jumps to any workspace it likes....... John Hasler <jhasler@newsguy.com> - 2016-08-04 17:30 +0200
                  Re: Chromium jumps to any workspace it likes....... Lisi Reisz <lisi.reisz@gmail.com> - 2016-08-04 17:50 +0200
                    Re: Chromium jumps to any workspace it likes....... John Hasler <jhasler@newsguy.com> - 2016-08-04 18:20 +0200
                      Re: Chromium jumps to any workspace it likes....... Lisi Reisz <lisi.reisz@gmail.com> - 2016-08-04 18:40 +0200
                        Re: Chromium jumps to any workspace it likes....... David Wright <deblis@lionunicorn.co.uk> - 2016-08-04 20:10 +0200
                          Re: Chromium jumps to any workspace it likes....... Lisi Reisz <lisi.reisz@gmail.com> - 2016-08-04 20:40 +0200
                            Re: Chromium jumps to any workspace it likes....... rhkramer@gmail.com - 2016-08-04 22:10 +0200
                              Re: Chromium jumps to any workspace it likes....... Lisi Reisz <lisi.reisz@gmail.com> - 2016-08-04 23:30 +0200
                            Re: Chromium jumps to any workspace it likes....... David Wright <deblis@lionunicorn.co.uk> - 2016-08-05 22:30 +0200
                        Re: Chromium jumps to any workspace it likes....... rhkramer@gmail.com - 2016-08-04 22:00 +0200
                          Re: Chromium jumps to any workspace it likes....... Lisi Reisz <lisi.reisz@gmail.com> - 2016-08-04 23:30 +0200
                  Re: Chromium jumps to any workspace it likes....... "Thomas Schmitt" <scdbackup@gmx.net> - 2016-08-04 18:20 +0200
                    Re: Chromium jumps to any workspace it likes....... Lisi Reisz <lisi.reisz@gmail.com> - 2016-08-04 18:40 +0200
            Re: Chromium jumps to any workspace it likes....... Charlie <ariestao1@ipstarmail.com.au> - 2016-08-04 15:20 +0200
              Re: Chromium jumps to any workspace it likes....... John Hasler <jhasler@newsguy.com> - 2016-08-04 17:40 +0200
              Re: Chromium jumps to any workspace it likes....... David Wright <deblis@lionunicorn.co.uk> - 2016-08-04 20:00 +0200
                Re: Chromium jumps to any workspace it likes....... Charlie <ariestao1@ipstarmail.com.au> - 2016-08-06 01:40 +0200
                  Re: Chromium jumps to any workspace it likes....... David Wright <deblis@lionunicorn.co.uk> - 2016-08-14 04:20 +0200
                    Re: Chromium jumps to any workspace it likes....... Charlie <ariestao1@ipstarmail.com.au> - 2016-08-14 04:50 +0200

Page 1 of 3  [1] 2 3  Next page →

#170648 — Chromium jumps to any workspace it likes.......

	
	From my keyboard:
   
	Debian testing 4.6.0-1-amd64
	Using FVWM
	Chromium - Version 52.0.2743.82 built on Debian stretch/sid,
running on Debian stretch/sid (64-bit)

Move onto the workspace on which Chromium is to open and try to do
so, and Chromium opens, but selects it's own workspace to open on?

Have read about this, or similar, on the web but can't find a
workaround to stop this happening.

Has anyone discovered this problem and found a way to stop this
happening? Please share. It would be appreciated.

Thank you,
Charlie

	East Gippsland Wildlife Rehabilitators Inc..
	           http://www.egwildlife.com.au/

-- 
	Registered Linux User:- 329524
	***********************************************

	There are two things to aim at in life: first, to get what you
	want; and after that to enjoy it. Only the wisest of mankind
	achieve the second. ....................Logan Pearsall Smith

	***********************************************

	Debian GNU/Linux - Magic indeed.

	-----------------------------------------------------

[toc] | [next] | [standalone]

#170652

On Wednesday 03 August 2016 02:10:46 Charlie wrote:
> Has anyone discovered this problem and found a way to stop this
> happening? Please share.

Can only offer fellow-feeling.  Most annoying.  It is of recent arrival here 
(Debian Jessie, 8.5, Google Chrome 52.0.2743.82 (64-bit)), and although I 
have found a pattern - first window opened opens in workspace in which it was 
last running, second (and subsequent) window(s) opened separately open(s) in 
workspace selected - I have not found how to avoid it.  I fear that it is 
another Google "feature".

I suspect it may have something to do with the arrival of workspaces in 
Windows 10.

Lisi

[toc] | [prev] | [next] | [standalone]

#170653

On Wed, 3 Aug 2016 09:56:25 +0100 Lisi Reisz sent:

> On Wednesday 03 August 2016 02:10:46 Charlie wrote:
> > Has anyone discovered this problem and found a way to stop this
> > happening? Please share.  
> 
> Can only offer fellow-feeling.  Most annoying.  It is of recent
> arrival here (Debian Jessie, 8.5, Google Chrome 52.0.2743.82
> (64-bit)), and although I have found a pattern - first window opened
> opens in workspace in which it was last running, second (and
> subsequent) window(s) opened separately open(s) in workspace selected
> - I have not found how to avoid it.  I fear that it is another Google
> "feature".
> 
> I suspect it may have something to do with the arrival of workspaces
> in Windows 10.
> 
> Lisi

	After contemplation, my reply is:

Sorry to read that your system is similarly afflicted. After a reboot
Chromuim settled down here. Chromium has been really good for so long.
But that could just be famous last words.

I only use it and Iceweasel, but now with the Iceweasel/Firefox
transition, which also has become a liability. Epiphany is my new
browser of choice in place of firefox-esr because of these bugs:


grave bugs of firefox-esr (→ 45.2.0esr-1) <Outstanding>
 
b1 - #828159 - firefox-esr: session tabs lost after upgrade from
iceweasel to firefox-esr serious bugs of firefox-esr (→ 45.2.0esr-1)
<Outstanding>

b2 - #827395 - firefox-esr: Firefox-esr privacy invading
defaults load beacons on 1st run serious bugs of firefox-esr (→
45.2.0esr-1) <Forwarded>

b3 - #822715 - firefox-esr: FTBFS with GCC 6:
'malloc' was not declared in this scope

So will leave it without installing again for a while.

Not a huge inconvenience. Just thought an answer might be out there.

Stay well,
Charlie
-- 
	Registered Linux User:- 329524
	***********************************************

	No object is mysterious. The mystery is in your eye.
	--Elizabeth Bowen

	***********************************************

	Debian GNU/Linux - Magic indeed.

	-----------------------------------------------------

[toc] | [prev] | [next] | [standalone]

#170659

	Hi.

On Wed, 3 Aug 2016 23:18:40 +1000
Charlie <ariestao1@ipstarmail.com.au> wrote:

> I only use it and Iceweasel, but now with the Iceweasel/Firefox
> transition, which also has become a liability. Epiphany is my new
> browser of choice in place of firefox-esr because of these bugs:
> 
<...> 
> b3 - #822715 - firefox-esr: FTBFS with GCC 6:
> 'malloc' was not declared in this scope

I'm really curious. How exactly the fact that firefox cannot be built
using gcc-6 affects you?


And returning to your original question - have you tried using
devilspie to pin Chromuim window to a single workspace?

Reco

[toc] | [prev] | [next] | [standalone]

#170669

On Wed, 3 Aug 2016 18:42:38 +0300 Reco sent:

> 	Hi.
> 
> On Wed, 3 Aug 2016 23:18:40 +1000
> Charlie <ariestao1@ipstarmail.com.au> wrote:
> 
> > I only use it and Iceweasel, but now with the Iceweasel/Firefox
> > transition, which also has become a liability. Epiphany is my new
> > browser of choice in place of firefox-esr because of these bugs:
> >   
> <...> 
> > b3 - #822715 - firefox-esr: FTBFS with GCC 6:
> > 'malloc' was not declared in this scope  
> 
> I'm really curious. How exactly the fact that firefox cannot be built
> using gcc-6 affects you?

I don't use firefox now.
 
> And returning to your original question - have you tried using
> devilspie to pin Chromuim window to a single workspace?


	After contemplation, my reply is:

Thank you for pointing out devils pie, but I will have to read a bit to
get to learn how to drive it.

Thank you for that.
Charlie

-- 
	Registered Linux User:- 329524
	***********************************************

	Use, do not abuse; neither abstinence nor excess ever renders
	man happy. .....Voltaire

	***********************************************

	Debian GNU/Linux - Magic indeed.

	-----------------------------------------------------

[toc] | [prev] | [next] | [standalone]

#170999

[Multipart message — attachments visible in raw view] — view raw

Did I already told you about Opera 
:-D)

[toc] | [prev] | [next] | [standalone]

#171003

On Fri, 12 Aug 2016 00:00:01 +0200 Rodary Jacques sent:

> Did I already told you about Opera 
> :-D)


	After contemplation, my reply is:

I did consider it. However its **not** a browser supported by Debian.

Lisi said that Chromium is probably behaving the way it is because
Windows now uses different viewpoints or desktops or workspaces [I
wouldn't know which].

However I didn't think that Chromium, though the source for Chrome, was
still mimicking that browser. I thought Chromium stood aloof from
Chrome. I also wasn't aware that Chromium is available for windows?

But I digress.

Bottom line:

I **try** [operative word] as much as possible to stay with Debian
supported packages.

But thanks for the suggestion.
Charlie

-- 
	Registered Linux User:- 329524
	***********************************************

	However mean your life is, meet it and live it; do not shun it
	and call it hard names. It is not so bad as you are. It looks
	poorest when you are the richest. -Henry David Thoreau

	***********************************************

	Debian GNU/Linux - Magic indeed.

	-----------------------------------------------------

[toc] | [prev] | [next] | [standalone]

#171031

On 2016-08-11, Charlie <ariestao1@ipstarmail.com.au> wrote:
>
> Bottom line:
>
> I **try** [operative word] as much as possible to stay with Debian
> supported packages.

That's the spirit.

I have Chrome (now an outdated version) on this Wheezy machine running
Gnome 3 (with workspaces) and do not experience the gratuitous jumping
you describe.

I haven't really been following the thread so maybe my data point is
irrelevant.

> But thanks for the suggestion.
> Charlie
>


-- 
Même l’avenir n’est plus ce qu’il était. 
Paul Valéry  

[toc] | [prev] | [next] | [standalone]

#171039

On Friday 12 August 2016 00:24:37 Charlie wrote:
> Lisi said that Chromium is probably behaving the way it is because
> Windows now uses different viewpoints or desktops or workspaces [I
> wouldn't know which].

They call them desktops!!!  Your "workspaces" was perfectly comprehensible, 
and the general point of language is to be understood.  A guess, purely - and 
a barely serious one at that.  But it is quite possible, even likely, in view 
of the coincidence of timing.

> However I didn't think that Chromium, though the source for Chrome, was
> still mimicking that browser.

It doesn't mimic it.  It is it.  Both are Google.  Chrome is the closed source 
proprietary one.  Chromium the open source one, but it is still Google and 
gets most of its stuff from Chrome.  As you say, Debian then packages 
Chromium, which is a big argument in favour of Chromium.  I *think* that it 
is Chrome that is the source for Chromium, and not the other way round, but I 
am not sure.

Lisi

[toc] | [prev] | [next] | [standalone]

#171051

On Fri, 12 Aug 2016 16:34:26 +0100 Lisi Reisz sent:

> It doesn't mimic it.  It is it.  Both are Google.  Chrome is the
> closed source proprietary one.  Chromium the open source one, but it
> is still Google and gets most of its stuff from Chrome.  As you say,
> Debian then packages Chromium, which is a big argument in favour of
> Chromium.  I *think* that it is Chrome that is the source for
> Chromium, and not the other way round, but I am not sure.

	After contemplation, my reply is:

Thanks for that information Lisi. I was obviously on the wrong track,
had it all wrong way round. Not that unusual as I have assumed and
it's obviously made an ass of me. But what you write explains some
things.

Be well,
Charlie

-- 
	Registered Linux User:- 329524
	***********************************************

	He who knows others is wise; He who know himself is
	enlightened. -Lao-tzu

	***********************************************

	Debian GNU/Linux - Magic indeed.

	-----------------------------------------------------

[toc] | [prev] | [next] | [standalone]

#170664

> On Aug 3, 2016, at 2:56 AM, Lisi Reisz <lisi.reisz@gmail.com> wrote:
> 
> On Wednesday 03 August 2016 02:10:46 Charlie wrote:
>> Has anyone discovered this problem and found a way to stop this
>> happening? Please share.
> 
> Can only offer fellow-feeling.  Most annoying.  It is of recent arrival here 
> (Debian Jessie, 8.5, Google Chrome 52.0.2743.82 (64-bit)), and although I 
> have found a pattern - first window opened opens in workspace in which it was 
> last running, second (and subsequent) window(s) opened separately open(s) in 
> workspace selected - I have not found how to avoid it.  I fear that it is 
> another Google "feature".
> 
> I suspect it may have something to do with the arrival of workspaces in 
> Windows 10.

Nope. The most recent Mac OS does the same thing. 

Sounds to me like a conspiracy of systems programmers all over the globe :-)

-- 
Glenn English

[toc] | [prev] | [next] | [standalone]

#170666

On Wednesday 03 August 2016 21:03:52 Glenn English wrote:
> > I suspect it may have something to do with the arrival of workspaces in
> > Windows 10.
>
> Nope. The most recent Mac OS does the same thing.

It isn't the OS we are complaining about.  It is Chromium/Google and its new 
habit, which I still think may have been invented by Google to suit what they 
imagine Windows 10 users would like, however many Os's have multiple desktops 
these days.  (Multiple desktops/workspaces depends, in fact, anyhow in Linux, 
on the DE/windows manager, not the OS.)

Lisi

[toc] | [prev] | [next] | [standalone]

#171005

 As far as I remember, it has nothing to do with the OS, nor with the browser 
or the desktop manager but with the windows manager. In 1999 (perhaps 2000) 
when Gnome was to be loaded carefully one package at a time,  NextStep or 
Nautilus windows manager (I can't remember which, perhaps a third one) 
introduced fixed workspaces, as many as 64 possible ( it was really great to 
open 64 pictures in GIMP), and (later?) the possibility to choose a workspace 
for a given application, e.g workspace 2 for the default browser, 3 for the 
mail, etc... In 2006 (perhaps before) this was introduced in MacOs under the 
name of Spaces, also fixed. Then, in MacOS and Linux (which was first?) 
worspaces became dynamic, i.e created as needed, and then couldn't be assigned 
to a given application; it seems nevertheless that an application tries to go 
to its later place.
	Happily enough, I never tried Windows (besides me, a poster says "This is 
an air conditioned room, don't open Windows®".

[toc] | [prev] | [next] | [standalone]

#171037

On Friday 12 August 2016 00:22:50 Rodary Jacques wrote:
>  As far as I remember, it has nothing to do with the OS, nor with the
> browser or the desktop manager but with the windows manager. In 1999
> (perhaps 2000) when Gnome was to be loaded carefully one package at a time,
>  NextStep or Nautilus windows manager (I can't remember which, perhaps a
> third one) introduced fixed workspaces, as many as 64 possible ( it was
> really great to open 64 pictures in GIMP), and (later?) the possibility to
> choose a workspace for a given application, e.g workspace 2 for the default
> browser, 3 for the mail, etc... In 2006 (perhaps before) this was
> introduced in MacOs under the name of Spaces, also fixed. Then, in MacOS
> and Linux (which was first?) worspaces became dynamic, i.e created as
> needed, and then couldn't be assigned to a given application; it seems
> nevertheless that an application tries to go to its later place.

In general, one can certainly assign to a given desktop, and as many separate 
windows on that desktop as one wishes.  But it does depend on the OS and 
DE/Window Manager.  You may be right that it depends primarily on which 
Window Manager is being used by the OS/DE.

> 	Happily enough, I never tried Windows (besides me, a poster says "This is
> an air conditioned room, don't open Windows®".

:-))  Nor I Windows 10 - but I have had to read some of its claims!!  Great 
poster!!!

Lisi

[toc] | [prev] | [next] | [standalone]

#170654

On Wed 03 Aug 2016 at 11:10:46 (+1000), Charlie wrote:
> 	
> 	From my keyboard:
>    
> 	Debian testing 4.6.0-1-amd64
> 	Using FVWM
> 	Chromium - Version 52.0.2743.82 built on Debian stretch/sid,
> running on Debian stretch/sid (64-bit)
> 
> Move onto the workspace on which Chromium is to open and try to do
> so, and Chromium opens, but selects it's own workspace to open on?
> 
> Have read about this, or similar, on the web but can't find a
> workaround to stop this happening.
> 
> Has anyone discovered this problem and found a way to stop this
> happening? Please share. It would be appreciated.

I'm not familiar with the term "workspace" in this context, especially
after reading Lisi's comment. Could you elaborate: does it apply to
the window manager or chromium?

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#170656

On Wednesday 03 August 2016 14:52:38 David Wright wrote:
> On Wed 03 Aug 2016 at 11:10:46 (+1000), Charlie wrote:
> > 	From my keyboard:
> >
> > 	Debian testing 4.6.0-1-amd64
> > 	Using FVWM
> > 	Chromium - Version 52.0.2743.82 built on Debian stretch/sid,
> > running on Debian stretch/sid (64-bit)
> >
> > Move onto the workspace on which Chromium is to open and try to do
> > so, and Chromium opens, but selects it's own workspace to open on?
> >
> > Have read about this, or similar, on the web but can't find a
> > workaround to stop this happening.
> >
> > Has anyone discovered this problem and found a way to stop this
> > happening? Please share. It would be appreciated.
>
> I'm not familiar with the term "workspace" in this context, especially
> after reading Lisi's comment. Could you elaborate: does it apply to
> the window manager or chromium?
>
> Cheers,
> David.

The desktop environment.  More often traditionally called "desktops" than 
workspaces.  It is a way of grouping things.

Please everyone, don't lets have a flamewar about terminology.  (Not aimed at 
you, David - but someone is bound to want to disagree. :-(  )

Lisi

Lisi

[toc] | [prev] | [next] | [standalone]

#170663

On Wed 03 Aug 2016 at 15:36:19 (+0100), Lisi Reisz wrote:
> On Wednesday 03 August 2016 14:52:38 David Wright wrote:
> > On Wed 03 Aug 2016 at 11:10:46 (+1000), Charlie wrote:
> > > 	From my keyboard:
> > >
> > > 	Debian testing 4.6.0-1-amd64
> > > 	Using FVWM
> > > 	Chromium - Version 52.0.2743.82 built on Debian stretch/sid,
> > > running on Debian stretch/sid (64-bit)
> > >
> > > Move onto the workspace on which Chromium is to open and try to do
> > > so, and Chromium opens, but selects it's own workspace to open on?
> > >
> > > Have read about this, or similar, on the web but can't find a
> > > workaround to stop this happening.
> > >
> > > Has anyone discovered this problem and found a way to stop this
> > > happening? Please share. It would be appreciated.
> >
> > I'm not familiar with the term "workspace" in this context, especially
> > after reading Lisi's comment. Could you elaborate: does it apply to
> > the window manager or chromium?
> >
> > Cheers,
> > David.
> 
> The desktop environment.  More often traditionally called "desktops" than 
> workspaces.  It is a way of grouping things.
> 
> Please everyone, don't lets have a flamewar about terminology.  (Not aimed at 
> you, David - but someone is bound to want to disagree. :-(  )

I just wanted to save some breath if the problem is of the sort
treated firstly here.

Anyway, if it's workspace in the sense of the one mention of
"workspace" in   man fvwm   ie desktop, then I can't be of any help.
I ran two desktops on two screens/graphics cards in fvwm for many
years and the boundary between them was impermeable.

OTOH if we're talking about viewports on one desktop, then yes, I do
have a problem where one of the Skype windows maps outside the entire
set of viewports, ie right off the desktop. I can get to it with the
Window Menu (Ctrl-rightButton presently, configurable) which brings
it into view.

I discovered in the past that I could achieve the same with a
FvwmButton if I found out the window title of the window concerned,
'my-skype-name - Skype*', then set up a button like

*MyButtons: (2x1+0+0, Title 'the label', Action MyBit)

and a function which includes the line

+ I All ('my...*') PipeRead '/bin/cat ${HOME}/.fvwm/move-skype'

where ${HOME}/.fvwm/move-skype contains, say

AnimatedMove 10p 10p

so that when you press the button, the windows races to the position
given, in the current viewport.

I use it when I start X to place various windows like digital clock,
analogue clock, sound mixer, xmms, Skype etc. Putting the coordinates
into files means you can dynamically compute them in .xsession using
the current screen resolution. The button is swallowed in the Pager
along with various scrot and video capture buttons.

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#170665

On Wednesday 03 August 2016 20:50:05 David Wright wrote:
> Anyway, if it's workspace in the sense of the one mention of
> "workspace" in   man fvwm   ie desktop, then I can't be of any help.

Thanks, David.  I don't think that anyone can be of any help.  I think one 
just has to curse and live with it!  After it has opened where it wants to 
open, I mouse-drag it to where I want it.  Easy, but mildly irritating.

Lisi

[toc] | [prev] | [next] | [standalone]

#170671

On Wed 03 Aug 2016 at 22:08:16 (+0100), Lisi Reisz wrote:
> On Wednesday 03 August 2016 20:50:05 David Wright wrote:
> > Anyway, if it's workspace in the sense of the one mention of
> > "workspace" in   man fvwm   ie desktop, then I can't be of any help.
> 
> Thanks, David.  I don't think that anyone can be of any help.  I think one 
> just has to curse and live with it!  After it has opened where it wants to 
> open, I mouse-drag it to where I want it.  Easy, but mildly irritating.

The OP said they use fvwm which exhibits the behaviour I described.
If you can drag the window from where it popped up to where you want
it, then it was on the correct *desktop*.

If it pops up on the wrong viewport, you've got to navigate to the
correct one and then either make it sticky and switch back, or drag it
viewport by viewport to the correct one.

Looking at the commented lines in my .xsession files, I see that
fvwm desktops correspond with the X server's $DISPLAYs, so
$ xterm -display :0.1
will map it to a different Desktop from :0 (or :0.0).

fvwm viewports can be addressed in xterm using X resources, so
$ xterm -xrm "*Page: 1 3"
will map it to the 4th row down and 2nd to the right, and switch
to that viewport.
They can also be addressed by using the geometry, so
$ xterm -geometry +2000+100
will map the xterm in the next viewport to the right if the
x-resolution is less than 2000. In this case, the viewport doesn't
switch: the window maps off the screen instead.

I have no idea how any of the browsers decide where and how large to
map their window. I don't think it could be as simple as -geometry;
unlike xterm, simplicity is just not their style.

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#170675

On Thursday 04 August 2016 03:21:20 David Wright wrote:
> The OP said they use fvwm which exhibits the behaviour I described.
> If you can drag the window from where it popped up to where you want
> it, then it was on the correct *desktop*.

No, it wasn't.   I said and meant "desktop", otherwise known as workspace.  If 
you say that the OP, who uses FVWM, said workspace and meant viewport, I 
cannot argue, since you obviously know FVWM, and I don't.

Lisi

[toc] | [prev] | [next] | [standalone]

Page 1 of 3  [1] 2 3  Next page →

Back to top | Article view | linux.debian.user

csiph-web