Skip to main content

Linux: Awesome is Awesome!

I decided to give Awesome a try. Awesome is a tiling window manager like xmonad. I've been using it for about a month, and I like it a lot.

It integrates with GNOME much better than dwm. Most users of dwm don't use GNOME, but I do. Its default settings are a lot nicer than xmonad's. When I use xmonad, I spend all my time futzing with my .xmonad.hs, but I haven't had to tweak Awesome at all the whole time I've used it. For instance, Awesome comes with a ton of layouts built in.

Getting gvim to work perfectly under xmonad required some tweaking, and I couldn't figure out how to get it to work perfectly under dwm. I know that this is gvim's fault because it doesn't follow the exact size prescribed by the window manager, so the bottom part of the screen gets messed up. I'm sure most dwm users don't use gvim--they probably run vim in a terminal. It worked perfectly under Awesome.

Getting NetBeans to work well took even more work, and even now it sometimes freezes in predictable (and avoidable) ways. I had to "sudo apt-get install suckless-tools", and then I added "xterm -e wmname LG3D" to my startup applications (i.e. my GNOME session). Finally, I switched to JDK 1.7.0 and edited /usr/local/netbeans-6.9.1/etc/netbeans.conf so that "netbeans_jdkhome="/usr/local/jdk-1.7.0".

Since Awesome and GNOME each have their own panels, I did some tweaking to make them get along better. I have Awesome's panel on the top, and one GNOME panel on the bottom. I got rid of things from the GNOME panel that were already provided by the Awesome panel. I'm pretty pleased with the result, and I didn't even have to futz with any configuration files to do it.

I really like the keybindings in Awesome. Since I had already played with xmonad and dwm, I didn't really have to re-learn the keybindings for Awesome since they're so similar. I just had to realize that all the keys were based on the command key (i.e. Mod4) instead of the control key.

I especially like having a different set of tags (i.e. virtual desktops) per monitor. That's exactly the paradigm I like the most. I use a big monitor for most things, and I use a lot of different tags. I use my laptop screen just for instant messaging applications, and I only use a single tag.

Plugging in or unplugging my monitor is a pain, especially since I have to tweak the Nvidia settings every time. I know it's a bit "ghetto", but my solution was to restart X every time I want to plug in or unplug my monitor. I think this actually takes less time than shuffling my windows around and futzing with my Nvidia settings.

I have found one Awesome bug. When I first login, my cursor is a clock, and it doesn't go away. If I play with the menus, it does. It's not a big deal, so I don't care.

The default layout is floating, and each tag has its own layout. This default works well for me. I only have to press Command-space to switch to tiling.

One of these days, I might give Qtile a try since it's written in Python and my buddy really likes it. However, in the meantime, I'm pretty happy with Awesome.

Comments

matt harrison said…
You know you want to give qtile a try. Eventually you will want to hack on your tiling wm....

WRT dual monitor support. Doesn't nvidia support xrandr? If I recall detaching worked on my intel gpu (or only required restarting awesome (which was a key binding)). Annoying to have to restart X. Qtile currently requires a restart with that but hopefully it will soon listen to xrandr events...
jjinux said…
I probably will give Qtile a try.

NVIDIA works. Awesome works. I just find it easier to log out and back in again rather than a) configuring NVIDIA via its GUI b) restarting Awesome c) shuffling all my windows around.
matt harrison said…
if xrandr works, then it seems like it would be easier with one command, rather than logging out, restarting apps, etc.

I've got a command called monitor_off.sh (ie turn off external monitor) that has the following in it:

xrandr --output VGA1 --off
xrandr --output LVDS1 --mode 1680x1050

In my awesome days, I just needed to run that and I was good to go.

cheers
Unknown said…
Nice, you gave Awesome a shot!

If you want a really slick looking GVim window, add these lines to your .gvimrc :

# Remove right scroll bar
set guioptions-=r
# Remove left scroll bar
set guioptions-=L
set guioptions-=b
" Remove menu
set guioptions-=m
" Remove toolbar
set guioptions-=T

After that it looks a lot more like vim in a terminal.
jjinux said…
> If you want a really slick looking GVim window, add these lines to your .gvimrc

Call me strange, but I actually like the "chrome" in Gvim.
jjinux said…
> if xrandr works, then it seems like it would be easier with one command, rather than logging out, restarting apps, etc.

Thanks, Matt. That's helpful.

Popular posts from this blog

Ubuntu 20.04 on a 2015 15" MacBook Pro

I decided to give Ubuntu 20.04 a try on my 2015 15" MacBook Pro. I didn't actually install it; I just live booted from a USB thumb drive which was enough to try out everything I wanted. In summary, it's not perfect, and issues with my camera would prevent me from switching, but given the right hardware, I think it's a really viable option. The first thing I wanted to try was what would happen if I plugged in a non-HiDPI screen given that my laptop has a HiDPI screen. Without sub-pixel scaling, whatever scale rate I picked for one screen would apply to the other. However, once I turned on sub-pixel scaling, I was able to pick different scale rates for the internal and external displays. That looked ok. I tried plugging in and unplugging multiple times, and it didn't crash. I doubt it'd work with my Thunderbolt display at work, but it worked fine for my HDMI displays at home. I even plugged it into my TV, and it stuck to the 100% scaling I picked for the othe

ERNOS: Erlang Networked Operating System

I've been reading Dreaming in Code lately, and I really like it. If you're not a dreamer, you may safely skip the rest of this post ;) In Chapter 10, "Engineers and Artists", Alan Kay, John Backus, and Jaron Lanier really got me thinking. I've also been thinking a lot about Minix 3 , Erlang , and the original Lisp machine . The ideas are beginning to synthesize into something cohesive--more than just the sum of their parts. Now, I'm sure that many of these ideas have already been envisioned within Tunes.org , LLVM , Microsoft's Singularity project, or in some other place that I haven't managed to discover or fully read, but I'm going to blog them anyway. Rather than wax philosophical, let me just dump out some ideas: Start with Minix 3. It's a new microkernel, and it's meant for real use, unlike the original Minix. "This new OS is extremely small, with the part that runs in kernel mode under 4000 lines of executable code.&quo

Haskell or Erlang?

I've coded in both Erlang and Haskell. Erlang is practical, efficient, and useful. It's got a wonderful niche in the distributed world, and it has some real success stories such as CouchDB and jabber.org. Haskell is elegant and beautiful. It's been successful in various programming language competitions. I have some experience in both, but I'm thinking it's time to really commit to learning one of them on a professional level. They both have good books out now, and it's probably time I read one of those books cover to cover. My question is which? Back in 2000, Perl had established a real niche for systems administration, CGI, and text processing. The syntax wasn't exactly beautiful (unless you're into that sort of thing), but it was popular and mature. Python hadn't really become popular, nor did it really have a strong niche (at least as far as I could see). I went with Python because of its elegance, but since then, I've coded both p