You will be glad to know I will be removing `float` support. It didn't
provide the performance boost I was hoping for.
On Wed, 13 Dec 2017 08:31:21 +0100
Mattias Andrée wrote:
> I'm not convinced, but since you guys disagree I will not implement this.
>
> On Wed, 13 Dec 2017 00:45:18 +
> Ri
I'm not convinced, but since you guys disagree I will not implement this.
On Wed, 13 Dec 2017 00:45:18 +
Richard Ipsum wrote:
> I lack community standing to really comment on this.
>
> That being said, as a casual observer it seems fairly obvious to me
> that what you're proposing is totall
I lack community standing to really comment on this.
That being said, as a casual observer it seems fairly obvious to me
that what you're proposing is totally anathema to suckless philosophy.
On Tue, Dec 12, 2017 at 02:49:34PM +, Mattias Andrée wrote:
> It may look insane on the surface level
On Tue, Dec 12, 2017 at 09:51:08AM +0100, David Demelier wrote:
> The current code has a fixed margins of 2, add a compile time tunable to
> edit it
> ---
> config.def.h | 1 +
> dwm.c| 2 +-
> 2 files changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/config.def.h b/config.def.h
>
It may look insane on the surface level. I am not commited to changes
listed in the TODO, most of them are just ideas that I will have to evalute
later whether they are worth implementing. Although I'm pretty convinced
most of them are good.
From: isabella p
On Tue, 12 Dec 2017 11:13:10 +
Chris Down wrote:
> Since now both would be stored in the git history, this would
> actually increase the size of the repo, so I'm not sure I see the
> benefit of this.
Smaller release tarballs?
--
Laslo Hunhold
don't you realize how insane the whole thing is?
On 12/12/17, Mattias Andrée wrote:
> Perhaps I should clarify that (1) the goal would be to have blind-tee
> (and blind-cat if that is implemented) to use already existing functions
> that sends data between two files, and have these functions use
Since now both would be stored in the git history, this would actually increase
the size of the repo, so I'm not sure I see the benefit of this.
Perhaps I should clarify that (1) the goal would be to have blind-tee
(and blind-cat if that is implemented) to use already existing functions
that sends data between two files, and have these functions use splice
when possible), so would only use tee explicitly, not splice, and (2)
a 1 hour long b
When I rendered a video, tee used 100% while the other process was
basically at 0, for more than 50% of the rendering time. I ran it multiply
times to verify that is was correct. An alternative solution would be
to use sockets, but that would require changes to the shell. Optimising
tee seems like
bullshit
On 12/4/17, g...@suckless.org wrote:
> commit d8aa45da86d1128149fd7ab6ac3725bf8e88a1b1
> Author: Mattias Andrée
> AuthorDate: Mon Dec 4 22:35:59 2017 +0100
> Commit: Mattias Andrée
> CommitDate: Mon Dec 4 22:35:59 2017 +0100
>
> update todo: tee is too slow
>
> Signed-o
The current code has a fixed margins of 2, add a compile time tunable to
edit it
---
config.def.h | 1 +
dwm.c| 2 +-
2 files changed, 2 insertions(+), 1 deletion(-)
diff --git a/config.def.h b/config.def.h
index a9ac303..3dbbfa5 100644
--- a/config.def.h
+++ b/config.def.h
@@ -2,6 +2,7 @
12 matches
Mail list logo
