I have
Style *Chromium* StartsOnDesk 4
Style *chromium* StartsOnDesk 4
(and I have tried other incantations) to get chromium to start on my desk #4. However, it starts in whatever desk it wants to, which is a bit of aa nuisance.
Is there anyone who can
(a) tell me the right way to do this, or
(b) suggest what sin(s) I might be committing in my config, or
(c) ask some probing questions to work through the issue?
Thanks very much.
Perhaps try:
Style *Chromium* !UsePPosition, StartsOnDesk 4
Note that, for the style name to match, you can use FvwmIdent to determine the class name of the window.
Thanks for the suggestion. I used those two Style lines because FvwmIdent says the Class is Chromium and the Resource is chromium. But, as I mentioned, neither were working for me.
Tragically, that suggestion did not work. Any other suggestions?
Curiously, after adding
Style *Chromium* !UsePPosition, StartsOnPage 5
Style *chromium* !UsePPosition, StartsOnPage 5
I restarted chromium a number of times. First, it started on Page (desk) 3. Then next time page 2. Then next time page 1. Then page 0. Apparently chromium gets around.
No other program (for which I have a StartsOnDesk config entry) wanders around like that.
This is my AutoMoveWindow script (single monitor).
## Automatically move applications to specific desk/page
## when they create windows.
#
## APPS COMMAND DESK/PAGE LOCATION
## ---------------------------------------------------------
Style Chromium StartsOnPage 0 0 0 # desk 0
Style *Chrome StartsOnPage 0 1 0 # desk 0
Style *Firefox StartsOnPage 0 1 0 # desk 0
Style Telegram StartsOnPage 0 1 0 # desk 0
Style Evolution StartsOnPage 1 0 0 # desk 1
Style "Mozilla Thunderbird" StartsOnPage 1 1 0 # desk 1
Style Gimp StartsOnPage 2 0 0 # desk 2
Style scribus StartsOnPage 2 1 0 # desk 2
Style GitHub* StartsOnPage 2 1 0 # desk 2
Rasat, thanks. Copying your Style line does indeed make chromium windows go where i want them… after chromium is already running. Unfortunately, even with that in my config, when I start up Chromium the initial window(s) go on whatever desk they want.
If this works for you, it might indicate I have some poltergeist in my fvwm3, which would be sort of weird.
No… this just means you have something in your configuration which is order-specific.
Can you put your entire fvwm config somewhere, please?
Hi Thomas. I have put a tar file (oops, typed ,gz instead of .gz) at
https://file.io/ZILnpVxWE4Ws
It supposedly expires in two weeks.
I removed many menu entries which should be immaterial, but the order of reading of files and the Styles I set up should all be intact.
Thanks.
The file is deleted.
Hmmmm… anyone here willing to suggest a reliable, useful, free file transfer service?
File io site says the file gets deleted after download if no expiry time. Someone may have downloaded it. Upload again and add a time.
Simply upload a file, share the link, and after it is downloaded, the file is completely deleted. For added security, set an expiration on the file and it is deleted within a certain amount of time, even if it was never downloaded.
I set the expiry time to 2 weeks last time.
Here is the next one…
Also set to 2 weeks. But maybe it will vanish upon the first download too.
It is deleted after first download. Luckily, I was the one. I uploaded it on my server. Download from this link.
Anyone have a chance to try this config out and see how chromium behaves?
I just tested and the style lines work fine. Can you share the info from FvwmIdent for your chromium window?
Looking through your config I notice some cleanup you should do. PipeRead echo is doing nothing except causing fvwm to have to deal with an empty input to discard. I would remove all lines that do that.
Note by default fvwm uses layers 0 though 6, you are starting things on much higher layers. Probably not needed but should update DefaultLayers bottom put top to match. Also the style should be Layer 0 N instead of just Layer N.
For seeing the window placement info, the command is BugOpts ExplainWindowPlacement True, that should give you info about window placement to see what fvwm is doing when it places the windows.
Once test you can do is move your configuration out of the way (so ~/.fvwm/config doesn’t exist), then use the default-config. Open up FvwmConsole or FvwmPrompt, set the style line for chromium and see if it works there. If it does work there, that means your config has some conflict.
The Class is “Chromium” and the Resource is “chromium”.
Do you need other pieces of info from the FvwmIdent ? (If so, is there some easy way to get that output into a text file?)
somiaj: thanks for the comments. At some point I was trying to get some actions in a function done in a predictable order, and (at the time) doing the piperead helped. That was a long time ago, to the point I don’t remember the specific problem.
Abuot the DefaultLayers… I have some programs that I want to be really, really on top (even above “StaysOnTop” windows), and so I have assigned them numbers bigger than the top layer. Things work how I want this way. (Perhaps they would if I put the highest layer I use as the third argument, but if two windows with the same layer overlap, I’m not sure why the one I want to be “really, really on top”) would be on top.
Thanks for noting my mistake with “Layer”.
Unfortunately, even when I fix the BugOpts line, I don’t see any output when the chromium windows are initially opened (nor if I move them manually). (By “the console”, I am assuming it means fvwm’s stdout or stderr, and whereever those might have been redirected to. If it means /dev/console, that is a bit more of a problem.)
Thanks for the suggestion of bailing on my config entirely. I was hoping to avoid that, but it may be the way to go.
Do you mind telling me which version of chromium you are using, and what distro you are using?
It is less about what we have setup (works for us), but more about you. Share the output of FvwmIdent on your chromium window. There is something about your setup causing issues. Did you try with the default-config?