On 27/03/2008, Eben King <[EMAIL PROTECTED]> wrote:
> On Thu, 27 Mar 2008, Thomas Adam wrote:
>  > Next (Firefox-bin) MoveToPage
>
> Thanks.  What kind of a statement is that, something that I'd feed to
>  FvwmTalk?  How would I specify _which_ Firefox-bin window I want moved?

You could use FvwmTalk, although I'd use FvwmConsole, personally.

It says:  "Take the next window in the window-ring, whose class (in
this case) is Firefox-bin, and perform the command MoveToPage."

>  Right now, there are 37, and having all of them in the same place would
>  kinda suck.

Well, you can either match the specific one based on the exact title,
or if you wanted select ones, "tag" them all by giving the windows a
State, a la:

State 1

(That's from within FvwmConsole, by the way).   Then you can do:

All (State 1) MoveToPage ...

> There shouldn't be.  TTBOMK, the only Style lines in there adjust window
>  appearance, WindowListSkip, that sort of thing.

"TTBOMK" doesn't cut it, I'm afraid.  You could always check your FVWM config.

>  When FF starts up, it restores all open windows from when it went down.  It
>  looks like it puts them in specific places, but I don't know what those
>  places are.

Well, this is where:

BugOpts ExplainWindowPlacement

Comes in handy.  When you next launch FF, FVWM will spit out where/why
a window was placed to (typically) ~/.xsession-errors -- although this
location depends on how you have X11 setup.

-- Thomas Adam

Reply via email to