aumatic liminal state that pervades among our relatives within
society. But as
for me I attribute this to Big Pharma's lucrative motive, not legal
summons which
I've seen cases of while at the ward.
Absolutely no morality is inherent in the "law" just because it's the
law.
Precisely. Legal is not necessarily moral.
Sylvain Saboua
right. A lot of diagnoses are abusive, esp. when considering
the prevalent
traumatic liminal state that pervades among our relatives within
society. But as
for me I attribute this to Big Pharma's lucrative motive, not legal
summons which
I've seen cases of while at the ward.
Absolutely no morality is inherent in the "law" just because it's
the law.
Precisely. Legal is not necessarily moral.
Sylvain Saboua
--
Sylvain Saboua
's all. You may read more about my personal journey :
https://www.saboua.xyz/UNIX.html
Sylvain Saboua
What a gallon of fresh air !
Did you try CRUX?
I've heard of it but there's few chances I'd ever come back from
(Open)BSD to Linux.
See the playlist referenced in my blog
mmer yet – theory is easy, practice is hard.
But I wish some day I reach the level where I can contribute.
That's all. You may read more about my personal journey :
https://www.saboua.xyz/UNIX.html
Sylvain Saboua
On Sat, Apr 04, 2020 at 03:19:13PM +, sylvain.bertr...@gmail.com wrote:
> For such basic command line, I should have connected to the xserver unix
> socket
> and should have sent directly the request.
Done (no xcb lib) then fixed. Same location on the web.
regards,
--
Sylvain
suckless in its context. Disregard it.
sorry,
--
Sylvain
ations are turning this global
switch on.
cheers,
--
Sylvain
k" with "One Compilation Unit" projects?
I know it is a bit annoying because it requires some pre-processor plumbing for
identifier names in order to avoid collisions in the one and only C global
namespace.
--
Sylvain
grapheme codepoint.
For instance the french letter 'è' won't be 1 codepoint anymore, but 'e' + '`'
(I don't recall the n11n order), namely a sequence of 2 codepoints.
I am a bit scared because software like ncurses, lynx, links, vim, may use the
abominations of software we discussed earlier to handle all this.
--
Sylvain
on of the "official" libicu (don't let me start on
harfb...): they all deserve a rube goldberg award.
--
Sylvain
For many projects, you can use the "One Compilation Unit" way: one root source
file
for one end result (shared lib/module/exe/etc).
The source tree is static and code selection happens with the C preprocessor.
--
Sylvain
Hi,
Out of the blue: I recently did switch from the "compiled" version of
youtube-dl to the use of it's raw code straight from the git repository,
because it felt starting significantly faster.
(nobody should have to use youtube-dl to get the video/dash url)
--
Sylvain
allocated for this, and if there are any
french citizens among suckless aware people who would like to join the party,
do not hesitate to get in touch with me.
regards,
--
Sylvain
Hi,
Coded the first iteration of a lil suckless-ish terminal audio file player
based on ffmpeg and alsa. Ofc, it's taylored for my needs. Might be of use to
some in suckless community.
It's here: https://repo.or.cz/nyanmp
--
Sylvain
one?
--
Sylvain
Hi,
When I run dota2, the game, in "desktop friendly fullscreen" when I alt-tab out
and back the borders are drawn again and I have to re-enable the "desktop
friendly fullscreen" in dota2.
fullscreen is ok with mplayer though.
anyone?
--
Sylvain
On Fri, Dec 20, 2019 at 08:47:18AM +0100, Laslo Hunhold wrote:
> ... Slock does not have pam implemented ...
REALLY?!!! How is this even possible? pam is amazing! pam is beautiful!
pam makes coffee!
--
Sylvain
On Wed, Dec 18, 2019 at 06:23:03PM +0600, Enan Ajmain wrote:
> ...
> ... /etc/pam.d folder ...
> ...
pam? paaam? PAAM?? Really?
--
Sylvain
loser look at
fontconfig code... jezus... no wonder this generate hate (Keith!! What did you
do)
I had to keep the dependency on that c++ pile of crap which is gperf though
(Bjarn!! What did you do!!!)
--
Sylvain
Just tested with a vte based terminal with noto mono regular, no rendering pb.
Then now it is sure, something is slightly wrong somewhere.
--
Sylvain
am still ?
--
Sylvain
digging out freetype/ttf demons?
--
Sylvain
ocks. And a rendering override is the
proof something is wrong somewhere :
- freetype ?
- typographic encoding of monospace otf/ttf fonts for those glyphs ?
I don't want to dig up nasty demons though.
--
Sylvain
what is the bottom of this, anyone?
--
Sylvain
ones are still massive compared to). There
are several orders of magnitude in between.
--
Sylvain
I have also the receiving part but the code is quite older:
https://rocketgit.com/user/sylware/lnanosmtp I just did a bit of refactoring
for the "1 compilation unit" suff and some updating (I personally use it on
aarch64). As I did explain, gogol did a fine job at pushing me coding all that.
--
Sylvain
organized crime where you have microsoft/apple (irony).
regards,
--
Sylvain
motion to suckless format.
--
Sylvain
y too rich syntax of C:
- one loop statement: #define loop for(;;)
- no enum.
- try to avoid qualifiers (const...).
--
Sylvain
l parser is simple (assuming you
> go against the RFC and only support UTF-8 like a sane
> person).
I'll parse UTF-8 (in theory) JSON to generate C code: short lived
process-->don't care about memory management.
1 - parse the JSON into a C friendly structs graph
2 - parse that graph to generate some C code.
--
Sylvain
suckless alternative to harfbuzz without
the same amount of resource than google??
--
Sylvain
Hi,
After xml, json.
Do you know of a light json parser lib? Or json seeming being very simple,
better write a parser directly?
I have libjq from the jq command line, but this is quite a beast and don't think
it fits anymore in the suckless frame.
--
Sylvain
cripts like arabic/korean/thai to give you an idea on how far
it can go and expect worse if you want to go global support.
--
Sylvain
On Tue, May 21, 2019 at 08:27:48PM +0200, Daniel Cegiełka wrote:
> https://releases.linaro.org/archive/13.05/components/toolchain/gcc-linaro/4.7/
It was based on 4.7.3 and included the arm64/aarch64 branch. There is gcc 4.7.4
and it seems the aarch64 branch is more recent.
--
Sylvain
is actually dead (6 years) or
not
working. If I am wrong, it would be good news for aarch64/arm64 bootstrapping
from C (namely you would not need a x86* system to build the stuff).
--
Sylvain
"register allocator" through brain f*cked
templates (like gcc inline asm). You keep it internal and it follow the
evolution, if any, of the "register allocator". And no need to keep the
template syntax forever for each assembler... As you said, it would probably
require QBE involvement in some way.
--
Sylvain
icense.
That said, C GUI toolkits: I know of GTK+ and EFL. But their SDKs are insane as
it is the norm now with "mainstream" open source software (and it's getting
worse as time goes by).
--
Sylvain
uthors are fine with it, (asm->plain and simple C, or
C11->simpler C).
I really need to check Quentin's QBE again.
What you do is great work, keep going while real life let you.
regards,
--
Sylvain
s context, those who add complexity to syntax which does increase
the near absolute metric of "technical cost" (not to mention the "human
factor"), _they_ have to justify themselves. I am tired too... to remind all
the time those basics to people I should not remind anything, just like you.
--
Sylvain
ve no idea of what
significant features a simple computer language like C brings on top of raw
assembly and why it is doing too much already.
--
Sylvain
on
> of thinking your restrictions to the end.
In suckless context, this is near an insult. I don't need to loose too much of
my time with such human being, and I won't. Let them code amazing-ly
abstracted c++52 or python12 or viper7 code... but if it could be on msdn where
it's more appropriate...
--
Sylvain
God! I barely did notice we were the first of April... and I was surprised to
see ideas
so much remote from suckless stated here.
Got me guys. I fell for it.
doh!
--
Sylvain
Nice April Fool's joke.
--
Sylvain
Dear David,
You are of the type of human being I, genuinely, sort of dislike. Namely a
syntax
kludge and excessive abstraction lover.
Your first sentence is already an insult to "suckless" people: "won't you write
in assembly next time?"
--
Sylvain
llars were not able to code an alternative dynamic DOM engine
(they only got their hands on w3c html specs...). Only one way to go, noscript
with basic (x)html.
--
Sylvain
dge and declaring
variable anywhere.
--
Sylvain
s.opengroup.org/onlinepubs/9699919799/functions/V2_chap02.html#tag_15_02_02
On this web page, when I tried to get the definition of the [CX] code related
to the _t suffix I got a nice page complaining javascript is nowhere to be
found, I had to use google to find the right page... bad omens.
--
Sylvain
On Tue, Mar 26, 2019 at 08:56:07PM +0100, Kurt Van Dijck wrote:
> I agree with most of your arguments
>
> > * use sized types: u8 u16 i64 float32 etc... you can use the C
> > preprocessor to fix that, but in some case, as a good tradeof (for
> > instance in
> > "object oriented C code"), add
On Tue, Mar 26, 2019 at 08:37:18PM +0100, Quentin Rameau wrote:
> > * do not use enum (hard rule)
> > * do not use typedef (hard rule)
> > * use sized types: u8 u16 i64 float32 etc... you can use the C
> > preprocessor to fix that, but in some case, as a good tradeof (for
> > instance in
> > "
"corporate code")
I certainly forget a ton of things, and tradeofs have to be done case by
case. Nothing is set in stone. We all do mistakes.
Keep in mind that we are all different, then we will draw "lines" not in the
same way, but there is an absolute value which is true for all: the "technical
cost" of your code and your deps (SDKs included).
--
Sylvain
s python (kind of slowly replacing perl5, and I remember being a
python fan boy a decade ago... pepe hands), and the one before was the
"javascript web" and I quickly did figure out the c++/java/similar bullshit a
long time ago.
--
Sylvain
l
can disable the use of libharfbuzz and go basic roman script support).
I did code a long time ago an alternative of libharfbuzz, C API, that hardcoded
for
roman like scripts. Then I could use GTK+ without the stench of c++. They
probably did change their API, that enough to break my code.
--
Sylvain
.
Yep, I guess lex/yacc (then GNU flex/GNU bison) are inappropriate, I even would
generalize to they do not belong in "suckless".
--
Sylvain
e, I am puzzled by line/column
tracking, which can be tricky (for instance C preprocessor/compiler accurate
line/column tracking with line-return escaping with lex/yacc??)
Maybe it's not an implementation issue of lex and yacc... they may actually
be _not_ suckless at all. Any thoughts on this?
--
Sylvain
On Tue, Feb 05, 2019 at 05:01:57AM -0500, Martin Tournoij wrote:
> as soon as you start doing more than printing raw strings.
Not even raw strings, but raw "lines" (\n added by echo).
My 3c.
--
Sylvain
On Mon, Feb 04, 2019 at 08:03:56PM +0100, Laslo Hunhold wrote:
> echo -n -e "GET / HTTP/1.1\r\nHost: localhost\r\n\r\n" | \
"My 2c": I would prefer shell "printf" than "echo -n -e"
--
Sylvain
the main "definitive no-nos" was the ABI xD. And now we have
C APIs for c++ abominations like llvm and harfbuzz :(
--
Sylvain
did notice some "XML entities" in the XML source file (the char escaping
sequence: &;) though, don't believe they are critical.
regards,
--
Sylvain
On Sat, Feb 02, 2019 at 01:20:16PM -0500, Sean MacLennan wrote:
> Json? Not sure what you need the xml parser for... but does it have to
> be xml?
Unfortunately, the source file is utf-8 xml.
--
Sylvain
Hi,
I am looking at xml parsers.
I am about to go expat, but I am wondering if there are some interesting
alternatives I did miss?
--
Sylvain
On Sat, Feb 02, 2019 at 07:46:37AM -0500, Greg Reagle wrote:
> I completely agree with these criticisms of C.
I don't like C.
Its syntax is way too rich already.
C is by far the most reasonable "compromise", namely, which "suckless".
--
Sylvain
fool
around with such thingies.
regards,
--
Sylvain
tware perfectly alien to
what "suckless" strives to become.
What "suckless" is, is that hard to understand??? Or is this the result of an
accute lack of perspective? And I though we were finally protected from those
cunning trolls. I was wrong.
Oh God! And I am feeding this beast right now...
--
Sylvain
all on this mailing list for french citizens who want to
join.
--
Sylvain
Hi,
Guys, why bothering with an obvious troll fed on google go propaganda???
come on...
--
Sylvain
developer level. I
am getting a lawer and I am going to start to deal with this issue first with
the french administration. Noscript browser devs may have to team up in order
to get something in official html standard, which is "edited" by M$ and gogol
ppl. A noscript/light browser profile, something like that.
--
Sylvain
ok at what did microsoft with pdf 2.0 at ISO too.
Expect POSIX to add significant technical cost over time, like ISO, ANSI,
the most monstruous being the w3c.
--
Sylvain
e still on suckless???
--
Sylvain
One is enough. As it should have been for loop constructs.
--
Sylvain
king, "the less the better",
"divide and conquier", "small is beautiful", "and NO, comfort/portability
brought by high level and very expensive script engines does not justify
anything".
--
Sylvain
27;s why when I
deal with mainstream distros (usually I have my own), I favor devuan and not
debian, which is free from systemd.
--
Sylvain
On Thu, Dec 27, 2018 at 12:56:29AM +1300, Martin Tournoij wrote:
> ... AFAIK all compilers accept // these days ...
Preprocessor. I guess having 2 ways to define comments is not significant,
then better stick to one and the historical one.
--
Sylvain
On Thu, Dec 27, 2018 at 12:51:08AM +1300, Martin Tournoij wrote:
> On Wed, Dec 26, 2018, at 13:23, Sylvain Bertrand wrote:
> > Since llvm is pure c++ madness and gcc is still far from being one:
> > gnu gcc sucks less than clang/llvm. yes, GNU gcc sucks less than BSD
> > clan
e same amount of c++ cr*p than
clang/llvm.
How can you be so wrong? Wake up and un-wash your brain!
On 12/25/18, Cág wrote:
> Sylvain Bertrand wrote:
>> ???
>> clang/llvm is a c++ abomination: a massive pile of c++ cr*p. If you
>> dislike the GNU make, wait to read the c++ code
???
clang/llvm is a c++ abomination: a massive pile of c++ cr*p. If you
dislike the GNU make, wait to read the c++ code of cmake, the build
system of clang/llvm, not to mention ninja (something in the horrible
python3 or python2). I am into llvm code right now, and I feel like
working in an asylum:
izers", aka compilers. We have
the same nasty ppl there.
Keep in mind that coding "proprietary programs" in the open source source world
means coding a huge kludge/bloat software (if possible with complex syntax
computer languages).
regards,
--
Sylvain
eme cluster" in unicode terminology) you want.
If those "characters" are actually mapped to only 1 font glyph, well, they were
probably filtered out for some reasons (could be missing from the font files)
or it's a "limitation".
--
Sylvain
On Sat, Sep 29, 2018 at 03:46:36PM +0200, Laslo Hunhold wrote:
> On Sat, 29 Sep 2018 12:59:15 +
> sylvain.bertr...@gmail.com wrote:
>
> Dear Sylvain,
>
> > mmmh... for the reason I stated before, the fonts files will probably
> > be more and more NFD normalizati
I have not gone into the details of the EGC boundaries algorithm, but I'm really
curious to how the unicode consortium algorithm can know that an unicode point
is an EGC terminator without looking the next unicode point.
--
Sylvain
normalization
> as much as you probably think.
Agreed, as far as I can think of, with my limited knowledge on unicode, it
would be kind of required only for the EGC renderer in order to help the
"rendering correctness".
Additionally, ill EGCs with tons of combining code points (less than 32 though)
will likely be "compressed" by this normalization.
> ...
regards,
--
Sylvain
uot; boundaries
computation, it seems that everything we need is there, but it raises many
more questions, for instance:
- how this finite state machine is resilient to garbage data?
- can we locate "extended grapheme cluster" boundaries on non normalized
unicode?
- can we normalize on the fly a "extented grapheme cluster"?
- etc...
regards,
--
Sylvain
(i.e. no more mutt with non ascii email, no more lynx with non ascii only web
page...). A zero-i18n framework. In the case of wayland st: own
ascii bitmap fonts and own font renderer.
- suckless gets its own unicode handling code (libicu/freetype+harfbuzz
look-alike implementation).
--
Sylvain
, a little thing on the side, librsvg is being rewritten in... rust
(The rust bootstrap SDK is a joke, have a look at it) xD
--
Sylvain
xml-ized with font specific augmented information.
--
Sylvain
al would render 'e' then the 'combining accent'
and
not 'é' as it should be. Or maybe unicode does contain "transactional code
points" already.
:(
--
Sylvain
an app which is a thin suckless wrapper around a
huge pile of ... You know what: st would be better of being a thin wrapper
around libvte then, because it would be even thiner.
:(
--
Sylvain
many
written, unicode supported, languages is harfbuzz.
A line is to be drawn here.
--
Sylvain
range, or to be sure the x11 font names have orthogonal encoding
fields.
To prepare such font list, you may have to split font files per
encoding/unicode range, something like that.
--
Sylvain
Hi,
It seems my previous message did not went through.
I was showing how mlterm reach this goal:
in a config file, in a table in the config header for st, a mapping
between style(bold/non-bold)/unicode range to a font name.
--
Sylvain
t (probably libinput), will have to be dealt by the terminal code
itself. I have native x11 on my system only because I play video games and
xwayland with vulkan/GL hardware acceleration is far from optimal last time I
checked.
--
Sylvain
On Sun, Sep 23, 2018 at 09:22:00AM -0700, AR Garbe wrote:
> On Sun, 23 Sep 2018 at 06:37, wrote:
> > st has a clean wayland fork? BTW, suckless wayland compositor, still too
> > early
> > to talk about it?
And has st a wayland backend or fork?
--
Sylvain
land fork? BTW, suckless wayland compositor, still too early
to talk about it?
--
Sylvain
of this?
--
Sylvain
Oh! I forgot to insist on the fact that I'm not against an _optional_ const
attribute, but with different semantics than the current const keyword.
--
Sylvain
id things" over time.
Like "enum" or "typedef", all that should not be in C, as more than one loop
keyword. But this is off-topic.
--
Sylvain
ink kmod and/or libblkid).
But I digress from the topic.
--
Sylvain
On Fri, Sep 22, 2017 at 02:25:54PM +0200, Laslo Hunhold wrote:
> On Fri, 22 Sep 2017 06:00:51 +
> sylvain.bertr...@gmail.com wrote:
>
> Hey Sylvain,
>
> > go is not suckless.
> >
> > Should have written your PoC using simple C.
>
> what are you talkin
d write it in PL/SQL if that solved the problem at hand.
I invite you to browse the archive since this is a recurent matter.
No, go is not suckless, neither is pl/sql.
--
Sylvain
go is not suckless.
Should have written your PoC using simple C.
--
Sylvain
uld steal your private keys and could have a
root kit on your system or in the man-in-the-middle, all that to sh*t your
digital presence.
(zomby computer are common)
--
Sylvain
1 - 100 of 288 matches
Mail list logo