Most motif widgets will scale according to font size. When using Xft fonts, set the Xft.dpi resource to 160 or whatever suits best. Scrollbar size may be adjusted with *XmScrollBar.width (for vertical) and *XmScrollBar.height (for horizontal) X resources. Other widgets that require manual size adjustment are: *XmPaned.sashWidth/sashHeight, *XmPanedWindow.sashWidth/sashHeight and *XmArrowButton.width/height.
EMWM desktop icon size can be adjusted with the Emwm*iconImageMaximum
If window resizing rubber-bands look too thin, specify a larger value in pixels with the Emwm*outlineWidth X resource. Window border widths may be adjusted with Emwm*resizeBorderWidth for resizable windows, and Emwm*frameBorderWidth for fixed size windows.
Since Motif 2.3 Xft fonts can be specified with render tables.
You can add named renditions to render tables and assign them
to widgets and/or widget classes.
Say you want to define a 10pt, bold, italic, sans rendition and call it "sans_10p":
*renderTable.sans_10p.fontName: Liberation Sans
*renderTable.sans_10p.fontStyle: Bold Italic
Then assign it to Motif widget class or name:
Or to all widgets:
There are more properties you can set; see XmRendition(3).
Note: It is technically possible to build the Motif toolkit without Xft support. So if the above doesn't do anything, such could be the reason.
Some applications will place their windows on screen, rather that letting the WM do it, if this is not desired EMWM can be configured to ignore program specified position with Emwm*class†*usePPosition: off. Setting the usePPosition to on will make EMWM always use program specified position, default is nonzero which means window positions other than 0,0 will be accepted.
Default window decorations and functions can also be overridden by setting Emwm*class†*clientFunctions and Emwm*class†*clientDecoration resources.
† The application window's class string can be retrieved with: $ xprop | grep "WM_CLASS" (then click on application window).
Note that xmsession is just a shell script that sets up the environment for xmsm (merging X resources, sourcing ~/.Xprofile etc.), hence it's only needed if this hasn't been done yet.
1. Execing xmsm from ~/.Xsession should work on most platforms.
2. If you prefer a clean environment with XDM, you can specify xmsession directly in xdm-config using the DisplayManager*session X resource
3. See FreeBSD Handbook on XDM and OpenBSD FAQ on this topic. Debian Linux will run /usr/bin/x-session-manager, which you can symlink xmsm to (Source: Debian WIKI).
You can create an .app-defaults subdirectory in $HOME and then export XAPPLRESDIR="$HOME/.app-defaults" environment variable (in .Xprofile, or whatever sets up your environment), then copy per-application defaults from (usr/local)/etc/X11/app-defaults over there for customization. This also keeps them out of the screen database, and there is no need to run xrdb after making changes.
I've been using MWM for a long time, because it did all I needed a WM to do. EMWM grew out of a couple of patches I created to make MWM work properly with recent software and X extensions, and hadn't published until Motif was LGPLed. My personal goal is just to keep it usable.
That said, I have nothing against extra configuration options so people can get it to work just the way they want, but that's pretty much it. If you need more functionality and/or customizability, you're probably looking for FVWM.
MWM had it all along, and the code is still there, albeit currently disabled, because it is implemented on top of Sun's IPC. The old code can be eventually repurposed for an EWMH based implementation. Then again, while it was a desirable feature when all you had was a 14" CRT with 800x600 pixel resolution, with screen space available nowadays I personally don't care for it at all.
Back to EMWM Homepage