LOGIN / SIGN UP

#191 making window events pass along a window ID

Reported by: gibbon Assigned to: pekdon
Phase: release-0.1.11 Component: configuration
Type: task Status: closed
Priority: 3: Medium
Watchers:

Attachments

Description

If a window ID was passed along with every event, you could do something like this in ~/.pekwm/mouse:

Client {

    Enter = "Any Any" { Actions = "Exec command -blarg WindowID" }

}

That way, a command that can be run on a specific window could be called automatically whenever the cursor enter a window, for instance.

2010-02-20

15:27:13 changed from open to closed
15:27:13

Commited to git, closing the task.

12:14:17 attached 0001-Added-CLIENT_WINDOW-and-CLIENT_PID-to-environment-fo.patch
12:14:17

Now unsetting the environment, required unsetenv compat code.

09:51:09

Good catch there, will make it static and take a client as parameter then.

09:46:31

Please make a small change to ActionHandler::actionExec(.). In case of !client unset the environment variables, so that old values don't get reused.

2010-02-19

22:33:25 attached 0001-Added-CLIENT_WINDOW-and-CLIENT_PID-to-environment-fo.patch
22:33:25

Patch for setting CLIENET_WINDOW and CLIENT_PID attached.

22:32:45 to release-0.1.11
22:32:45 changed from new to open
22:32:45 changed from Andreas to Claes Nästén
22:32:45

OK by IOError if the patch doesn't introduce to many changes.

18:45:15

Currently this dynamic menus set the environment variables CLIENT_WINDOW and CLIENT_PID when mapping, could be done in the environment but variables are expanded while parsing.

I guess doing a simple wrapper like this:

 #!/bin/sh
 
 /path/to/real/command -blarg $CLIENT_WINDOW

Together with support for setting it in the environment should work, need to implement support for it in the exec code though if OK by IOError.