[xmonad] Layout.Gaps and PerScreen; is it going to happen?

Mikael Puhakka mr.progo at gmail.com
Sat Feb 20 11:46:51 EST 2010

I wanted to chime in and state that the issue isn't with xmonad at
all. Now that I had time, I checked out the xprop outputs and how
conky calculates it. With an older version of 1.80 it looks like a
design decision to define struts to "bottom" when user chooses to
place conky to "bottom right" corner.

Enough of offtopic, I wanted also to say that Xmonad really tickles my
needs. I honestly thought I couldn't move on from Fluxbox as I was
very customed to the traditional layered windowing with mildly useful
tabs along with it. Like in dwm, hardcoded settings  are something
magical and surprisingly handy.

-- Mikael

On Wed, Feb 17, 2010 at 17:59, Mikael Puhakka <mr.progo at gmail.com> wrote:
> Hello,
> I did manage to get Conky set its struts properly against the Google
> consensus (I was going to reply yesterday to say that Conky can't
> strut but they were all wrong;)
> However, apparently Conky sets a wrong kind of attributes to its strut:
> _NET_WM_STRUT_PARTIAL(CARDINAL) = 0, 0, 0, 201, 0, 0, 0, 0, 0, 0, 4032, 4239
> _NET_WM_STRUT(CARDINAL) = 0, 0, 0, 201
> Graphically presented, this picture represents a "Full" layout with a
> black terminal, red conky and white is unused background:
> http://havu.viuhka.fi/kuvat/xmonad_layout_struts.png
> I would very much like to have the unused strut space on the right
> side all the way to the top. This way Rainlendar could sneak in
> without strutting also.
> I just wonder if the issue here is caused by conky (the above WM_STRUT
> records indicate so, if I am reading it correctly) or avoidStruts. I
> did try the more specific avoidStrutsOn [R] but it didn't do anything
> besides the basic operations a plain "avoidStruts" does.
> Enlighten me, o mighty one.
> --Mikael
> On Mon, Feb 15, 2010 at 20:58,  <wagnerdm at seas.upenn.edu> wrote:
>> If conky and rainlendar set their struts properly, you should be able to get
>> by with manageDocks/avoidStruts. Documentation:
>> http://www.xmonad.org/xmonad-docs/xmonad-contrib/XMonad-Hooks-ManageDocks.html
>> ~d
>> Quoting Mikael Puhakka <mr.progo at gmail.com>:
>>> Dear Xmonad community,
>>> I've recently switched to Xmonad from a 3-year relationship with
>>> Fluxbox and just after 4-5 days of daily using I am beginning to love
>>> this thing very passionately.
>>> However, the old habits die hard and I don't even want to let go of
>>> every of them. Some vices of mine include a small Conky instance in a
>>> corner, a pseudo-transparent xterm tail -f :ing /var/log/messages with
>>> semi-hourly fortunes, and a Rainlendar the flashy calendar
>>> application.
>>> The "tail -f" monitor behind stuff in tiled environments such as this
>>> doesn't make much sense but I rather wouldn't part from the other two.
>>> Basically the subject says it all; I wonder if there is a working Gap
>>> modifier that would work on one screen only (I have currently a
>>> tri-head xinerama setup). I googled through the mailing lists and
>>> since 2008 there has been no fuzz about it.
>>> Am I left with a hack like a gapped layout to be used with one screen
>>> only, or is there a better solution for this? These applications don't
>>> do well with Layout.Monitor or alike. As a lazy workaround I've been
>>> using "Circle" layout for that particular screen and workspace (it's
>>> surprisingly handy and not just an eye toy).
>>> TIA,
>>> Mikael
>>> _______________________________________________
>>> xmonad mailing list
>>> xmonad at haskell.org
>>> http://www.haskell.org/mailman/listinfo/xmonad
>> _______________________________________________
>> xmonad mailing list
>> xmonad at haskell.org
>> http://www.haskell.org/mailman/listinfo/xmonad

More information about the xmonad mailing list