Re: [xmonad] Visual hints for XMonad actions

I'm trying to figure out why ShowWName doesn't use the dzen module to show the workspace name, what is the rule to use dzen instead of createNewWindow (for example) and why? On 12/27/2012 12:00 PM, xmonad-request@haskell.org wrote:
I wrote a patch for xmonad-contrib 0.10.1 to include an action to show some text in the centre of the screen. The patch is based on XMonad.Layout.ShowWName (thank you again Brandon Allbery) but it is an action and not a layout modifier. In this way it could be used to show some text when a key is pressed, for example. It includes an event handler to destroy the window after the timeout. Isn't this pretty much the exact use-case dzen was designed for? Just use spawn "dzen" manually, or, if you're into that kind of thing, try
Message: 2 Date: Wed, 26 Dec 2012 13:50:44 -0500 From: wagnerdm@seas.upenn.edu Subject: Re: [xmonad] Visual hints for XMonad actions To: xmonad@haskell.org Message-ID: <20121226135044.93047io82qmqzbic@webmail.seas.upenn.edu> Content-Type: text/plain; charset=ISO-8859-1; DelSp="Yes"; format="flowed" Quoting Mario Pastorelli
: the module X.U.Dzen[1]. ~d
[1] http://hackage.haskell.org/packages/archive/xmonad-contrib/0.10/doc/html/XMo...

On Thu, Dec 27, 2012 at 8:50 AM, Mario Pastorelli < pastorelli.mario@gmail.com> wrote:
I'm trying to figure out why ShowWName doesn't use the dzen module to show the workspace name, what is the rule to use dzen instead of createNewWindow (for example) and why?
Last I checked, dzen didn't have a way to remove itself after a timeout; if you want to do that, or you otherwise want to manipulate the window (say, update or remove and post a new one of the user immediately changes workspaces again), it's far easier to create it internally and pass the XID around than it is to try to find/save the XID via the ManageHook. Especially if you don't want the window to be managed otherwise. (Note that, for the same reason you can't tell apps to start on a specific workspace directly, you can't get an XID out of spawning an application; it isn't known until the window is created, and not identifiable as belonging to a particular application until the window is actually mapped, and the ManageHook will receive it at that point.) -- brandon s allbery kf8nh sine nomine associates allbery.b@gmail.com ballbery@sinenomine.net unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net

Quoting Brandon Allbery
Last I checked, dzen didn't have a way to remove itself after a timeout; if
dzen2 -p 10 for a ten-second timeout. I think the real reason ShowWName doesn't use dzen is to avoid having an external dependency, which seems pretty reasonable really. ~d

Note there's also xosd for this kind of task
http://hackage.haskell.org/package/xosd
Even a convenient wrapper:
http://hackage.haskell.org/package/printxosd
for use from xmonad.
On Thu, Dec 27, 2012 at 11:59 AM,
Quoting Brandon Allbery
: Last I checked, dzen didn't have a way to remove itself after a timeout; if
dzen2 -p 10 for a ten-second timeout. I think the real reason ShowWName doesn't use dzen is to avoid having an external dependency, which seems pretty reasonable really.
~d
_______________________________________________ xmonad mailing list xmonad@haskell.org http://www.haskell.org/mailman/listinfo/xmonad
participants (4)
-
Brandon Allbery
-
Don Stewart
-
Mario Pastorelli
-
wagnerdm@seas.upenn.edu