-
-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FvwmRearrange -tile -r -mn 3 -maximize 0 0 #1107
Comments
Read the manual page, the options and behavior of FvwmRearrange has been drastically changed. The single letter options no longer exist. |
|
The issue is |
Testing with default config, doesn't work. Manpage examples, only |
Are you saying there's something in the default config which references Again, you need to take into account the changes made to |
The default config is fine. I am testing the different FvwmRearrange examples in the manpage. |
OK. When you actually have something which might be an issue, let us know. Until then, please try and not muddy the waters. |
The issue is that option |
But it has always been that way, @rasatpc -- that's not anything new. They're mutually-exclusive. |
It worked fine until recent updates. I have been using option |
The wiki has not been updated, use the man page. What do you mean the option '-tile' does not work, in my tests it does what it is designed to do. |
I tried many options mentioned in the FvwmRearrange manpage. Some work, others not. Here is the list:
Option |
You have not clarified what doesn't work is doing. Also you should search the manual page better, Of course |
I copied your spelling error. :) With the correction, everything works fine. Also, I found the option |
Ahh sorry, silly me. |
fvwm3 --version
)fvwm3 1.1.1 (1.1.0-120-g3e0d960d)
Behaviour
Tile windows into columns and rows.
FvwmRearrange -tile -r -mn 3 -maximize 0 0 86 82
Does not work when numbers are added to maximize. Without numbers, it places all windows into columns without rows.
FvwmRearrange -tile -r -mn 3 -maximize
The text was updated successfully, but these errors were encountered: