THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

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

User who did this - Daniel Hahler (blueyed) 

Attached to Project - awesome
Summary - Unknown signal "marked" / "unmarked"; re-add support for marked 
clients back to default config
Task Type - Bug Report
Category - awful
Status - Unconfirmed
Assigned To - 
Operating System - All
Severity - Low
Priority - Normal
Reported Version - git/master
Due in Version - Undecided
Due Date - Undecided
Details - I was trying to use the client's marked-API, but its signals are not 
emitted:

    W: awesome: luaA_object_emit_signal:286: Trying to emit unknown signal 
'marked'
    W: awesome: signal_object_emit:239: Trying to emit unknown signal 'marked'

(probably an oversight in 65825bdd2264673391c305769642b1b31dc7831c).

Marking has been removed partly in 4ff51d5189a27c1d4501cfa3bd2423e9b2235c8d and 
ee1a3f24d78b5dfb67de5473cb55a5f468000b27.

I have noticed that marks had been removed from the default configuration, but 
I think it's a useful feature and therefore started with re-adding the 
callbacks that change the client's border, when marked (removed in 
ee1a3f24d78b5dfb67de5473cb55a5f468000b27):

    -- Hook function to execute when marking a client
    client.connect_signal("marked", function (c)
        c.border_color = beautiful.border_marked
    end)

    -- Hook function to execute when unmarking a client.
    client.connect_signal("unmarked", function (c)
        c.border_color = beautiful.border_focus
    end)

Since beautiful.border_marked still exists (in the default theme), I think 
re-adding those to the default config would make sense anyway?

4ff51d5189a27c1d4501cfa3bd2423e9b2235c8d removed:

`awful.key({ modkey }, "t", awful.client.togglemarked),` and a function to move 
all marked clients to a new tag (via modkey-shift-F1..F9).

This could be provided by default also, by either using the marked or current 
client in the current function for these shortcuts.

"modkey + t" however is now used for toggling the clients on-top flag.
There could be either a new default, or something commented out.


Awesome 3.5.2


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

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.

Reply via email to