Re: Client Movement between screens
There's a function awful.client.movetoscreen(c, s), which moves client c to screen s. I don't have a multi-screen set up to test this with, but my first attempt would be to add bindings to function (c) local nextscreen = c.screen + 1 if nextscreen screen.count then nextscreen = 1 end awful.client.movetoscreen(c, nextscreen) end and function (c) local prevscreen = c.screen - 1 if prevscreen 1 then prevscreen = screen.count end awful.client.movetoscreen(c, prevscreen) end to clientkeys in your rc.lua. There's probably some one-line way of choosing the next or previous screen, using %, but it's a bit too early in the morning here to think about that... (and it would obfuscate the code). Best, Matt On Thu, Mar 15, 2012 at 08:34:22PM -0500, Gerald Klein wrote: Hi, The default ability to move clients between screens is in only 1 direction, does anyone know if there is a way to go either directions or directly to a screen so I don't have to cycle through all my screens to get to where I am going. thanks for any help you may give. --jerry -- Gerald Klein DBA www.geraldklein.com j...@zognet.com 708-599-0352 Linux registered user #548580 The below contributed statements are wellfunny and I apologize if someone is offended.not. Unix is user-friendly. It just isn't promiscuous about which users it's friendly with. - Steven King Frustrated Windows users have two options. 1. Resort to throwing computers out of windows. 2. Resort to throwing Windows out of computers Ever realized that if you play Windows CD backwards you'll hear satanic messages? But that's nothing! If you play it forward it will install Windows. Ubuntu -- an African word, meaning Slackware is too hard for me. The day Microsoft makes a product that doesn't suck, is the day they make a vacuum cleaner. Linux is like a wigwam: no gates, no windows and Apache inside. (Chinese proverb c. 910 B.C.) being a Linux user is sort of like living in a house inhabited by a large family of carpenters and architects. Every morning when you wake up, the house is a little different. Maybe there is a new turret, or some walls have moved. Or perhaps someone has temporarily removed the floor under your bed * Unknown Customer: I'm running Windows... Helpdesk: Yes... Customer: ...and now my computer stopped working ! Helpdesk: Yes, you already said that. The box said Requires Windows 98 or better. So I installed Linux. I ran the Microsoft Malicious Software Removal tool but Internet Explorer is still installed on my computer. -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Re: Setting keyboard layout per client
ali.mousavi, don't you use Debian Wheezy? Some days ago I've got a strange issue with old configs for keyboard layout changing on Wheezy. Anyway, take Alexander's advice, setxbmap+kbdd should work for any system. On Thu, Mar 15, 2012 at 3:23 PM, ali.mous...@gmail.com ali.mous...@gmail.com wrote: hi, I wonder if anyone has a working way to set the keyboard leyout per client. I tried using xxkb which was suggested in the wiki[1], but it couldn't remember the layout for applications probably due to this bug[2]. So I tried kbdd which is explained in the wiki[3], and it was the only thing that worked but I couldn't use the shortcut alt + shift to change the keyboard. sometimes the shortcut works, sometimes doesn't and this is pretty much annoying. changing the shortcuts using the mouse buttons seemed to be working as expected. so, if anyone has any advice I really appreciate it. [1] http://awesome.naquadah.org/wiki/FAQ#How_to_add_a_keyboard_layout_switcher_.3F [2] https://awesome.naquadah.org/bugs/index.php?do=detailstask_id=476 [3] http://awesome.naquadah.org/wiki/Keyboard_layouts_with_kbdd
Re: Client Movement between screens
Hello, Matthew has done it _almost_ right, because awful itself handles wrapping. Something like this will be enough: function(c) local prevscreen = c.screen - 1 awful.client.movetoscreen(c,prevscreen) end function(c) local nextscreen = c.screen + 1 awful.client.movetoscreen(c,nextscreen) end Tested on 3 screens and works great - thanks for the idea Matthew :) BR, Paweł -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Re: Client Movement between screens
As I was also unable to find the information some time ago, I have edited the wiki and added this solution: https://awesome.naquadah.org/wiki/Move_Client_to_Monitor_Left/Right BR, Paweł -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
[awesome bugs] #490 - urxvt's client border is transparent under xcompmgr
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#490 - urxvt's client border is transparent under xcompmgr User who did this - Paweł Rumian (gorkypl) -- I'd like to request reopening of this bug, because: - I have encountered the same problem - The author of urxvt claims it is WM-related problem: http://lists.schmorp.de/pipermail/rxvt-unicode/2009q1/000906.html - wmii suffered from (most probably) the same problem and it was resolved by fixing thw WM, not urxvt: http://code.google.com/p/wmii/issues/detail?id=188 -- More information can be found at the following URL: https://awesome.naquadah.org/bugs/index.php?do=detailstask_id=490#comment2896 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. -- To unsubscribe, send mail to awesome-devel-unsubscr...@naquadah.org.
[PATCH] Functions for extended table inspection (gears.debug)
I'm a bit tired of carrying these around my machines so it would be nice
to see them in gears.debug. It is cold and empty there anyway.
The function names should definitely be changed. I use d because it is
easy to write, but perhaps something more comprehensible might do better.
From fec0997188f708a0a16aafeb590a9865a6b0dc61 Mon Sep 17 00:00:00 2001
From: Alexander Yakushev yakushev.a...@gmail.com
Date: Fri, 16 Mar 2012 22:03:23 +0200
Subject: [PATCH] gears.debug: Add functions for inspecting tables
Signed-off-by: Alexander Yakushev yakushev.a...@gmail.com
---
lib/gears/debug.lua.in | 65
1 file changed, 65 insertions(+)
diff --git a/lib/gears/debug.lua.in b/lib/gears/debug.lua.in
index 634faa0..6ee92d2 100644
--- a/lib/gears/debug.lua.in
+++ b/lib/gears/debug.lua.in
@@ -7,9 +7,16 @@
local error = error
local tostring = tostring
local traceback = debug.traceback
+local print = print
+local type = type
+local pairs = pairs
+local require = require
module(gears.debug)
+-- Variable to keep naughty module once it is required.
+local naughty = nil
+
--- Check that the given condition holds true, else throw an error
-- @param cond If this is false, throw a lua error with a backtrace.
-- @param message Message to print in the error (optional).
@@ -20,4 +27,62 @@ function assert(cond, message)
end
end
+-- Given a table (or any other data) return a string that contains its
+-- tag, value and type. If data is a table then recursively call d_raw
+-- on each of its values.
+-- @param data Value to inspect.
+-- @param shift Spaces to indent lines with.
+-- @param tag The name of the value.
+-- @return a string which contains tag, value, value type and table key/value
+-- pairs if data is a table.
+local function d_raw(data, shift, tag)
+local result =
+
+if tag then
+result = result .. tostring(tag) .. :
+end
+if not data then
+result = result .. nil
+else
+result = result .. tostring(data)
+end
+if type(data) ~= table then
+return result .. ( .. type(data) .. )
+end
+
+shift = (shift ~= nil) and shift ..or
+for k, v in pairs(data) do
+result = result .. \n .. shift .. d_raw(v, shift, k)
+end
+
+return result
+end
+
+--- Inspect the value in data.
+-- @param data Value to inspect.
+-- @param tag The name of the value.
+-- @return a string that contains the expanded value of data.
+function d_return(data, tag)
+return d_raw(data, nil, tag)
+end
+
+--- Print the table (or any other value) to the console.
+-- @param data Table to print.
+-- @param tag The name of the table.
+function d(data, tag)
+print(d_return(data, tag))
+end
+
+--- Show the table (or any other value) using Naughty.
+-- @param data Table to show.
+-- @param tag The name of the table.
+function d_show(data, tag)
+if not naughty then
+naughty = require(naughty)
+end
+naughty.notify( { title = ETDP,
+ text = log.d_return(s),
+ timeout = 0})
+end
+
-- vim: filetype=lua:expandtab:shiftwidth=4:tabstop=8:softtabstop=4:textwidth=80
--
1.7.9.4
