Spencer Janssen | 1 Apr 01:23 2009
Picon

Re: Segfault

On Tue, Mar 31, 2009 at 07:50:29AM +0100, Jim Burton wrote:
> Hi, I'm using xmonad 0.8.1, GHC 6.10, Ubuntu intrepid, and every now and
> then I get an X error immediately after logging in and am bounced back to
> the login screen. Logging in again normally works fine. Here is
> .xsession-errors from one of those occasions:
> 
> /etc/gdm/Xsession: Beginning session setup...
> Setting IM through im-switch for locale=en_GB.
> Start IM through /etc/X11/xinit/xinput.d/all_ALL linked to
> /etc/X11/xinit/xinput.d/default.
> /home/jim/.xsession: line 9:  5756 Segmentation fault      $CABAL_BIN/xmonad
> 
> ###############
> 
> And here is my .xinitrc:
> 
> #!/usr/bin/env bash
> xsetroot -cursor_name top_left_arrow -solid gray30
> CABAL_BIN=/home/jim/.cabal/bin
> $CABAL_BIN/xmobar &
> gnome-settings-daemon &
> numlockx on &
> unclutter &
> 
> $CABAL_BIN/xmonad
> 
> ################
> 
> The line .xsession-errors refers to is the last one, which launches
> xmonad. What's going on?
(Continue reading)

Jim Burton | 1 Apr 09:57 2009

Re: Segfault

At Tue, 31 Mar 2009 18:23:49 -0500,
Spencer Janssen wrote:
>
> On Tue, Mar 31, 2009 at 07:50:29AM +0100, Jim Burton wrote:
> > Hi, I'm using xmonad 0.8.1, GHC 6.10, Ubuntu intrepid, and every now and
> > then I get an X error immediately after logging in and am bounced back to
> > the login screen. Logging in again normally works fine. Here is
> > .xsession-errors from one of those occasions:
> >
[snip]
> > The line .xsession-errors refers to is the last one, which launches
> > xmonad. What's going on?
> >
> > Thanks,
> >
> >
> > --
> > Jim Burton
>
> We need information to see what is going on.  The most likely problem is a
> miscompiled xmonad, try cleaning, rebuilding, and reinstalling xmonad and
> contrib.  Finally, execute "xmonad --recompile".
>

Thanks for your reply. I already rebuilt but will try xmonad
--recompile.

> If the problem persists, try to get a stack trace.
>

(Continue reading)

Roman Cheplyaka | 1 Apr 11:52 2009

Re: Property vs Query Bool

* Adam Vogt <vogt.adam@...> [2009-03-30 20:10:05-0400]
> * On Monday, March 30 2009, Konstantin Sobolev wrote:
> 
> >Hello
> >
> >I'm trying to implement my own LayoutClass which mixes the ideas of IM
> >and CombineTwo. It has to contain some predicate as a part of it's
> >state, which will tell where to put new windows.
> >As I see IM uses WindowProperties for this purpose, but I wouldn't
> >like to use it for 2 reasons:
> >1. Property essentially duplicates Query Bool.
> >2. Property isn't flexible enough. For instance, I can't match a
> >window by title substring, while I can easily do it with Query.
> >However, there's one problem (and I guess that's why Property was
> >introduced): Query doesn't derive Read and Show, and as far as I
> >understand it's not so easy to implement them.
> >So what should I use, Query Bool with empty (Read, Show)
> 
> Another way to pass a function (that is not changed by running the layout), 
> is to use a typeclass:
> 
> > class IsAQuery a where
> >   query :: a -> Query Bool
> 
> > data Dummy = Dummy deriving (Read,Show)
> 
> > instance IsAQuery Dummy where
> >   query _ = do
> >     ..... query stuff
> 
(Continue reading)

Kendall Shaw | 1 Apr 19:46 2009

Re: Swing and keyboard

I think the problem I experienced is a result of setting AWT_TOOLKIT=MToolkit. I noticed that I get the same
non-working keyboard in whatever KDE's window manager is. Unsetting that environment variable, I have
not had the non-working keyboard in xmonad so far.

So, I first set AWT_TOOLKIT which fixed the grey window problem. Then I tried setting setWMName to LG3D in
EwmhDesktops.hs, but left AWT_TOOLKIT set, which seems to cause the non-working keyboard problem.

Kendall
Konstantin Sobolev | 3 Apr 23:00 2009
Picon

one more layout

Hello,

Could somebody review my attempt to write a layout and tell if it's
worth including in contrib?

Inventively named ComboP, it mostly acts as CombineTwo, but also takes
a predicate which controls new windows placement.
For instance

withIM (1%7) (ClassName "Tkabber") Grid

is roughly imitated by

combineTwoP (TwoPane 0.1 (1/7)) (Tall 0 0.1 (1/2)) Grid (ClassName "Tkabber")

Also, a few notes/questions from an XMonad newcomer:

- I see a lot of flickering when switching workspaces or tabs in
Tabbed. Looks like root image is shown first,
and then windows paint on top of it. It's very noticeable, especially
when some windows are slow to redraw.

- ResizableTile doesn't work correctly when placed into some
combinator which feeds only a subset of windows
to it(?). For instance try this:

windowNavigation $ combineTwo (dragPane Vertical 0.1 (1/2)) t t
    where t= ResizableTall 0 (1/100) (1/2) []

put 4 windows into resulting 2*2 grid and try to send Shring/Expand
(Continue reading)

Ismael Carnales | 5 Apr 03:38 2009
Picon

Opinions (skip if you are busy)

Hi, I was bothering some people on IRC and someone suggested me to
send my opinions in an email, so here it goes:

To clarify things: I love Xmonad, I admire much of it's simplicity in
some ways and complexity in others (taling about code) but I think it
fails in one main thing: communication.

I'm relatively new to Xmonad and totally new to haskell, but when some
of my co-workers show me Xmonad I fell in love with it at the moment,
and I tried to learn everything I could about it. So I reviewed the
hole contrib documentation.

What was my first thinking? No screenshots of the results of the usage
of the module (only the withIM LayoutModifier had one, my preferred
contrib), overlapping and difficult to understand functionality and
some real gems that make your day-to-day life with Xmonad worh it.

I'm really amazed of how some really experienced Xmonad users are
recently discovering UrgencyHook, I myself had encounter recently
ShellPrompt and replaced dmenu for good. What was the difficult thing?
finding them, and understanding their intended usage. UrgencyHook can
tell you about Pidgin messages, Mutt mails, IRSSI messages, everything
(unluckly it depends on extenal programs) and it's poor documented.

When I found smart borders I thought: "why isn't it the default
behaiviour for all layouts and make me explicitely add it", also found
that perworkspace makes Xmonad so much powerfull that I think it
should be a main feature selecting the layouts to apply to a
workspace. Even Tabbing is hidden and Full is the preferred one,
altough they deliver almost same funcionality only that Tabbed doesn't
(Continue reading)

Ismael Carnales | 5 Apr 04:17 2009
Picon

First steps (not only words)

Breaking gwern's suggestion this is my second mail today :)

The way to implement some of my suggestions?

* Clean XMonadContrib of duped functionality modules
* Reviews XMonadContrib in search of dupped/common-used code
* Move this code to another contrib module, and maybe implement a
better interface over it
* Write good docs about the new module, it will be the base from new
modules to come
* Maintain this module in partial-stable situation (limitting commits)
* Move some functionality of this module to core

With these steps we can assure less breakage fom updating contribs,
and that will be more easy to write new modules because there's a
common codebase written and approved by core devels.

bye!
Kathryn Andersen | 5 Apr 04:47 2009

Re: Opinions (skip if you are busy)

On Sat, Apr 04, 2009 at 10:38:43PM -0300, Ismael Carnales wrote:
> What was my first thinking? No screenshots of the results of the usage
> of the module (only the withIM LayoutModifier had one, my preferred
> contrib), overlapping and difficult to understand functionality and
> some real gems that make your day-to-day life with Xmonad worh it.

Yes, yes, yes!

For a number of contrib modules, the documentation is minimal, they
don't explain what the module is for, what the results should be, what
the parameters *mean*.  Sure, they have a one-sentence description, but
that isn't enough.

A picture paints a thousand words; while screenshots wouldn't replace
good documentation, they would augment good documentation.

The difficulty, though, with providing screenshots is that they would be
best seen *with* the documentation for a module, but said documentation
is in the haskell code of the module (which is a Good Thing, don't get
me wrong) but that doesn't provide (so far as I know) the ability to add
in images to the generated HTML.

I know that someone did some screenshots on a separate page, but the
problem with that is that it's separated from the modules in question,
and also it has limited coverage.

I'm not sure what the solution is, but it would be nice to have one...

*thinks*

(Continue reading)

Mike Sampson | 5 Apr 05:16 2009

Re: Opinions (skip if you are busy)

HI,

On Sun, Apr 5, 2009 at 12:47 PM, Kathryn Andersen <kat_lists-HPSroj+Wjutt+tyI2NedBz+iFHGzDt/a@public.gmane.org> wrote:
What would make it easier for people to contribute screenshots?  Ones
that were clear examples of different layouts?
What would be nice would be
a) a list of all known layouts (alphabetical?)
b) a screenshot of each
c) a snippet of code which shows how that particular layout was
configured.

That is a great idea! Maybe include a simple vector representation of the layout suitable for use as an icon (when scaled down) for those who use icons in their status bars.

I'm pretty happy with the XMonad documentation. After a brief flirtation with another wm believe me the XMonad docs are at least up to date. I sometimes use the web based documentation however recently I started keeping darcs repos of the source for XMonad and the contrib modules solely for reference as I run xmonad from my distros repos. Having the source available makes it easy to check something with a quick grep. Most of the issues I have are due to my lack of skills in Haskell. I have read a couple of books on Haskell but have yet to become as skilled in it as python, C or C++. I have a long way to go. :)

Mike
<div>
<p>HI,<br><br></p>
<div class="gmail_quote">On Sun, Apr 5, 2009 at 12:47 PM, Kathryn Andersen <span dir="ltr">&lt;<a href="mailto:kat_lists@...elinux.org">kat_lists@...</a>&gt;</span> wrote:<br><blockquote class="gmail_quote">

What would make it easier for people to contribute screenshots? &nbsp;Ones<br>
that were clear examples of different layouts?<br>
What would be nice would be<br>
a) a list of all known layouts (alphabetical?)<br>
b) a screenshot of each<br>
c) a snippet of code which shows how that particular layout was<br>
configured.<br>
</blockquote>
</div>
<br>That is a great idea! Maybe include a simple vector representation of the layout suitable for use as an icon (when scaled down) for those who use icons in their status bars.<br><br>I'm pretty happy with the XMonad documentation. After a brief flirtation with another wm believe me the XMonad docs are at least up to date. I sometimes use the web based documentation however recently I started keeping darcs repos of the source for XMonad and the contrib modules solely for reference as I run xmonad from my distros repos. Having the source available makes it easy to check something with a quick grep. Most of the issues I have are due to my lack of skills in Haskell. I have read a couple of books on Haskell but have yet to become as skilled in it as python, C or C++. I have a long way to go. :)<br><br>Mike<br>
</div>
Henrique G. Abreu | 5 Apr 16:55 2009
Picon

Re: Swing and keyboard

Kendall,
AWT_TOOLKIT=MToolkit does not work well and introduce many problems to java apps, to solve the gray window problem use just the setWMName workaround.
There's another known problem with java issue 177, java apps appear to receive focus but keyboard doesn't work until user clicks on the window.
Have not applied the patch yet, but it seems to solve this.

Henrique G. Abreu

On Wed, Apr 1, 2009 at 14:46, Kendall Shaw <kshaw-BLmIX6/LPxu52Q1+CP7Olg@public.gmane.org> wrote:
I think the problem I experienced is a result of setting AWT_TOOLKIT=MToolkit. I noticed that I get the same non-working keyboard in whatever KDE's window manager is. Unsetting that environment variable, I have not had the non-working keyboard in xmonad so far.

So, I first set AWT_TOOLKIT which fixed the grey window problem. Then I tried setting setWMName to LG3D in EwmhDesktops.hs, but left AWT_TOOLKIT set, which seems to cause the non-working keyboard problem.

Kendall
_______________________________________________

<div>
<p>Kendall,<br>AWT_TOOLKIT=MToolkit does not work well and introduce many problems to java apps, to solve the gray window problem use just the setWMName workaround.<br>There's another known problem with java <a href="http://code.google.com/p/xmonad/issues/detail?id=177" target="_blank">issue 177</a>, java apps appear to receive focus but keyboard doesn't work until user clicks on the window.<br>

Have not applied the patch yet, but it seems to solve this.<br><br clear="all">Henrique G. Abreu<br><br></p>
<div class="gmail_quote">On Wed, Apr 1, 2009 at 14:46, Kendall Shaw <span dir="ltr">&lt;<a href="https://mail.google.com/mail?view=cm&amp;tf=0&amp;to=kshaw-BLmIX6/LPxu52Q1+CP7Olg <at> public.gmane.org" target="_blank">kshaw@...</a>&gt;</span> wrote:<br><blockquote class="gmail_quote">I think the problem I experienced is a result of setting AWT_TOOLKIT=MToolkit. I noticed that I get the same non-working keyboard in whatever KDE's window manager is. Unsetting that environment variable, I have not had the non-working keyboard in xmonad so far.<br><br>
So, I first set AWT_TOOLKIT which fixed the grey window problem. Then I tried setting setWMName to LG3D in EwmhDesktops.hs, but left AWT_TOOLKIT set, which seems to cause the non-working keyboard problem.<br><br>
Kendall<br>
_______________________________________________<br><div>
<div></div>
<div>xmonad mailing list<br><a href="https://mail.google.com/mail?view=cm&amp;tf=0&amp;to=xmonad <at> haskell.org" target="_blank">xmonad@...</a><br><a href="http://www.haskell.org/mailman/listinfo/xmonad" target="_blank">http://www.haskell.org/mailman/listinfo/xmonad</a><br>
</div>
</div>
</blockquote>
</div>
<br>
</div>

Gmane