On 18 April 2012 12:52, Connor Lane Smith wrote:
> On 18 April 2012 08:57, Arian Kuschki
> wrote:
> > for some time now, not sure how long, dwm changes the displayed tag when
> an
> > application is activated.
>
> The blame here is either with dwm or the application, depending on the
> way you l
> You need to separate the argument from the actual command like so:
>
> static const char *volinccmd[] = {"/home/olek/.bin/pavolume", "increase",
> NULL};
>
> Otherwise it would try to exec a script named "pavolume increase" in the
> folder "/home/olek/.bin" without any arguments.
Mea culpa :)
T
Greetings.
On Wed, 18 Apr 2012 13:41:39 +0200 "Galos, David"
wrote:
>
> I've fixed it to use no regex; only goto, loops and string.h stuff;
> attached is the patch.
Your proposed changes are applied. I still have to insist on checking
the right side of »end« to be checked for length.
On 18 April 2012 08:57, Arian Kuschki wrote:
> for some time now, not sure how long, dwm changes the displayed tag when an
> application is activated.
The blame here is either with dwm or the application, depending on the
way you look at it. Essentially, dwm supports the _NET_ACTIVE_WINDOW
EWMH c
On Wed, Apr 18, 2012 at 11:06:01AM +0200, Alexander Tanyukevich wrote:
> OK. But why my bindings in config.h doesn't work:
> [...]
> static const char *volinccmd[] = {"/home/olek/.bin/pavolume increase", NULL};
> [...]
You need to separate the argument from the actual command like so:
static cons
On Wed, Apr 18, 2012 at 11:06:01AM +0200, Alexander Tanyukevich wrote:
> >> or use xbindkeys to bind those keys, e.g.
> >
> > Or speckeysd.
>
> OK. But why my bindings in config.h doesn't work:
>
> #include "X11/XF86keysym.h"
> ...
> static const char *volinccmd[] = {"/home/olek/.bin/pavolume inc
>> or use xbindkeys to bind those keys, e.g.
>
> Or speckeysd.
OK. But why my bindings in config.h doesn't work:
#include "X11/XF86keysym.h"
...
static const char *volinccmd[] = {"/home/olek/.bin/pavolume increase", NULL};
static const char *voldeccmd[] = {"/home/olek/.bin/pavolume decrease", NUL
On 18 April 2012 09:57, Arian Kuschki wrote:
> Hi,
>
> for some time now, not sure how long, dwm changes the displayed tag when
> an application is activated. E.g. I click a link that is opened in an
> external program and that program comes into view even if its tag was not
> visible before. Dwm
Hi,
for some time now, not sure how long, dwm changes the displayed tag when an
application is activated. E.g. I click a link that is opened in an external
program and that program comes into view even if its tag was not visible
before. Dwm behaves like OS X now in this regard. Is this a bug or a