ut there really is no 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
On Tue, 27 Sep 2016 15:42:01 +0200
Silvan Jegen 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
On Tue, 27 Sep 2016 14:49:14 +0200
Martin Kühne wrote:
> Why not carry the IRC back into the name and make it binoirc or even
> birco?
Or maybe just birc. :D
--
FRIGN
uot; might be nice memorable names for the
frontend interface (and easy to type).
Cheers
FRIGN
[0]: http://bino3d.org/
--
FRIGN
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
ut alternatives that come as close as possible, namely giftcards.
Cheers
FRIGN
--
FRIGN
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
n the interpretation is equal everywhere and 9base
is quite easily portable.
Cheers
FRIGN
--
FRIGN
sions in life.
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
ause they are too "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
ems 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
On Tue, 6 Sep 2016 09:37:09 +0200
Kevin Michael Frick wrote:
> GCC, probably. Which sucks, but if Hitler warns you not to step of a
> cliff, you don't ignore his warning because he is Hitler.
I can understand the point you are making about GCC, but what is wrong
with Hitler? /s
--
FRIGN
inary 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
e and only available for x86 and x86_64 linux?
Cheers
FRIGN
--
FRIGN
ulti-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
On Thu, 1 Sep 2016 11:46:36 -0300
Marc Collin 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
> by FRIGN, 2015-01-29.
>
>
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
ng Xorg-related, not sure
> what else could be important.
I can not reproduce it here.
Cheers
FRIGN
--
FRIGN
Gentoo allows me to only
compile in things into Abiword I really need. There are a lot of things
not compiled into my version, making it rather lightweight. :)
Cheers
FRIGN
--
FRIGN
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
--
FRIGN
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
ript to call 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
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
re. 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
On Thu, 11 Aug 2016 16:07:29 +0200
Paul Menzel wrote:
Hey Paul,
> Are there plans to get release 0.7(?) out, so that users, not
> building from repository, but from release source archives, can
> profit from them?
just FIY, Christoph tagged a 0.7 release a few minutes ago[0].
Chee
tch. 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
Hub or at suckless.org?
In the latter case, I would favor keeping it on suckless.org having
given it more thought.
Cheers
FRIGN
--
FRIGN
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
oes main development 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
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
script
> (?) 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
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
mirror, with all its 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
it's only a building block.
Of course, runit is only a service manager. But runit+sinit+misc is a
whole other story.
Cheers
FRIGN
--
FRIGN
On Wed, 3 Aug 2016 12:23:41 +0100
Dimitris Papastamos 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
already set up Let's Encrypt on
2f30.org, maybe he can help set things up for suckless.org. :)
Cheers
FRIGN
--
FRIGN
pted traffic. 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
encrypted, 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
white
> #70849d:#2e3a67
> black
> 1.0
>
>
> #aa
> #808488:#303438
> black
> 0.5:0.9:0.1
>
>
Yuck! XML config? No thanks!
--
FRIGN
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
han 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
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
On Mon, 1 Aug 2016 17:13:14 +0200
Ton van den Heuvel 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
illing to
> edit the patch to fix that, let me know.
just update your patch and attach it to your response.
Cheers
FRIGN
--
FRIGN
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
> key presses kind of defeats the point of having asterisks at all. You
> might as well just make the flag not show any text at all which is a
> pretty common alternative for Unix password prompts anyway.
my suggestion prints as many asterisks as there are runes. try it
out! :D
Cheers
FRIGN
--
FRIGN
a
static char asterisks[BUFSIZ];
and do a
drw_font_getexts(drw->fonts, text, cursor, &curpos, NULL);
memset(asterisks, '*', curpos / 8);
asterisks[curpos / 8] = '\0';
drw_text(drw, x, 0, w, bh, lrpad / 2, asterisks, 0);
or something along the lines.
Cheers
FRIGN
--
FRIGN
On Mon, 25 Jul 2016 13:07:23 -0700
Eric Pruitt wrote:
> Again, no one is saying passwords should be sent via the command line.
> Look at the patch. It uses stdout just like vanialla dmenu.
Ah I see, thanks for clearing up that part. Now, what do the other
people think about it?
Cheers
... | 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
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
(Gender studies, psychology, social
sciences, ...), it is easy to spot someone who just talks but doesn't
deliver in a real scientific context, to which I also count software
development, especially language theory.
Show some code or you'll have lost all the respect by many people here,
inclu
ody sense and gives a false sense of
security.
Cheers
FRIGN
--
FRIGN
ought 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
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
y 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
g.h is your responsibility, that's it.
--
FRIGN
On Mon, 18 Jul 2016 13:49:16 +0300
Cág wrote:
Hey Cág,
> If someone knows what goes wrong or workarounds, please tell.
did you try recompiling with "-fPIC"?
Cheers
FRIGN
--
FRIGN
still potentially useful or should it go away?
You can put it into historical as a whole, as it's too old.
--
FRIGN
uckless.org tools, 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
On Tue, 12 Jul 2016 17:42:37 -0800
Britton Kerin 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
On Tue, 12 Jul 2016 17:42:37 -0800
Britton Kerin 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
t
for each 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
he non-git version here on the ml.
Cheers
FRIGN
--
FRIGN
other naming scheme.
Cheers
FRIGN
--
FRIGN
ght 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
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
st 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
On Fri, 17 Jun 2016 10:01:43 -0800
Britton Kerin 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
On Fri, 17 Jun 2016 09:14:30 +0200
Anselm R Garbe wrote:
> The date should always be updated, whenever the patch is touched in some way.
Agreed.
@All:
Check out http://st.suckless.org/patches/, I changed the patch name formatting
as discussed here.
Cheers
FRIGN
--
FRIGN
dy 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
'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
t 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
;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
tches. Should 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
r
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
and without doubt, they can hinder you. But does it really justify
just handrolling your own, unportable, probably buggy libc?
Cheers
FRIGN
--
FRIGN
. Use
> it! Please...
> 9. Oh wait, I see that you have strcpy(), 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
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
? :P
Cheers
FRIGN
--
FRIGN
ts 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
eccomp.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 execing, risking a TOCTTOU-problem.
Cheers
FRIGN
--
FRIGN
ere 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
ting 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
On Tue, 31 May 2016 18:42:45 +0100
Chris Down 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)?
Cheers
FRIGN
--
FRIGN
much simpler, much
more secure (de/encoder) and actually gets the grapheme handling right.
Stay tuned.
Cheers
FRIGN
--
FRIGN
ut 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
valuable contributions to this project,
it's just you to make the decision.
Cheers
FRIGN
--
FRIGN
On Tue, 17 May 2016 08:54:19 +0200
Anselm R Garbe wrote:
> I can only imagine he meant sandy which I would suggest to be removed asap.
Yes sorry, I meant sandy.
--
FRIGN
ess.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
sistent across suckless
tools, and thus, breaking it breaks consistency.
Cheers
FRIGN
--
FRIGN
o maintain it with few people.
--
FRIGN
ors 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
ow to run the passwd tool or set up my .ssh dir myself.
> (tinycore yay)
I'm not too sure about this point. On some distributions, you can literally
brick your hardware by writing to some /sys variable as root.
I don't feel comfortable running Chromium as root to be honest, it's
like unprotected sex with a street hooker.
> 18. text editors: ed, perhaps vi
vi is fine.
Cheers
FRIGN
--
FRIGN
t least not more 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
your shell and it should work.
Cheers
FRIGN
--
FRIGN
he vis editor alone is enough bloat in the suckless
repositories.
Cheers
FRIGN
--
FRIGN
of expression.
Everybody has the 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
sizes. Go may have
comparable speeds to C and makes a lot of things much simpler to do, but
the binary sizes are just insane. They'll address this in the upcoming
versions, but until then, I'll not look into it.
Once the day comes and a hello world goes below 800K (400K, ...), I'll
definitely look into it.
Cheers
FRIGN
--
FRIGN
uckless-ml is the wrong place to promote Rust and there is
a lot of material on the web on why Rust cannot in any way be
considered even barely a suckless language.
C is definitely not suckless either, especially when it comes
to UB, but it's probably the language with least suck and
highest
gt; you're the only community I know which are committed to what you do.
read K&R 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 #2f30.
Cheers
FRIGN
--
FRIGN
1 - 100 of 739 matches
Mail list logo
