On 7/25/17, Silvan Jegen wrote:
> Hi
>
> On Wed, Jul 26, 2017 at 7:32 AM, Michael Forney
> wrote:
>> Over the past couple weeks, I implemented a ninja-compatible build
>> tool in C. It is much simpler and smaller than ninja and seems to
>> perform at least as well.
>>
>> https://github.com/michae
Hi
On Wed, Jul 26, 2017 at 7:32 AM, Michael Forney wrote:
> Over the past couple weeks, I implemented a ninja-compatible build
> tool in C. It is much simpler and smaller than ninja and seems to
> perform at least as well.
>
> https://github.com/michaelforney/samurai
>
> It has all the features I
just more technical debt
thanks for your disservice.
Hi all,
Over the past couple weeks, I implemented a ninja-compatible build
tool in C. It is much simpler and smaller than ninja and seems to
perform at least as well.
https://github.com/michaelforney/samurai
It has all the features I care about, apart from gcc -MD header
dependency parsing which
That's right. No new build system is suggested.
Let me suggest a small poll:
1 What build systems do you consider as most suckless?
2 Generating Makefile from a shell script: it sucks, it's acceptable
or it's rather suckless?
It would be great if you give some explanation for your answer.
I thin
On Tue, 25 Jul 2017 11:59:59 +0200
Laslo Hunhold wrote:
> [...] In my opinion, a bug report on how "Uselessfont stops working
> under dwm" is helpful, [...]
correction: is _not_ helpful
--
Laslo Hunhold
On Mon, 24 Jul 2017 22:13:36 -0500
Joshua Haase wrote:
Hey Joshua,
> I do think a good issue tracker is needed and would be willing to
> contribute on september 2-3 (although maybe in a different time zone:
> [UTC-6]).
>
> As for useless bug reports, a good cure would be to give access only
> t
