On 7/31/08, Filippo Erik Negroni <[EMAIL PROTECTED]> wrote:
> Hi All,
>
> I noticed the code in dwm uses unsigned int for positive counters of
> memory arrays instead of size_t.
> Is there a particular reason you don't use size_t in order to convey
> that you are using that quantity as a counter of
Works like a champ! Here is my script setup (please let me know if I
can improve anything):
.xinitrc:
--
...
rmdir /tmp/dwm-bar-script-lock
dwm-statusbar &
dwm-launch
dwm-statusbar:
--
#!/bin/bash
#Incrementing numbers are just for testing.
LOCK=/tmp/dwm-bar-script-l
Thanks, that's interesting.
Hi All,
I noticed the code in dwm uses unsigned int for positive counters of
memory arrays instead of size_t.
Is there a particular reason you don't use size_t in order to convey
that you are using that quantity as a counter of memory space?
--
Cheers,
Filippo
@pancake :
> I dont see any point for having a function called
> "dwmiinoinfiniteloop"
Well this function is necessary, I didn't know how to call it,
though its name is relevant... If you don't like its name feel free
to change it but I won't. The important thing is that it does its job.
I
Hi all and pancake !
This is the dwmii.c file containing the dwmii layout with the
instructions to make it work !
@pancake :
> I dont see any point for having a function called
> "dwmiinoinfiniteloop"
Well this function is necessary, I didn't know how to call it, though
its name is relevan
On 7/30/08, Kurt H Maier <[EMAIL PROTECTED]> wrote:
> static const char *barcmd[] = { "/path/to/script > /path/to/pipe", NULL };
SHCMD("/path/to/script > /path/to/pipe") macro should be used there
(so the '>' is interpreted by the shell)
Maybe you could not run the script in the loop, and instead trigger it
when you activate the bar. Something like this:
static const char *barcmd[] = { "/path/to/script > /path/to/pipe", NULL };
...
static Key keys[] = {
{ MODKEY, XK_b, spawn, {.v = barcmd
Thanks for the suggestion. I tried it out by wrapping the FD readin
block with if(showbar) and it suppressed the output of the while loop
to the dwm bar.
However, to test it out I put an incrementing value in the while block
of my dwm wrapper script and when I re-enable the bar, the value seems
to
On Wed, 2008-07-30 at 13:14 +0200, QUINTIN Guillaume wrote:
> Hi all,
>
> This is the DWMII layout for DWM 5.1. It is a layout in the dwm way this
> time ! The only modification is within the Client struct and holds in 11
> chars : "int dwmii;\n". This modification prevents from having a more
>
On 7/30/08, QUINTIN Guillaume <[EMAIL PROTECTED]> wrote:
> The only modification is within the Client struct and holds in 11
> chars : "int dwmii;\n". This modification prevents from having a more
yes the dwm config.h api is that powerful :)
i'd put all the layout code in a separate file though,
Hi all,
This is the DWMII layout for DWM 5.1. It is a layout in the dwm way this
time ! The only modification is within the Client struct and holds in 11
chars : "int dwmii;\n". This modification prevents from having a more
complex algorithm and more lines of code. The last release of my layou
2008/7/30 Alex Matviychuk <[EMAIL PROTECTED]>:
>> There were also some minor changes to config.h, please use diff(1)
>> when upgrading your 5.0.1 config.h in order to prevent bugs.
>
> How do I map togglemax? Is it still around?
Indirectly, Mod1-m and then Mod1-space
Note, I decided to handle til
13 matches
Mail list logo
