Re: [gentoo-user] Re: How to set size to windows in Openbox in local config WAS: Something eats my memory

[Miroslav Rovis]

On 170413-06:14+0200, Floyd Anderson wrote:
> After rereading my previous reply to your response, two things catching
> my eyes. Firstly I have forgotten to mentioned a neatly urxvt extension
> [1] (for an on the fly font size changing) in the terminal font related
> paragraph of my prior post.
I do have the package:

x11-misc/urxvt-font-size

installed, and enabled. It is enabled via the line further below, and
it is the case since more than one year ago (I did it, at the latest,
around the time these files were last modified, so to recall all of
this, and to write this message took me some time :-) ):

$ ls -ABRgo ~miro/_Xresources_*fonts
-rw-r--r-- 1 641 2016-03-07 23:04 /home/miro/_Xresources_fonts
-rw-r--r-- 1 238 2016-03-12 14:34 /home/miro/_Xresources_no_fonts
$

But I'll attach my commented current ~/.config/openbox/autostart to give
an example of a simple config to even casual readers who will be finding
this via search engines. Pls. find attached:

autostart_2017-04-13_miroR.txt

( floyd, the explanation is for potential readers who are less advanced
than even me, just skim through it; or if you prefer, do correct it if
there's anything wrong, or where it, or my explanation here, is
incomplete )

This line, in the attached file autostart_2017-04-13_miroR.txt, arranges
for font resizing:

xrdb ~miro/_Xresources_no_fonts

xrdb just loads resources, from its manual page: 
       xrdb - X server resource database utility

And this is what gets the fonts resized on the fly:

$ cat ~miro/_Xresources_no_fonts
   URxvt.perl-ext-common: font-size
   URxvt.keysym.C-Up:     perl:font-size:increase
   URxvt.keysym.C-Down:   perl:font-size:decrease
   URxvt.keysym.C-S-Up:   perl:font-size:incglobal
   URxvt.keysym.C-S-Down: perl:font-size:decglobal

( C is the Ctrl key, Up and Down are the arrow keys, don't know what S
stands for, I've actually been using only the C-Up and C-Down. But the
x11-misc/urxvt-font-size package is just two files, the 300+ lines perl
script and the README, read there once you install the package... )

I attached autostart_2017-04-13_miroR.txt because finally the
positioning and sizing of urxvt (and other windows) I am able to do,
from my spartan-austere-simple, no-frills-whatsoever Openbox desktop,
and I like to offer the solutions that worked for me to other potential
readers!

It could even get improved soon, if, from the other message of floyd's
(more time I need to digest and to reply to that other message, which is
actually previous to this one of his that I am replying to) I figure out
how to get the urxvt windows to start with just just 1 pixel borders and
no GUI title and bottom bars...

It could even get improved. Could. But it it won't, this is already a
huge improvement with respect to what I was living with for... years. At
every starting of desktop, manually arranging the positioning and sizes
of windows...

That's why I'm sharing it, to help other users of lean and mean desktops
without bloat. Remember I'm on a non-dbus system, so I am somewhat of a
DIYer in a way (although more and more people prefer no-bloat, so also
no-dbus and no-poetterware installs, and it is now much easier for users
than when I converted my system to such).

What now follows is the explanation of the current state of my urxvt
terminal windows with respect to their positions being or not lost while
resizing them. Which is another issue to resolve, with, hopefully,
floyd's patch.

So, while the positioning of windows usually remains the same for very
simple resizing; simply C-Up to increase the font, and later C-Down to
decrease it back to the previous size returns the window to the exact
same position as previously in all respects, that is no longer the case
when more than one or two steps, such as two consecutive C-Up are
performed, and later two consecutive C-Down: the window does not return
to where it originally was, but moves away, usually upwards.

Previously, up until several months ago (just 2-3? or maybe 8-9?, I
don't recollect well at all), the window would move away even after one
single C-Up followed by one single C-Down. And as I described above,
that undesired move-away no longer happens, but it no longer happens
only for one step C-Up and one step C-Down. Which means somebody has
already tried, and with limited success, to fix the restoring of the
positions of windows upon these increases and decreases :-) .

So yes:
> I have made a little patch to keep the window position while resizing
> the font. I you are interested in, let me know.
I am interested about your patch! I hope it won't be complex, the
patching...

> Secondly, and even more important, my last paragraph:
> >>Can I tell you more? […]
> >>
> >>And, given the above... How come I couldn't figure out the syntax can
> >>only be similar for positioning as it is for
> >>cropping/compositing/resizing the images, I can not tell, other than
> >>being myself terribly unimaginative...
> >This is the point I mentioned above somewhere. If you acquire your
> >experience by yourself, you mostly can see parallelism to other things
> >you have learned in the past. Copy here and copy there, consume this and
> >consume that (without thinking, just for a quick success), doesn’t make
> >those things happen.
> has some potential to get me wrong. Please, do not refer it to yourself
> as my assumption why you have not figure out the syntax of the geometry
> switch. Naturally this happens all the time — to me too. And as you say,
> often someone cannot say why nor what is going on behind the scene.
No, c'mon. I won't get you wrong. I may be sensitive, but not that much
;-) 

> For a recent example, as I looked for the above mentioned extension, I
> realised that the local script has some changes against the origin one
> but I was unable to remember who has made this. At the end I must say
> nobody else than me might have done this but I really do not recall it.
I'm not sure I get what you mean by 'local script'? Does 'local' mean:
gentoo repo?

> To finish this second topic, my intention was only to pointing out what
> can happen not *what* happened and had been better placed at my prior
> community related statement.
All is fine.

This is where the two-files, very useful x11-misc/urxvt-font-size
package is developed:
> [1] <https://github.com/majutsushi/urxvt-font-size>
>
> --
> Regards,
> floyd

I need more time to digest you previous email.

Regards!
-- 
Miroslav Rovis
Zagreb, Croatia
https://www.CroatiaFidelis.hr