That would be dwm for me, although I do run awesome from time to time.

Yes, that's a must with some windows. Some windows/programs are best run in a floating mode (eg. notifications, small programs or anything that would in other windows managers be classified as a 'pop-up' window.)

I am not using any tiling windowmanager. Only WindowMaker (with the fsviewer filemanager) or CDE.
Some 10 years ago, I was using fvwm or olvwm (OpenWindows). I regret a bit that olvwm is not anymore in Slackware,
but I guess that it was not anymore compatible with modern X servers. Personally, I don't see why Slackware
should by default install another windowmanager besides twm,mwm,fvwm,WindowMaker and Blackbox. Anyway, if a tiling windowmanager is added to Slackware, I would prefer to have it in extra/ so that it can be installed from pkgtool if needed after the main installation. Ideally, it should not depend on more libraries than twm or fvwm, not take a lot of disk space, and not consume a lot of memory when running. In that way, it will be useful on machines with a minimal X installation (servers) or low memory where a full KDE/GNOME is not an option.

I used to be a KDE fan but after giving i3 a try I haven't looked back. On desktop and laptop. As mentioned before, it is easy enough to build, and since I want to stay up to date with the latest features it does not have to be included in Slackware.

However, I think at least one tiling wm should be included in Slackware to make them more accessible to Slackers.

I like my overlapping windows including focus-follows-mouse and manually z-ordering. I don't use the "Maximize" option of my window manager.

For those who miss a status bar with the datetime, spectrwm can leave a narrow band of pixels free for the root window. It will then run a command every x seconds and write the output to that band in the font you choose.

I run a straight-forward dash script to display a fairly comprehensive status bar with datetime, cpu use, memory use, battery charge, disk space, weather, moon phase, and ISP quota use.

I got introduced to i3 via this thread, and it's now my main WM.

why there is no ion3/notion?

dwm for me.

I like the idea of including a tiling WM in Slackware, but it would make sense if it was one that could be easily customised at runtime via a file (i.e. not dwm) and didn't have any extra dependencies.

My tiling window managers are KDE and XFCE.

I just install x-tile (available from SlackBuilds.org).

there are omitted many other tiling wms (stumpwm, herbsluftwm, wmii, notion etc). i simply did chosen most known ones or some i've personal experience with.

great once one discovers simplicity and effectiveness of tiling concept there is no way back. however it does presume computer is used more for work then playing

Hi, we had at least two polls about tiling-WMs here in the Slackware-forum last year.

I'm using Xmonad, but had to switch to i3 now because Xmonad didn't build anymore on current after I've tried to upgrade all the installed packages from slackbuilds.org on my system ;-) That's the disadvantage when on runs current and stable and current differ too much.

It would be nice to have at least one tiling-WM in Slackware, but which one? Xmonad is very good, but it has too much dependencies and is configured with Haskell. i3 is easy to configure, but I would say there are more different configurations than users. Which configuration should be the default for Slackware?
I've noticed your point that they use the keyboard slightly different than the vi-editor. But it was no problem to solve this.
I agree that many Slackware-users use tiling-WMs but as you also noted there are about 50 or more tiling-WMs available. And those who use one are those who don't have any problems to build it for their system.

Markus

i3 defaults are quite sane so it could be a good starting point (well with the exception of urxvt which is not installed by default on Slackware. That's fixed in i3.SlackBuild). Furthermore, the initial run of i3 welcomes you with a key binding wizard.

From Slackware 14.1 onwards (or the current -current branch), we will be able to enjoy i3 with its full vanilla functionality including pango support.

The only potential "problems" I see with i3 being bundled with Slackware are:

a) dependencies: libev, yajl, dmenu
If we consider i3status as well, 'confuse' will have to be added to the list. These are small packages but still it'll mean a total of 6 additional packages being included with Slackware.

b) i3lock - requires PAM.

dmenu is optional, although somebody may find it more comfortable then launching from xterm/rxvt
i3lock is relatively superfluous as xscreensaver can serve as well.