I was trying to compile ii against musl, and I found that it seems ii.c is
missing include declaration namely
#include
otherwise fd_set is undefined and most likely select() too. I do not know how
it compiles with gnu libc, or maybe this is problem with musl and select.h
should be included from so
Hi,
* Edgaras [2012-08-14 11:40]:
> I was trying to compile ii against musl, and I found that it seems ii.c is
> missing include declaration namely
> #include
> otherwise fd_set is undefined and most likely select() too. I do not know how
> it compiles with gnu libc, or maybe this is problem with
On Mon, Aug 13, 2012 at 4:54 PM, Andrew Hills wrote:
> On Sun, Aug 12, 2012 at 8:23 PM, Uriel wrote:
>> This whole topic is so silly, just use a language that doesn't need
>> any of this nonsense, like Go.
>
> Are you insinuating that Go is the best choice for all projects,
For all projects, obv
Hey everyone,
I got a new monitor recently and started to work with
two screens and dwm.
No problem at all. Everything works fine, except for one
_really annoying_ issue with dmenu and dwm.
If no windows are open on the current tag of one screen
and I switch to this screen&tag using the keyboard
< top
On Tue, Aug 14, 2012 at 9:01 AM, v4hn wrote:
> Hey everyone,
>
> I got a new monitor recently and started to work with
> two screens and dwm.
> No problem at all. Everything works fine, except for one
> _really annoying_ issue with dmenu and dwm.
>
> If no windows are open on the current t
On Tue, Aug 14, 2012 at 03:01:08PM +0200, v4hn wrote:
> Hey everyone,
>
> I got a new monitor recently and started to work with
> two screens and dwm.
> No problem at all. Everything works fine, except for one
> _really annoying_ issue with dmenu and dwm.
>
> If no windows are open on the current
On Tue, Aug 14, 2012 at 9:33 AM, Martti Kühne wrote:
>
> On Tue, Aug 14, 2012 at 03:01:08PM +0200, v4hn wrote:
> > Hey everyone,
> >
> > I got a new monitor recently and started to work with
> > two screens and dwm.
> > No problem at all. Everything works fine, except for one
> > _really annoying_
Hey all,
Recently on the Arch mailing list there has been much discussion of
different init systems. I was just wondering which init system, y'all
approve of. SysV or OpenRC pretty suckless and unix-y to me.
What do you think?
Calvin
That's a really good question!
Maybe, I already know what suckless thinks about SystemD.
--
Envoyé d'Archlinux
On Tue, Aug 14, 2012 at 01:36:55PM -0400, Calvin Morrison wrote:
> Hey all,
>
> Recently on the Arch mailing list there has been much discussion of
> different init systems. I was just wondering which init system, y'all
> approve of. SysV or OpenRC pretty suckless and unix-y to me.
>
> What do yo
On 14 August 2012 13:50, Kurt H Maier wrote:
> On Tue, Aug 14, 2012 at 01:36:55PM -0400, Calvin Morrison wrote:
>> Hey all,
>>
>> Recently on the Arch mailing list there has been much discussion of
>> different init systems. I was just wondering which init system, y'all
>> approve of. SysV or Open
first initiate sanity in your brain
On Tue, Aug 14, 2012 at 01:26:06PM -0400, Carlos Torres wrote:
> > [1]
> > https://github.com/mar77i/dwm-patches/blob/master/dmenumon/dmenumon.patch
>
> What happened to *arg?
>
> > [2] https://gist.github.com/3349298
>
pass NULL in config.h keys[], as an arg, it's needed to provide a common gr
There are dependency based init systems, should use mk for it.
net: 1
inetd: net
2: getty inetd
mk 2 # go to runlevel 2
# inetd crashes
mk 2 # bring it back to life
It would need some sort of procfs view with process names, where unlink
sends a term signal, and some extra features for
14 matches
Mail list logo
