reason to have
it. It's a gimmick, but maybe you can give really compelling reasons to
include it.
> Otherwise i haven't used it much but seems to be just as expected, a
> gnu comparable cli. I need to update my scripts and then i will start
> using this instead of busybox.
I'm glad you like it! If you find any bugs, please report them!
Cheers
FRIGN
--
FRIGN <d...@frign.de>
On Tue, 27 Sep 2016 15:42:01 +0200
Silvan Jegen <s.je...@gmail.com> wrote:
> As far as I know that is a way to show appreciation for talks at
> universities (at least in Switzerland).
Same in Germany. :)
--
FRIGN <d...@frign.de>
On Tue, 27 Sep 2016 14:49:14 +0200
Martin Kühne <mysat...@gmail.com> wrote:
> Why not carry the IRC back into the name and make it binoirc or even
> birco?
Or maybe just birc. :D
--
FRIGN <d...@frign.de>
t;bioc" or "binoc" might be nice memorable names for the
frontend interface (and easy to type).
Cheers
FRIGN
[0]: http://bino3d.org/
--
FRIGN <d...@frign.de>
Hello fellow hackers,
the videos of this year's suckless conference in the webm format are
online. You can view them on the conference page[0].
Cheers
FRIGN
[0]: http://suckless.org/conferences/2016
--
FRIGN <d...@frign.de>
ink
about alternatives that come as close as possible, namely giftcards.
Cheers
FRIGN
--
FRIGN <d...@frign.de>
de in in no time (even faster than your cc card
number) and it's all good.
If you send an item back because you didn't like it, Amazon will
automatically put the credit back on your gift card balance.
Cheers
FRIGN
--
FRIGN <d...@frign.de>
ly
portable per-se, given the interpretation is equal everywhere and 9base
is quite easily portable.
Cheers
FRIGN
--
FRIGN <d...@frign.de>
If you end up configuring your Kernel yourself and remove everything
you don't need in the first place (including all drivers with BLOBs),
your compilate won't contain BLOBs as well.
With best regards
FRIGN
[0]: https://www.shellcheck.net/
--
FRIGN <d...@frign.de>
oo "difficult", but because they just eat
up time, unless you spit out makefiles in 10 seconds each. Rewriting
the build systems for other projects and maintaining them along the
line is borderline insane.
With best regards
FRIGN
--
FRIGN <d...@frign.de>
nly
seems to be popular in very tight spaces.
I know, PDF is hard to render and the renderers are bloated, but we
have to live with it. We used to piss on people for sending us docx's
instead of pdf's, now we need to change the format we're working on
again? No thanks.
--
FRIGN <d...@frign.de>
with Hitler? /s
--
FRIGN <d...@frign.de>
d reduce binary size
> way further than this custom libc thing, BTW.
or instead I just use sane programs who don't deploy NiH-solutions.
And it would be much more work than that. All the socket stuff is very
far away from how Posix describes it.
Cheers
FRIGN
--
FRIGN <d...@frign.de>
software when
it's unportable and only available for x86 and x86_64 linux?
Cheers
FRIGN
--
FRIGN <d...@frign.de>
nd multi-codepoint case conversions.
This all depends on my redevelopment of libutf that is currently in the
works, but given some personal things I have not gotten around to it in
the last few months and thus development kinda halted.
Cheers
FRIGN
--
FRIGN <d...@frign.de>
On Thu, 1 Sep 2016 11:46:36 -0300
Marc Collin <marc.coll...@gmail.com> wrote:
Hey Marc,
> The missing brackets on paste.c that I talked about on the last
> message revealed something else to me.
>
> It was introduced in commit cdbc0d50356a0f7e0dd5755e3c46593a947cf029
>
initrc is a mess and stages an environment before
starting dwm.
Try to set up a minimal working example in a clean environment, e.g.
try running gentoo and write the .xinitrc yourself. Your lack of
control over this environment will forever hinder us from finding the
cause of this issue.
Cheers
FRIGN
--
FRIGN <d...@frign.de>
attempt at debugging anything Xorg-related, not sure
> what else could be important.
I can not reproduce it here.
Cheers
FRIGN
--
FRIGN <d...@frign.de>
common,
same with the other formats in the office suite.
So it's sufficient to dump the bloated mess LibreOffice is and use
Abiword and Gnumeric. At least from the latter I know it is also
heavily used at CERN, which explains why it even has superior
data analysis tools than Excel itself.
Cheers
FRIGN
fice ain't slim, and people
> keep sending me word documents :/
I can recommend Abiword and Gnumeric whole-heartedly. They are
_relatively_ slim and are great substitutes for Word and Excel
respectively.
Cheers
FRIGN
--
FRIGN <d...@frign.de>
l all the
necessary dependencies in the openrc context. It is definitely
questionable how easy this job is if I wanted to solve the same problem
using systemd-mount.
Cheers
FRIGN
--
FRIGN <d...@frign.de>
t; of the farbfeld image format I have to highlight
here that all the tools on suckless.org assume the sRGB color space,
which, to be fair, is not a big sin given X11 and the entire ecosystem
does not encourage color management of this dimension.
Cheers
FRIGN
--
FRIGN <d...@frign.de>
ay, just
to make sure. It also makes it simpler to apply patches to it, as soon
as patches are released for a stable version (I'm on it).
Cheers
FRIGN
--
FRIGN <d...@frign.de>
e a few minutes ago[0].
Cheers
FRIGN
[0]:http://git.suckless.org/st/commit/?id=6e79e8357ed1987a7f7a52cc06249aadef478041
--
FRIGN <d...@frign.de>
witch. We all
know that OpenBSD is much further on the convergence line towards an
ideal operating system for server and desktop applications than Linux
and its messy userland.
Cheers
FRIGN
--
FRIGN <d...@frign.de>
development
happen on GitHub or at suckless.org?
In the latter case, I would favor keeping it on suckless.org having
given it more thought.
Cheers
FRIGN
--
FRIGN <d...@frign.de>
at stali relies on.
I've been wondering for a while what you think the problem is with
OpenBSD. Wouldn't it make more sense to somehow start an initative in
OpenBSD to promote static linking there?
Cheers
FRIGN
--
FRIGN <d...@frign.de>
evelopment happen? On GitHub or
here on git.suckless.org?
> You see the code and the comment. What else do you need?
A description in the actual commit what the underlying problem was? Is
it too much to ask?
Cheers
FRIGN
--
FRIGN <d...@frign.de>
zens of image
formats.
The conversion can happen in-situ and is generally no problem, as any
image viewer program has to do that anyway to get the raw "bits". The
overhead of first writing those bits into a farbfeld stream is pretty
minimal.
Cheers
FRIGN
--
FRIGN <d...@frign.de>
> (?) that converts all arguments to temporary farbfeld files and passes
> them to sxiv.
Yes exactly. That's how sent[0] does image handling and it works very
well!
Cheers
FRIGN
[0]: http://tools.suckless.org/sent/
--
FRIGN <d...@frign.de>
ak farbfeld.
farbfeld is damn stable and one can easily use the 2ff tool to convert
from all possible image formats with the help of imagemagick.
Look at sent on how it is handled there.
Cheers
FRIGN
--
FRIGN <d...@frign.de>
implied
beauty[1]. Do I really need to dig around github now to see what the
commit fixed?
What do you think?
Cheers
FRIGN
[0]:http://git.suckless.org/sxiv/tree/
[1]:http://git.suckless.org/sxiv/commit/?id=53a72c7b657d9dc3347d9d68e0b9a00773efe732
--
FRIGN <d...@frign.de>
building block.
Of course, runit is only a service manager. But runit+sinit+misc is a
whole other story.
Cheers
FRIGN
--
FRIGN <d...@frign.de>
On Wed, 3 Aug 2016 12:23:41 +0100
Dimitris Papastamos <s...@2f30.org> wrote:
> I did set it up for the first few months but then was too lazy to
> renew it.
What about Hiltjo then? He set it up for codemadness.nl.
--
FRIGN <d...@frign.de>
et up Let's Encrypt on
2f30.org, maybe he can help set things up for suckless.org. :)
Cheers
FRIGN
--
FRIGN <d...@frign.de>
ic. In my opinion, the best
would be just to allow self-signed certificates in browsers, but Let's
Encrypt comes close enough.
Cheers
FRIGN
--
FRIGN <d...@frign.de>
ted, with all benefits of it.
> If you would contribute, you would have SSH access. A onion
> service might be a consideration, to add something similar to
> »security« as an access method for suckless.org.
Yes, an onion service would be really cool.
Cheers
FRIGN
--
FRIGN <d...@frign.de>
> 20
>
> white
> #70849d:#2e3a67
> black
> 1.0
>
>
> #aa
> #808488:#303438
> black
> 0.5:0.9:0.1
>
>
Yuck! XML config? No thanks!
--
FRIGN <d...@frign.de>
other than to play around with it. It's a
horrible mess and the wayland devs expect us to boil the ocean without
any clear benefits at hand.
Cheers
FRIGN
--
FRIGN <d...@frign.de>
t; barely larger than the current X11 version's git tip (though the
> wayland version depends on wld[4]).
How can you compare the two? You need a third-party library (wld) to
get shit done. Just wait down the line how much of a fucking mess we
are going to have!
Cheers
FRIGN
[0]: https://www.youtube.com/watch?v=Ux-WCpNvRFM
--
FRIGN <d...@frign.de>
l use Linux for graphic design and photography. I can't
even imagine how much of a mess it will be if every single compositor
has to think of ways for color management, handle joysticks, don't fuck
things up and so on. It's a huge mess!
Cheers
FRIGN
--
FRIGN <d...@frign.de>
On Mon, 1 Aug 2016 17:13:14 +0200
Ton van den Heuvel <tonvandenheu...@gmail.com> wrote:
> Fallback fonts can already be configured through Fontconfig, why does
> st need separate functionality for this?
Because Fontconfig is a load of crap!
--
FRIGN <d...@frign.de>
aren't willing to
> edit the patch to fix that, let me know.
just update your patch and attach it to your response.
Cheers
FRIGN
--
FRIGN <d...@frign.de>
stumpled upon this issue. hmm, difficult. Still, you need
to find a simpler solution for your purpose, even though I don't think
it'll ever get merged into mainline.
Cheers
FRIGN
--
FRIGN <d...@frign.de>
. try it
out! :D
Cheers
FRIGN
--
FRIGN <d...@frign.de>
implify
it. Why not go with a
static char asterisks[BUFSIZ];
and do a
drw_font_getexts(drw->fonts, text, cursor, , NULL);
memset(asterisks, '*', curpos / 8);
asterisks[curpos / 8] = '\0';
drw_text(drw, x, 0, w, bh, lrpad / 2, asterisks, 0);
or something along
people think about it?
Cheers
FRIGN
--
FRIGN <d...@frign.de>
rd piped like
$ dmenu ... | example
I really would like to see if "example" actually exists. Does it
really make sense to do that and is it even safe?
Cheers
FRIGN
--
FRIGN <d...@frign.de>
oody
answer to my question already. I want to see a real example, a real
program that actually _exists_ which takes passwords on the command
line, or an example where you use dmenu to enter passwords in some
"dynamic" context not observable to me at the moment.
Cheers
FRIGN
--
FRIGN <d...@frign.de>
ect by many people here,
including me, if there ever was one.
Cheers
FRIGN
--
FRIGN <d...@frign.de>
this doesn't make any bloody sense and gives a false sense of
security.
Cheers
FRIGN
--
FRIGN <d...@frign.de>
There are some things thought that I'd like to see in mainline, e.g.
removing borders of the window when there's only one window in the
current tag.
Cheers
FRIGN
--
FRIGN <d...@frign.de>
On Wed, 20 Jul 2016 13:37:01 +0200
Christoph Lohmann <2...@r-36.net> wrote:
> Sorry for the late answer, I had to save the world.
Care to elaborate?
--
FRIGN <d...@frign.de>
> independently in a very straight-forward way. The rest stays the same.
Yeah, this looks very good! Any comments from the other fellow?
Else I'll just pull it into the wiki asap.
Thanks for your hard work Eon!
Cheers
FRIGN
--
FRIGN <d...@frign.de>
ing. What you configure in
config.h is your responsibility, that's it.
--
FRIGN <d...@frign.de>
On Mon, 18 Jul 2016 13:49:16 +0300
Cág <c...@riseup.net> wrote:
Hey Cág,
> If someone knows what goes wrong or workarounds, please tell.
did you try recompiling with "-fPIC"?
Cheers
FRIGN
--
FRIGN <d...@frign.de>
s patch
> still potentially useful or should it go away?
You can put it into historical as a whole, as it's too old.
--
FRIGN <d...@frign.de>
ols, especially those wrt to
the Xlibs, which might run but can turn out to be quite ineffective
(as you have shown here).
I wondered about these CPU-spikes in dwm as well.
Cheers
FRIGN
--
FRIGN <d...@frign.de>
On Tue, 12 Jul 2016 17:42:37 -0800
Britton Kerin <britton.ke...@gmail.com> wrote:
>
If patches turn out to be unportable to HEAD without huge problems or
work, the best approach is to try to contact the author and move the
patches to historical/.
Cheers
FRIGN
--
FRIGN <d...@frign.de>
On Tue, 12 Jul 2016 17:42:37 -0800
Britton Kerin <britton.ke...@gmail.com> wrote:
>
Oh, and I almost forgot:
Don't use git-format-patch for the git patches. Just pipe the output of
git diff to a file.
Maintaining those git-format-patches is too much work.
Cheers
FRIGN
--
FRIGN <d...@frign.de>
ach single page. Don't be scared to flood wiki@ with
commits.
Each page should receive a style-cleanup as well, and
both can be combined easily.
I hope this helps. :)
Cheers
FRIGN
[1]: http://dwm.suckless.org/patches/current_desktop
[2]: http://dwm.suckless.org/patches/alpha
[3]: http://dwm.suckless.org/patches/fancycoloredbarclickable
--
FRIGN <d...@frign.de>
e to agree to the non-git version here on the ml.
Cheers
FRIGN
--
FRIGN <d...@frign.de>
git-patches, which followed the other naming scheme.
Cheers
FRIGN
--
FRIGN <d...@frign.de>
but I thought I'd ask one more time if
> we're sure we're happy with this naming scheme.
Yeah, let's do this! :) Think about the users and don't worry too much.
Cheers
FRIGN
--
FRIGN <d...@frign.de>
y spend time on fixing
the patches (like Matthias Schoth, Jochen Sprickerhof, Eric Pruitt,
Ayrton, myself and others). They actually do real work instead of
phantasizing here on this ML.
Cheers
FRIGN
--
FRIGN <d...@frign.de>
patch section just needs an overhaul analogous to the st
patch section had. End of story.
It's already difficult enough getting people to maintain their
patches now, let alone in some git environment.
Cheers
FRIGN
--
FRIGN <d...@frign.de>
On Fri, 17 Jun 2016 10:01:43 -0800
Britton Kerin <britton.ke...@gmail.com> wrote:
>
the right format is
--.diff
for release patches. Now do some work and change it to that...
Use the st patches as reference, they are correct and have been
agreed upon.
Cheers
FRIGN
--
FRIGN <d...@frign.de>
:)
To everybody else: Stop painting pictures here on the ml and actually
help improve the patches. In the end, only the one who does something
gets to decide how it's done.
Cheers
FRIGN
--
FRIGN <d...@frign.de>
atch
you don't see which one is the newest one.
As a last point of thought: The shorthash gives no info at all. It could
either be a broken patch against HEAD or not, however, pasting the
hash in the name somehow claims more than it does, and gives less
information to 99% of people.
Cheers
FRIGN
--
FRIGN <d...@frign.de>
here is: using the date of
the "update" is the best and easiest heuristic. you see with one look
if a git-patch is relatively old or new.
Cheers
FRIGN
--
FRIGN <d...@frign.de>
king stuff here won't change much, just change suckless.org/wiki.md
> so that most of the people can see it.
Yes, very good point. I'll look into it.
Cheers
FRIGN
--
FRIGN <d...@frign.de>
ld we remove them or provide them for older
versions of dwm?
In my opinion, there is no reason for this legacy stuff. The
dwm-patch section is already cramped enough, a cleanup would
be pretty helpful.
What do you guys think?
Cheers
FRIGN
--
FRIGN <d...@frign.de>
be a simpler
approach to this whole (or)deal, however, I really don't see
so much that would justify tipping over all existing code built
on top of the libc and starting anew.
Cheers
FRIGN
--
FRIGN <d...@frign.de>
egards, Posix has issues
and without doubt, they can hinder you. But does it really justify
just handrolling your own, unportable, probably buggy libc?
Cheers
FRIGN
--
FRIGN <d...@frign.de>
you just don't use it.
> Alrighty then.
> And that was just what I saw in lnanosmtp.c. And I didn't check the
> protocol.
It's just a big fucking mess there is no need for. Sylvain, sit down
again, use a fucking libc so fucking BSD users and other arch users
can fucking use your shit. Then we can talk.
Cheers
FRIGN
--
FRIGN <d...@frign.de>
kill,
what is the big deal? You'll find a libc in any system really, and
even for crazy embedded cases, you could just create a statically
linked binary.
Cheers
FRIGN
--
FRIGN <d...@frign.de>
and wondered: what the hell is ulinux? :P
Cheers
FRIGN
--
FRIGN <d...@frign.de>
op of UDS and implements a very simple messaging
protocol.
> I personally find the idea of polluting our source code for this
> appalling and suggest the wiki.
We also had the idea yesterday on IRC to let the OpenBSD guys know
and just help them apply the patch to the st port.
Cheers
FRIGN
--
FRIGN <d...@frign.de>
dge-seccomp.c
> TLDR: pledge on Linux implemented in terms of SecComp.
As far as I know, SecComp has some weird behaviour when you exec.
Other than pledge, which "resets" the permissions, SecComp keeps
the limitations.
Because of that, the only way would be to somehow disable Seccomp
before ex
s. However, there always will
remain a bad aftertaste given it's an OS-dependent solution.
However, to be fair, I think OpenBSD is the best OS out there.
Cheers
FRIGN
--
FRIGN <d...@frign.de>
starting with #ifdefs is a long road and can lead to hard
to read code ("ifdef-hell")
2) the usage-stats of OpenBSD don't justify the inclusion
unfortunately.
Cheers
FRIGN
--
FRIGN <d...@frign.de>
On Tue, 31 May 2016 18:42:45 +0100
Chris Down <ch...@chrisdown.name> wrote:
Hey Chris,
> This is with a heavily patched dwm 6.0[0] and LibreOffice 5.0.6.3.
can you also reproduce this bug with vanilla dwm (git upstream!) and
the latest stable version of LibreOffice (5.1.2.2)?
Chee
libutf which is much simpler, much
more secure (de/encoder) and actually gets the grapheme handling right.
Stay tuned.
Cheers
FRIGN
--
FRIGN <d...@frign.de>
d never welcome this, but I'm glad to make an exception for
pledge(). Use the define trick
#ifndef __OpenBSD__
int pledge(const char *promises, const char *paths[]) { return 0; }
#endif
though.
Cheers
FRIGN
--
FRIGN <d...@frign.de>
tch.
I'm positive you can make valuable contributions to this project,
it's just you to make the decision.
Cheers
FRIGN
--
FRIGN <d...@frign.de>
On Tue, 17 May 2016 08:54:19 +0200
Anselm R Garbe <garb...@gmail.com> wrote:
> I can only imagine he meant sandy which I would suggest to be removed asap.
Yes sorry, I meant sandy.
--
FRIGN <d...@frign.de>
ls.suckless.org/slock/patches/pam_auth
I'm not a big fan of PAM, but it's fine as an external patch.
The document was not found because the wiki hadn't been updated. I did
it and now it's accessible.
Cheers
FRIGN
--
FRIGN <d...@frign.de>
are consistent across suckless
tools, and thus, breaking it breaks consistency.
Cheers
FRIGN
--
FRIGN <d...@frign.de>
ntain it with few people.
--
FRIGN <d...@frign.de>
made to run ncurses
> applications.
suckless strives for perfection in an environment where most people
are illiterate.
We are like a book club in india, but just because we literate while
the majority is illiterate it doesn't mean that we are doing something
wrong. We may not be a big force, but at least we're heading in
the right direction.
--
FRIGN <d...@frign.de>
re than Debian, which sucks ass).
If you depend on Linux-stuff, I'd take a look at Gentoo again.
For rolling releases, you can go with -CURRENT on OpenBSD.
Cheers
FRIGN
--
FRIGN <d...@frign.de>
$ wmname LG3D
in your shell and it should work.
Cheers
FRIGN
--
FRIGN <d...@frign.de>
I think the vis editor alone is enough bloat in the suckless
repositories.
Cheers
FRIGN
--
FRIGN <d...@frign.de>
choice to either choose a language which gives you
a big range of freedom of expression or use one that dictates how you
express yourself in tight margins.
Cheers
FRIGN
--
FRIGN <d...@frign.de>
...), I'll
definitely look into it.
Cheers
FRIGN
--
FRIGN <d...@frign.de>
st simplicity while giving the most power to the developer.
Cheers
FRIGN
--
FRIGN <d...@frign.de>
ng and
> you're the only community I know which are committed to what you do.
read K and read suckless code. :)
Join in on IRC (#suckless on OFTC or #2f30 on freenode) and ask questions
if you like. #suckless is a strict development channels, so newbie
questions are honestly more welcome on #2f
://tools.suckless.org/farbfeld
--
FRIGN <d...@frign.de>
hand I'm very open if others correct
me and give me an example where one or multiple of the other
formats are still in use today.
Keep up the good work!
Cheers
FRIGN
--
FRIGN <d...@frign.de>
sion
of flash, then I would look deeper into it, however, keep two
things in mind:
1) The normal flash (the non-chrome one) is dead.
2) YouTube offers an HTML5-player.
3) Flash is not open source software.
Cheers
FRIGN
--
FRIGN <d...@frign.de>
1 - 100 of 695 matches
Mail list logo
