Re : Cups/Num Lock change event
De : basilio basi...@gmx.com
À : awesome@naquadah.org
Envoyé le : Vendredi 13 avril 2012 21h18
Objet : Re: Cups/Num Lock change event
Hi to all!
I understand that my question is not as easy as changing background and
all that bells and whistles and really needs an expert. But anyway I
need some help. I believe that this can be done somehow using signals. I
just can't understand how to catch the event of pressing Cups/Num Lock
button other way than awful.key(). This is too complicated for me
unfortunately. Can somebody give a clue? The rest I could have done myself.
Thanks ahead.
P.S. awful.key({},Caps_Lock, ) gets the keypress event right and caps
lock even toggles, but it forces unwanted keyboard layout change of the
current window either.
07.04.2012 23:41, basilio пишет:
Hi to all!
Is there a way to trace Cups/Num lock change event from rc.lua?
(Other than awful.key({ }, Caps_Lock, ))
I need that for triggering update of the widget with Cups Num locks
state. Thanks ahead.
Hi,
Did you try with xset ?
mytextbox = widget({ type = textbox })
mytextbox.text = io.popen(xset q | grep Num |awk '{print $8}'):read(*all)
with a link to a Timer, but it's not efficient ...
--
To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Odd lua error in xdg menu
Hi, thanks in advance, I am getting an odd lua error when I try to access my programming menu item of an xdg menu. /usr/share/awesone/lib/awful/menu.lua :221: attempt to compare number with nil This points to the following statement. awful.client.focus.byidx( -1 ) I am at loss how this is connected to the error as I am trying to access one menu item. Also other menu items work just fine. Dies anyone have an idea what this is? appreciate the help thanks --jerry -- Gerald Klein DBA contac...@geraldklein.com www.geraldklein.com http://geraldklein.com/ j...@zognet.com 708-599-0352 Linux registered user #548580
Fwd: Odd lua error in xdg menu
Sorry that line was incorrect the line actually is: if icon.width data.h or icon.height data.h then thanks I apologize: -- Forwarded message -- From: Gerald Klein j...@zognet.com Date: Sun, Apr 15, 2012 at 8:18 AM Subject: Odd lua error in xdg menu To: awesome@naquadah.org Hi, thanks in advance, I am getting an odd lua error when I try to access my programming menu item of an xdg menu. /usr/share/awesone/lib/awful/menu.lua :221: attempt to compare number with nil This points to the following statement. awful.client.focus.byidx( -1 ) I am at loss how this is connected to the error as I am trying to access one menu item. Also other menu items work just fine. Dies anyone have an idea what this is? appreciate the help thanks --jerry -- Gerald Klein DBA contac...@geraldklein.com www.geraldklein.com http://geraldklein.com/ j...@zognet.com 708-599-0352 Linux registered user #548580 -- Gerald Klein DBA contac...@geraldklein.com www.geraldklein.com http://geraldklein.com/ j...@zognet.com 708-599-0352 Linux registered user #548580
[awesome bugs] #987 - Guake won't appear in an empty tag (Attachment added)
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below. User who did this - Dariusz Dwornikowski (tdi) Attached to Project - awesome Summary - Guake won't appear in an empty tag Task Type - Bug Report Category - Core Status - Unconfirmed Assigned To - Operating System - Linux Severity - Medium Priority - Normal Reported Version - 3.4.11 Due in Version - Undecided Due Date - Undecided Details - The problem is with guake terminal (I use version 0.4.2 and awesome 3.4.11). Description: Guake does not show itself on an empty tag. Workaround : Guake shows itself when there is at least one window in a tag, or You click on a tag in a awesome bar and then guake appears. Steps to reproduce: Install guake, push F12 in ampty tag, guake does not appear. I am attaching xprop output from guake window. One or more files have been attached. More information can be found at the following URL: https://awesome.naquadah.org/bugs/index.php?do=detailstask_id=987 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.
[awesome bugs] #982 - Mouse events under non-English keyboard layout
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#982 - Mouse events under non-English keyboard layout User who did this - Roman Kosenko (kite) -- So does that mean this is a bug in xkbcomp and not in awesome? It seems so... But other applications work fine - awesome is one of a few applications that directly use xcb. Xlib uses xcb in some other way and there are no problems. -- More information can be found at the following URL: https://awesome.naquadah.org/bugs/index.php?do=detailstask_id=982#comment2952 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.
[awesome bugs] #987 - Guake won't appear in an empty tag (Attachment added)
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#987 - Guake won't appear in an empty tag User who did this - Arvydas Sidorenko (Asido) -- I just tried guake-0.4.2-r1 on awesome-git v3.4-646-g6841999 Build: Apr 6 2012 21:38:35 for x86_64. Everything works fine. -- One or more files have been attached. More information can be found at the following URL: https://awesome.naquadah.org/bugs/index.php?do=detailstask_id=987#comment2953 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.
[awesome bugs] #988 - Does not spawn on all screens in a multi-screen X11 layout
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below. User who did this - Lukas Sabota (prg318) Attached to Project - awesome Summary - Does not spawn on all screens in a multi-screen X11 layout Task Type - Bug Report Category - Core Status - Unconfirmed Assigned To - Operating System - Linux Severity - High Priority - Normal Reported Version - git/master Due in Version - Undecided Due Date - Undecided Details - I'm having an issue on a mutli-monitor, multi-Xscreen setup with the latest source of awesome in git. Awesome 3.4.11 does not have this issue. In 3.4.11, awesome spawns on each of my 3 X screens when I run startx with awesome in my .xinitrc (which is the expected behavior). With awesome from the latest git source, awesome only spawns on the primary monitor. The other monitors show the stock X11 cursor when mousing over to them. I've tested this with my usual configuration as well as removing the ~/.config/awesome directory for both 3.4.11 and git and it does not change the behavior. Here are my specifications: 64 bit Arch Linux xorg 1.12.1 (Xinerama disabled -- Multiple X screens -- one screen for each monitor) nvidia proprietary module (gt 520 card) Let me know if there is any more information I can provide. More information can be found at the following URL: https://awesome.naquadah.org/bugs/index.php?do=detailstask_id=988 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.
