-
Notifications
You must be signed in to change notification settings - Fork 10
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
Allow user configuration to set geometry defaults #71
Comments
Thanks for your report and suggestion. Configurable default geometry values seem reasonable to me, I should be able to put that in in the upcoming days (assuming I don't hit an unexpected difficulty). Do you use the debian or arch linux package (in which case I know I should also trigger the packaging). I'm wondering though why/where things go wrong for you, so I have a few followup questions:
|
I am using the arch aur package (both
|
Sorry for the delay despite my promise to only take a few days. I just remembered that shellex inherits settings from rxvt and rxvt has a default geometry. Does adding something like the following to
(note that's in characters of the desired window, not in pixels of the monitor). If not, I just pushed the branch size-defaults to my fork https://github.com/pseyfert/shellex/tree/size-defaults (the configuration is then Something else I'm wondering, when starting shellex from a shell, there's some debug output, for me something like:
And for the monitor size determination shellex just calls |
When using shellex (in this case with bspwm), there is the possibility that shellex does not find the display dimensions. In this case, setting shellex to appear on the bottom edge puts it in an inaccurate position, with no way (That I am able to see) to change this behavior short of compiling from source with manual edits done to the defaults defined here.
This could presumably be resolved by optionally reading these defaults from
.Xresources
in the same way thatedge
andpos
are.The text was updated successfully, but these errors were encountered: