Adam Nielsen | 16 Sep 14:18 2014
Picon

How to bind to nonstandard keys

Hi all,

Further to my last post, I am trying to have certain behaviour bound to
specific keys.

I have redefined my keyboard such that the F1 key (among others)
produces they same key code but a different keysym.  Pressing my F1 key
now acts as if F21 is pressed.

However I cannot correctly bind to this key in Awesome.  If I run xev
and press F1, it tells me I have pressed F21.  If I tell Awesome to
bind to F21, then when I press the key xev tells me it is bound to
another program (good) but Awesome does nothing (bad).

Worse still, if I tell Awesome to bind an action to F1, then it does
the action even when I am pressing what is supposed to be the F21 key.
(This means I can't actually press F1 because Awesome has stolen that
key.)

How can I tell Awesome to respect the XKB keyboard mapping and perform
an action on the keys it has bound?  Currently it binds to the correct
key but fails to act on it.

Many thanks,
Adam.

Adam Nielsen | 16 Sep 06:08 2014
Picon

Bind key to switch to specific app on any desktop/monitor

Hi all,

I'm wondering whether it's possible to write a Lua function that
switches focus to a specific app, such as Firefox or a terminal.

The reason I ask is that I have redefined my keyboard mapping so that
the F1 to F12 keys generate keycodes for F21 to F32.  (If I hold Caps
Lock while pressing the keys I get the original F1 to F12 back again.)

I would like to assign for example F21 to focus my web browser, F22 to
focus my e-mail client, F23 to focus the active chat window, etc.  This
way I can make better use of my muscle memory and quickly switch
between apps without having to remember what monitor I am currently on
and what desktop the app is on.  I frequently forget and end up
switching desktop on the wrong monitor, so I am hoping this will fix
the problem.

The trick is I don't want to focus a specific desktop on a specific
screen, because I tend to move the apps between monitors depending on
which ones I want to view all at once.  So this function would need to:

 1. Find a window based on some criteria (class, title, etc.)  It would
    be great if this was a function parameter so some keys could search
    for a window by title, but others by class or role.

 2. Focus whichever monitor the window resides on.

 3. Switch to whichever desktop the window is on.

 4. Focus the window.
(Continue reading)

Joren Heit | 15 Sep 21:58 2014
Picon

Weird terminator behavior

Hi guys,

I wrote some simple routines to enable tiling in a floating environment. It works fine with, for example, an iceweasel window but I get really weird behavior with my terminal emulator: Terminator.

When I open a fresh window and try to tile it e.g. to the left, the window starts resizing automagically. However, when I have dragged/resized it prior to tiling, everything works as expected.

To illustrate this, I've uploaded a demo to youtube: https://www.youtube.com/watch?v=a5wgCw01kkE
Does anyone have any idea what's going on? Here's the most important piece of the lua code:

function tile(c, dir)

   if c == nil then return end

   if not floatTile[c] then
      resetFloatTile(c)
   end

   c.maximized = false
   c.minimized = false

   local s = mouse.screen
   local cg = c:geometry()
   local sg = screen[s].workarea

   local x, y, width, height

   if dir == "left" then
      x,y,width,height = tileLeft(c, cg, sg)
   elseif dir == "right" then
      x,y,width,height = tileRight(c, cg, sg)
   elseif dir == "up" then
      x,y,width,height = tileUp(c, cg, sg)
   elseif dir == "down" then
      x,y,width,height = tileDown(c, cg, sg)
   elseif dir == "full" then
      x,y,width,height = tileFull(c, sg)
   end

   c:geometry({x = x, y = y, width = width, height = height})
end


I think the only relevant piece of the code above is the change in geometry.
By the way, other windows sometimes don't get drawn properly after tiling. I remember in 3.4 that we could force a redraw of a client, but I couldn't find anything anymore in the docs.

Thanks,
Joren

Matija Žeželj | 15 Sep 18:06 2014
Picon

lain, widget update and dual screen issues

Hi list,

I use Lain and vicious to display widgets in awesome and i have dual screen setup; my notebook screen is used as secondary display and external, hdmi screen is used as primary.
On primary and secondary monitors same wibox is displayed but only on primary(external) monitor there is systray and i like it that way. But i came across he problem with lain widgets - they are not updating on external monitor.
My rc.lua is attached so you can see how i call the widgets.
other then that i had no issues and this rc.lua works great just in order to refresh the widgets on main screen i need to restart awesome :)

Thx in advance,
--
Matija Žeželj
Attachment (rc.lua): text/x-lua, 34 KiB
Zum Testen | 15 Sep 12:39 2014
Picon

Adjust screen brightness with launcher

I want to change the brightness of my screen with awful.widget.launcher. The launcher should contain an
icon, indicating the actual brightness. Clicking on the launcher should open a menu to choose the
brightness value in percent.

Problem: When clicking on the launcher, the icon is changing immediately to the icon, which was first
loaded after starting awesome, ignoring the actual brightness. Choosing a value from the list of the menu
will update the icon properly. But if cancelling the menu, the wrong icon will remain.

For example, the brightness was 30% when starting awesome. I change the brightness with the launcher to
100%. No problem. But now I click on the launcher again: the launcher will show the 30% icon, despite the
fact that I have not chosen a value from the menu. Pressing Escape will cancel the menu, but the wrong icon
still remains: The brightness is 100% but the icon shows 30%.

mybrightness.lua (the global mybrightness_launcher will be added to my wibox):

local awful = require("awful")

local mybrightness_menu = awful.menu({ items = 
    {{"100%", function() awful.util.pread("xbacklight -time 0 -set 100"); brightness_update() end},
     {" 30%", function() awful.util.pread("xbacklight -time 0 -set  30"); brightness_update() end}}})
mybrightness_launcher = awful.widget.launcher({image = "bright100.png", menu = mybrightness_menu})

function brightness_update()
    local max_brightness = awful.util.pread('cat /sys/class/backlight/intel_backlight/max_brightness')
    local actual_brightness = awful.util.pread('cat /sys/class/backlight/intel_backlight/actual_brightness')
    local brightness_percent = 0
    if max_brightness ~= nil and actual_brightness ~= nil then
        brightness_percent = actual_brightness * 100 / max_brightness
    end

    if brightness_percent > 50 then
        brightness_icon = "bright100.png"
    else
        brightness_icon = "bright030.png"
    end
    mybrightness_launcher:set_image(brightness_icon)
end

brightness_update()

Kevin Clay | 14 Sep 10:46 2014
Picon

Awesome Menu Applicaions

I have been through the wiki on installing Awesome for the first time 
and I see screenshots in which the awesome menu has categorized lists of 
applications. The wiki doesn't explain how to do this or if it supposed 
to do this automagically. My menu doesn't show any applicaions and I was 
wondering how to get it to do this.

Thanks.

Paul Jolly | 7 Sep 09:24 2014
Picon

PID of active window

Hi - this will I'm sure be a fairly basic question. 

I have a keyboard shortcut to launch a urxvt:

terminal = "urxvt"
-- ...
awful.key({ modkey,           }, "Return", function () awful.util.spawn(terminal) end)

What I'm now looking to do is setup another key binding that, given the currently active window, a urxvt instance, launches another instance which uses the same CWD. 

Has anyone done this before?

If I can can the PID of the current window that will be enough to then use pwdx or similar approaches. 

Other thoughts/approaches?

Thanks,


Paul
Andre Naujoks | 1 Sep 11:15 2014
Picon

Windows opening on wrong screen

Hi.

I am just giving awesome a try and like it so far. I am on a debian sid
with awesome version 3.4.15-1+b1.

It has one quirk, where I think it is a bug.

When I open a window (say a terminal with Mod4 + Return, but the
application does not matter.), the window should apear on the current
active screen. This works for two of my three screens, but not for the
third. The same happens when I open a window via the right-mouse-click
menu from the desktop, or when I use the top left button to bring up the
menu.

- I select the screen by either moving the mouse into it, or Mod4+Ctrl+j/k.
- I start an application on my right-most screen and the window opens on
my primary/center screen.

I attached a screenshot of my layout, so you get an idea of what I am
talking about. (the black stripes above the left and right screen are
unused, i.e. the monitors end where the menu-bar is)

As mentioned it works for the left and the center screen, but not for
the right one.

Am I doing something wrong or is this a bug? I am not familiar enough
with lua or window managers at all to try my hand at this, but I can
test and try patches.

Regards
  Andre
mickael foucaux | 1 Sep 11:06 2014
Picon

ubuntu 12.10 + awesome 3.4.15

Hi there!

Just installed fresh awesome over ubuntu. And my issue is:

- Meta + R: works blind. I want to show the one line terminal.

Does anybody know how to configure the desktop ?

thanks,

mickael
Evgeny Pakhomov | 26 Aug 12:11 2014
Picon

Desktop notifications + tag mark

Hi,

Is there any way to make a desktop notification from Google Chrome mark the tag where the browser resides in the same way a just opened application does? On my theme a tag becomes green.
I've tried to find some settings in Google Chrome to make its window blink when a notification is sent, but there appears to be nothing.

Regards,
Eugene

Dolan Murvihill | 23 Aug 03:41 2014
Picon

Difficulty building on Arch

Hello,

Cmake is giving me difficulty when trying to build Awesome on Arch. The build
says:

CMake Error: Attempt to add a custom rule to output
"/home/d/awesome/themes/default/titlebar/floating_normal_inactive.png.rule" which already
has a custom rule.
CMake Error: Attempt to add a custom rule to output
"/home/d/awesome/themes/default/titlebar/maximized_normal_inactive.png.rule" which already
has a custom rule.
CMake Error: Attempt to add a custom rule to output
"/home/d/awesome/themes/default/titlebar/ontop_normal_inactive.png.rule" which already has a
custom rule.
CMake Error: Attempt to add a custom rule to output
"/home/d/awesome/themes/default/titlebar/sticky_normal_inactive.png.rule" which already has a
custom rule.
CMake Error: Attempt to add a custom rule to output
"/home/d/awesome/themes/zenburn/titlebar/floating_normal_inactive.png.rule" which already
has a custom rule.
CMake Error: Attempt to add a custom rule to output
"/home/d/awesome/themes/zenburn/titlebar/maximized_normal_inactive.png.rule" which already
has a custom rule.
CMake Error: Attempt to add a custom rule to output
"/home/d/awesome/themes/zenburn/titlebar/ontop_normal_inactive.png.rule" which already has a
custom rule.
CMake Error: Attempt to add a custom rule to output
"/home/d/awesome/themes/zenburn/titlebar/sticky_normal_inactive.png.rule" which already has a
custom rule.
CMake Error: Attempt to add a custom rule to output
"/home/d/awesome/themes/default/titlebar/ontop_normal_inactive.png.rule" which already has a
custom rule.
CMake Error: Attempt to add a custom rule to output
"/home/d/awesome/themes/default/titlebar/sticky_normal_inactive.png.rule" which already has a
custom rule.
CMake Error: Attempt to add a custom rule to output
"/home/d/awesome/themes/default/titlebar/floating_normal_inactive.png.rule" which already
has a custom rule.
CMake Error: Attempt to add a custom rule to output
"/home/d/awesome/themes/default/titlebar/maximized_normal_inactive.png.rule" which already
has a custom rule.
CMake Error: Attempt to add a custom rule to output
"/home/d/awesome/themes/zenburn/titlebar/ontop_normal_inactive.png.rule" which already has a
custom rule.
CMake Error: Attempt to add a custom rule to output
"/home/d/awesome/themes/zenburn/titlebar/sticky_normal_inactive.png.rule" which already has a
custom rule.
CMake Error: Attempt to add a custom rule to output
"/home/d/awesome/themes/zenburn/titlebar/floating_normal_inactive.png.rule" which already
has a custom rule.
CMake Error: Attempt to add a custom rule to output
"/home/d/awesome/themes/zenburn/titlebar/maximized_normal_inactive.png.rule" which already
has a custom rule.
-- Configuring incomplete, errors occurred!
See also "/home/d/awesome/CMakeFiles/CMakeOutput.log".
See also "/home/d/awesome/CMakeFiles/CMakeError.log".
Makefile:22: recipe for target 'cmake' failed
make: *** [cmake] Error 1

Has anyone seen this before? I am not very familiar with CMake.


Gmane