awesome | 2 Apr 14:06 2011

[awesome bugs] #877 - Occasional keyboard freeze

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#877 - Occasional keyboard freeze
User who did this - Momchil (xaxo)

----------
I might have found out what "freezes" my keyboard, namely SlowKeys from AccessX, but still don't know how to
disable SlowKeys. If I wait long enough the keys work as normal, but don't know how to quit SlowKeys or
change the key combo for activating it. For the time being I've disabled AccessX completely.

I will try your patch regarding the error message and send you the output.

Thank you for your time.
----------

More information can be found at the following URL:
https://awesome.naquadah.org/bugs/index.php?do=details&task_id=877#comment2592

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-unsubscribe <at> naquadah.org.

awesome | 6 Apr 08:24 2011

[awesome bugs] #883 - awful.autofocus and moving clients

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

A new Flyspray task has been opened.  Details are below. 

User who did this - awesome fan (awesomefan) 

Attached to Project - awesome
Summary - awful.autofocus and moving clients
Task Type - Bug Report
Category - awful
Status - Unconfirmed
Assigned To - 
Operating System - All
Severity - Medium
Priority - Normal
Reported Version - 3.4.9
Due in Version - Undecided
Due Date - Undecided
Details - I am using awesome 3.4.9, built from source, on Debian 6.

Although I require'd awful.autofocus in my rc.lua, I am able set up a tag with open clients and no focus. I can
simply do so by viewing an empty tag and programatically moving (e.g. view awesome-client) a client to the
that empty tag I am currently viewing. The client is moved to my tag, but the focus is not updated.

More information can be found at the following URL:
https://awesome.naquadah.org/bugs/index.php?do=details&task_id=883

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.
(Continue reading)

awesome | 8 Apr 16:44 2011

[awesome bugs] #883 - awful.autofocus and moving clients

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#883 - awful.autofocus and moving clients
User who did this - Uli Schlachter (psychon)

----------
What exactly do you do to make this happen?
----------

More information can be found at the following URL:
https://awesome.naquadah.org/bugs/index.php?do=details&task_id=883#comment2593

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-unsubscribe <at> naquadah.org.

awesome | 9 Apr 09:25 2011

[awesome bugs] #883 - awful.autofocus and moving clients

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#883 - awful.autofocus and moving clients
User who did this - awesome fan (awesomefan)

----------
I added this function to my rc.lua:

function move_to_tag(xid, tag)
   local clients=client.get()
   for k,c in pairs(clients) do
	  if c.window==xid then
		 awful.client.movetotag(tag, c)
		 return true
	  end
   end

   return false
end

now I am on tag a, open a new terminal shell (emacs shell), and execute

sleep 5 ; echo 'move_to_tag(XID, media_tag)' | awesome-client

with XID being the very x window id of the shell window.
media_tag has no clients at all.
Whilst the 5 second sleep, I am unselecting all selected tags and select media_tag. After 5 seconds, my
shell window is moved to media tag (the tag currently selected), but the focus is not set to that the shell
(Continue reading)

awesome | 9 Apr 09:27 2011

[awesome bugs] #884 - "property::selected"-signal broken?

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

A new Flyspray task has been opened.  Details are below. 

User who did this - awesome fan (awesomefan) 

Attached to Project - awesome
Summary - "property::selected"-signal broken?
Task Type - Bug Report
Category - Core
Status - Unconfirmed
Assigned To - 
Operating System - All
Severity - Medium
Priority - Normal
Reported Version - 3.4.9
Due in Version - Undecided
Due Date - Undecided
Details - I am using awesome 3.4.9, built from source, on Debian 6.

I would like to auto-select the client under point when changing the selection of tabs.
Doing it like this

tag.add_signal(
   "property::selected",
   function(t)
   local c = mouse.object_under_pointer()
   if c then
   client.focus = c
   end
(Continue reading)

awesome | 9 Apr 10:08 2011

[awesome bugs] #884 - "property::selected"-signal broken?

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task is now closed:

FS#884 - "property::selected"-signal broken?
User who did this - Uli Schlachter (psychon)

Reason for closing: Not a bug
Additional comments about closing: "property::signal" isn't emitted on the tag class, but on the
individual tags. Try this (nil means "all screens"):

awful.tag.attached_add_signal(nil, "property::selected", function () print("I know how to use
signals") end)

(In the git/master branch this is changed so that instance signals are also emitted on the class, so your
code would work there)

More information can be found at the following URL:
https://awesome.naquadah.org/bugs/index.php?do=details&task_id=884

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-unsubscribe <at> naquadah.org.

awesome | 9 Apr 10:29 2011

[awesome bugs] #884 - "property::selected"-signal broken?

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#884 - "property::selected"-signal broken?
User who did this - awesome fan (awesomefan)

----------
Oh, ok. Thank you.

Unfortunately "property::selected" does not work for my use-case. It is called before the actual layout
algorithm is run, that is mouse.object_under_pointer() returns the client under point in the old tag selection.
I think awesome need a new signal - something like layout_run ?!
----------

More information can be found at the following URL:
https://awesome.naquadah.org/bugs/index.php?do=details&task_id=884#comment2595

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-unsubscribe <at> naquadah.org.

awesome | 9 Apr 10:41 2011

[awesome bugs] #884 - "property::selected"-signal broken?

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#884 - "property::selected"-signal broken?
User who did this - awesome fan (awesomefan)

----------
ok, the arrange signal of screen is what I am looking for :D
----------

More information can be found at the following URL:
https://awesome.naquadah.org/bugs/index.php?do=details&task_id=884#comment2596

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-unsubscribe <at> naquadah.org.

awesome | 9 Apr 11:11 2011

[awesome bugs] #885 - new signal post_arrange

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

A new Flyspray task has been opened.  Details are below. 

User who did this - awesome fan (awesomefan) 

Attached to Project - awesome
Summary - new signal post_arrange
Task Type - Feature Request
Category - Core
Status - Unconfirmed
Assigned To - 
Operating System - All
Severity - Low
Priority - Normal
Reported Version - git/master
Due in Version - Undecided
Due Date - Undecided
Details - I am using awesome 3.4.9, built from source, on Debian 6.

I would like to get the client under the mouse pointer whenever the layout is rearranged (e.g. a new client is
added, the tags are switched, etc.)
Is there any method to do so? I tried the arrange signal of screen, but calling
awful.mouse:client_under_pointer() in the callback always returns the client under pointer in regard
to the old layout, not the new one.

More information can be found at the following URL:
https://awesome.naquadah.org/bugs/index.php?do=details&task_id=885

You are receiving this message because you have requested it from the Flyspray bugtracking system.  If you
(Continue reading)

awesome | 9 Apr 11:31 2011

[awesome bugs] #885 - new signal post_arrange

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task is now closed:

FS#885 - new signal post_arrange
User who did this - Uli Schlachter (psychon)

Reason for closing: Not a bug
Additional comments about closing: The arrange signal is emitted after the layout is run, not before (=
does exactly what you want it to do). The problem you are hitting is that awesome does lazy (un)banning to
avoid some flicker. So awesome's internal state was already changed to the new layout, but the X11 server
wasn't told about any of this yet (We do ask the X11 server for client_under_pointer()).

Ugly workaround: Use a timer!

local t = timer({timeout = 0})
t:add_signal("timeout", function() t:stop() local c = awful.mouse.client_under_pointer() print(c) end)
t:start()

This would make sure that your code runs after the tag switch is handled completely (= in the next main loop
iteration, in this case).

More information can be found at the following URL:
https://awesome.naquadah.org/bugs/index.php?do=details&task_id=885

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.

--

-- 
(Continue reading)


Gmane