Index | Thread | Search

From:
izder456 <izder456@disroot.org>
Subject:
Re: NEW: x11/emwm
To:
ports@openbsd.org
Date:
Sat, 3 Feb 2024 21:13:09 -0600

Download raw body.

Thread
  • Omar Polo:

    NEW: x11/emwm

    • Christian Weisgerber:

      NEW: x11/emwm

      • izder456:

        NEW: x11/emwm

On Sat, 3 Feb 2024 22:14:36 +0100
Christian Weisgerber <naddy@mips.inka.de> wrote:

> Omar Polo:
> 
> > Here's an updated tarball with a few more tweaks on top:
> > 
> >  - use DIST_TUPLE instead of GH_* (takes less lines :-)
> >  - don't need to patch the makefile; just override the variables
> > using MAKE_FLAGS and FAKE_FLAGS
> >  - use tabs for indenting the values  
> 
> I've been wanting to look at this for months, well before the port
> was submitted here, but I can never find the time, so just some
> quick remarks:
> 
> If it uses the 1.1 release anyway, it should just use the release
> tarball
> https://fastestcode.org/dl/emwm-src-1.1.tar.xz
> instead of GitHub.
> 
> This is advertised as an mwm fork "without changing the way the
> window manager looks and behaves".  Well, it _looks_ different,
> even after neutering app-defaults/Emwm.  What's up with that?  Also,
> aren't those app-defaults intended as an example, rather than actual
> defaults?
> 
> Resizing xterm is a crapshoot, because their is a size mismatch
> between emwm and xterm.  A default 80x24 xterm is "81x26" or some
> such.  This is a showstopper, IMO.  I don't know whether it also
> affects pixel-dimensioned windows.
> 
> On the plus side, it interops better with Firefox in at least two
> regards:
> * Maximizing the Firefox window correctly maximizes it.
>   (With mwm its extended to twice the screen height/width.)
> * The PiP window can be moved.
> 

I also found this plays better with multiple X11 heads. 

On smaller screens, this isn't an issue but on larger screens IIRC,
around 720p and up, the vetical/horizonal maximize and fullscreen
maximize is broken. Emwm seems to also fix this. The default Xterm size
is gross. that is yucky. you should check my x11/emwm-utils port too,
this is probably the killer feature that this project provides IMHO. 

I should use the tarball from fastestcode.org, thats a good idea,
thanks.

It looks like upstream had a point release bump to 1.2 as of the 28th.

I fixed that too.

It is attached.

I plan to reply to the thread for my x11/emwm-utils port with the
version bumped and the above suggestions.

Thoughts?

-- 
----
-iz