So I've been trying to use this config as my starter with xmonad, but it's been pretty rough so far, finding out what things are defined specifically for the original creator and then realizing that I have to change them.

Well at this point I have no idea what I'm supposed to do in order to get yeganesh to work. I did not modify the configs mapping to launch and it successfully does so, however it doesn't actually "launch stuff" when I press enter. I ran dmenu_run from the command line, and that worked as expected, so I have no idea what it might be.

I've an arch linux installation and current git reposistory has been cloned., and xmonad/xmobar works perfect. But the default dmenu-with-yeganesh doesn't do anything it appears but doesn't launch the app. The following modificaiton solves the problem for my case. I'm not sure if this problem is glabal and effects all users:

in the ~/.xmonad/bin/dmenu-with-yeganesh the execution command should be added i.e.:

this line: dmenu_path | ~/.cabal/bin/yeganesh -- -nb ....
should be modifedi to this:
exec $(dmenu_path | ~/.cabal/bin/yeganesh -- nb .......)

best regards

This isn't really an issue, but I added some volume indicators to my xmobar, and thought I'd let you know in case you'd like to do the same.

See
hamtie@6e0bed5

Cheers.

Hi, sadly I don't know any Haskell. Will there be a chance to support numpad keys on switching workspaces?

This may be particular to me, and/or may be obvious to Haskell users. But as someone new to xmonad and Haskell, I was kind of puzzled as to why the action bound to Alt+P - dmenu/yeganesh - was not working. Using Manjaro Linux (XFCE Flavor) v0.83.

Installing yeganesh globally like cabal install --global yeganesh did the trick for me, and now it works great. Maybe the README should instruct accordingly. Thanks for the great config.

In readme you giving such a command:

ln -s ~/.xmonad/xsession ~/.xsession (and correspoding for .xinitrc)

but xsession is in /bin forlder so it should be

ln -s ~/.xmonad/bin/xsession ~/.xsession

no?

I was just curious about what was being used in terminal of the screenshot. I could discern vim but nothing else. Could you please let me know?

Hi! First, thanks for sharing your xmonad config; I've found it to be a really nice starting point for using xmonad. Since upgrading to the latest version (changes as of Feb 18), the config no longer works for me; when I reload with the new config, I get a view of my desktop background with a black box around it, and am unable to see applications. If I log out and attempt to log back in, my screen flashes and I am returned to the login screen.

Downgrading back to the first commit before today fixes it.

Hi, I was looking for a sane, easy-to-use configuration for xmonad and I followed the directions but when I load xmonad none of the scripts work? dmenu works in a default config of xmonad but stops coming up with mod-P when I have this enabled. I'm not sure what's wrong and I'd like to be able to implement this.

I'm not asking for personal tech support (well sorta) 'cause that can take time for a busy dev like yourself lol, but I'm curious if there's something I missed from the readme or an installation requirement. Thanks!

So I've tried multiple Stalonetray Config, i've tried both .stalonetrayrc-single.rc and .stalonetrayrc-dual.rc
and it does not work correctly. Stalonetray Always launches on my 2nd Monitor (btw i'm running 3 monitors) and i cant get on to the first monitor, both of which are 1080p monitors

On most recent distros running systemd, Consolekit is not required, as login sessions are now handled by systemd-logind. This includes Arch Linux and Debian.

In addition to this, Consolekit is not being maintained anymore.

I love how simple your config is and am basing parts of my own public xmonad.hs (and bin files) on it.

Any chance you could add an open source license to the project?

I was trying to trace down an issue with stalonetray, so I tried upgrading to xmonad-0.13. I installed xmonad via cabal --global, and hid my old (apt install'd) xmonad by moving it to xmonad.orig.

However, now I seem to have gotten into an inconsistent state, when I reload xmonad I get the following compile error:

xmonad.hs:82:7:
Couldn't match type ‘xmonad-0.12:XMonad.Core.Query’
with ‘Query’
NB: ‘xmonad-0.12:XMonad.Core.Query’
is defined in ‘XMonad.Core’ in package ‘xmonad-0.12’
‘Query’ is defined in ‘XMonad.Core’ in package ‘xmonad-0.13’
Expected type: Query Bool
Actual type: xmonad-0.12:XMonad.Core.Query Bool
In the first argument of ‘(-->)’, namely ‘isFullscreen’
In the expression:
isFullscreen --> (doF W.focusDown <+> doFullFloat)

I recognize this isn't really a problem with your config, but any pointers on how to fix it would still be really appreciated. :)

I'm on Ubuntu 16.04 using Stack instead of normal cabal, and since I'm new to xmonad, and haskell, I'm not sure if I've botched something up.

In trying to get xmonad to work, I ended up doing sudo apt-get install xmonad ... as well as stack install xmonad, so I'm not sure which is being used but xmonad finally sort of works. I removed all of my attempts at a custom config before trying this lib, which I think is a great idea btw, and it's super glitchy.

As soon as I log in to xmonad, it opens 2 bash terminals and a chrome window, but those only exist for like 5 sec. before they all disappear, to be found on none of the alternate workspaces, and the entire screens turns to my nautilus desktop, and icons respond to my mouse, but i can't open any folders, and i can't open any programs including a new terminal. I can logout, and back into my normal Ubuntu (is it Unity?) in order to post this issue.

Any idea what I've done wrong? Or are there any logs somewhere I can send you that might help discern whats up?

What is the font on the screenshot, featured in terminal window and vim?

xmonad.hs actually runs dmenu_path_c, not dmenu or dmenu_run. So that is a dependency needing to be listed.

Hello, thanks to share your config, seem it will very good for me, just begining in the Linux.

Well i install the thing as you said in the readme.md. The issues I notice:

The "Vol" only shows Updating, the stalanotray not load or are not showing up, when i press alt+p, nothing happens, the same to the screen shots binds.

thank you

This may be more an issue with xmobar than this repository, but I found that xmobar didn't work right when installed with pacman. I tried each version 0.15.x-0.16.

Ultimately I uninstalled xmobar using pacman, then installed with sudo cabal install --global xmobar. I then had to change the invocation of xmobar, because this installs to /usr/local/bin/xmobar instead of /usr/bin/xmobar. But now it works.

Perhaps this isn't an issue for everyone, but I figure that the install instructions, adjusted like so, will probably still work for everyone it worked for previously, plus cases (such as my own) where it was not working right.

xmonad.hs:75:1: parse error (possibly incorrect indentation)

myLayout = avoidStruts (
    Tall 1 (3/100) (1/2) |||
    Mirror (Tall 1 (3/100) (1/2)) |||
    tabbed shrinkText tabConfig |||
    Full |||
    spiral (6/7)) |||
    noBorders (fullscreenFull Full)

Specifically on the first line, I don't know why.

I have an empty space where my stalonetray should be. I'm not sure what's wrong, as I haven't used stalone tray before.

• I'm using xmonad 0.13
• I'm on almost-unmodified head ( a few trivial changes like new keyboard shortcuts)
• I adjusted the resolutions in stalonetrayrc-single as directed
• I have stalonetrayrc-single linked to .stalonetrayrc

This bug does happen on the new dmenu version like in Fedora 18.
https://bugzilla.redhat.com/show_bug.cgi?id=757435
line 136: spawn "exe=dmenu_path_c | yeganesh && eval "exec $exe"")
must be dmenu_run instead.
Then everything works fine, since this breaks with the older versions this is a problem.

How to start xmonad from LightDM on ubuntu 13.04

Using Slim and the suggested symbolic link [1], xcompmgr doesn't seem to be running on startup. After installing xtransset-df for window opacity settings and setting an opacity level on a particular window I expected the window's opacity to change but nothing happened.

This led me to run the xcompmgr command in a terminal [3] taken from the bin/xsession file which is symbolically linked to ~/.xsession (and b/c I was originally using xinit instead of slim, ~/.xinitrc). The window immediately reduced in opacity.

This is the primary concern for this ticket, whether the xsession script is mostly blown away by the last exec command or not but first and foremost why xcompmgr isn't running.

However, my personal and private goal is for the windows to fade down their opacity when they loose focus. If you can help me with that I would be greatful. I've linked my commits [2] below so that you can see what I'm working with.

[1] ~/.xsession -> /home/obimod/.xmonad/bin/xsession*
[2] https://github.com/obimod/xmonad-config/commits/master
[3] xcompmgr -n -c -C -t-5 -l-5 -r4.2 -o.55 -F ...(taken from an archlinux wiki page)