ChanServ changed the topic of #kisslinux to: Unnofficial KISS Linux community channel | https://kisscommunity.org | post logs or else | song of the day: http://yewtu.be/fG0xfGZSmR4
illiliti has joined #kisslinux
ehawkvu[m] has quit [Read error: Connection reset by peer]
ehawkvu[m] has joined #kisslinux
ehawkvu[m] has quit [Read error: Connection reset by peer]
ehawkvu[m] has joined #kisslinux
ehawkvu[m] has quit [Read error: Connection reset by peer]
ehawkvu[m] has joined #kisslinux
gully has quit [Ping timeout: 256 seconds]
illiliti has quit [Quit: leaving]
illiliti has joined #kisslinux
<illiliti> libevdev and mtdev are included because upstream doesn't have them
<illiliti> wlroots, libinput, sway are patched
ehawkvu[m] has quit [Read error: Connection reset by peer]
ehawkvu[m] has joined #kisslinux
ehawkvu[m] has quit [Read error: Connection reset by peer]
ehawkvu[m] has joined #kisslinux
ehawkvu[m] has quit [Read error: Connection reset by peer]
ehawkvu[m] has joined #kisslinux
ehawkvu[m] has quit [Ping timeout: 256 seconds]
ehawkvu[m] has joined #kisslinux
ehawkvu[m] has quit [Read error: Connection reset by peer]
ehawkvu[m] has joined #kisslinux
ehawkvu[m] has quit [Read error: Connection reset by peer]
ehawkvu[m] has joined #kisslinux
<testuser[m]> Hi
ehawkvu has joined #kisslinux
Guest8 has quit [Quit: Client closed]
ehawkvu has quit [Ping timeout: 256 seconds]
mahmutov has quit [Ping timeout: 240 seconds]
gully has joined #kisslinux
an3223 has quit [Ping timeout: 240 seconds]
an3223 has joined #kisslinux
ehawkvu has joined #kisslinux
gully has quit [Ping timeout: 256 seconds]
ehawkvu has quit [Read error: Connection reset by peer]
mahmutov has joined #kisslinux
an3223 has quit [Ping timeout: 240 seconds]
an3223 has joined #kisslinux
ejjdhfjsu has joined #kisslinux
illiliti has quit [Read error: Connection reset by peer]
illiliti_ has joined #kisslinux
illiliti_ is now known as illiliti
mahmutov has quit [Ping timeout: 256 seconds]
ejjdhfjsu has quit [Ping timeout: 272 seconds]
fturco has joined #kisslinux
<soliwilos> illiliti: Nice! Would any project using libinput and wlroots need to be patched as well?
<illiliti> no, just rebuilt
<illiliti> but if project directly depends on libudev, then yes
<illiliti> see sway for example
<illiliti> btw, wlroots patch also supports mcf's libinput
<illiliti> BUT, his libinput is linux-only and doesn't have support for quirks
<soliwilos> Great work. :)
<soliwilos> I will give it a try.
<illiliti> do it!
fturco has quit [Quit: rcirc on GNU Emacs 27.2]
gully has joined #kisslinux
gully has quit [Ping timeout: 256 seconds]
gully has joined #kisslinux
Rohan has joined #kisslinux
Rohan has quit [Ping timeout: 240 seconds]
mahmutov has joined #kisslinux
<testuser[m]> It has been many years since I shipped a memory bug in C++. It is just not a real worry for me.
ejjdhfjsu has joined #kisslinux
illiliti has quit [Quit: leaving]
gully has quit [Ping timeout: 256 seconds]
gully has joined #kisslinux
midfavila has joined #kisslinux
<midfavila> afternoon everyone.
<testuser[m]> Hi
sad_plan has joined #kisslinux
Rohan has joined #kisslinux
gully has quit [Ping timeout: 256 seconds]
ehawkvu has joined #kisslinux
<ehawkvu> slinux
<sad_plan> is not shuf part of posix?
<midfavila> not afaik
<midfavila> dd bs=2 count=1 if=/dev/random 2>> /dev/null | od - | sed -ne 's& *& &gp' | cut -d ' ' -f2
<midfavila> this gets you a random number in a portable fashion
<midfavila> you can use that with ls and sed to grab random elements of a list
<midfavila> kind of a hackjob but it does work - I use it in my media player script
<sad_plan> thought as much. that was an immensly long command to replace shuf :') but I was initially using it to randomly select a file in a directory
<midfavila> :P
<midfavila> you can reference my fpm script if you want - I use it to do exactly that
<midfavila> obligatory shilling
<sad_plan> nice
<midfavila> I really need to rewrite it to use my rand one-liner instead of the entire pipeline
<testuser[m]> Vro use awk
<midfavila> i don't know awk yet lmao
<sad_plan> I was initially just making a script to randomly select a wallpaper, and then set the wallpaper, in a loop, so it changed wallpaper every 5 minutes or so
<midfavila> awk would probably be marginally better
<midfavila> you could also potentially use bc
<sad_plan> Im not that familiar with awk, but I can look into it
<sad_plan> thought bc was only for math?
<sad_plan> atleast thats what Ive used it for
<midfavila> my bc implementation comes with a library that implements rand(), among other things
<midfavila> just not sure if it's posix
<sad_plan> arithmatic math or w/e it was called
<sad_plan> aah
<sad_plan> I dunno
<midfavila> bc can be used for most floating-point calculations
<midfavila> but it has some really unfortunate limitations
<midfavila> for example, you can't have non-integer exponents
<sad_plan> nice. I was going to make a math script for some bs at work, and figured Id use bc
gully has joined #kisslinux
<midfavila> unfortunately it doesn't look like bc's standard library includes random number generators
<sad_plan> just curious, why are you writng full paths to everything? i mean, sed, wc etc
<sad_plan> intead of just writing wc -l
<midfavila> because I wrote fpm in about fifteen minutes at 3AM a while ago
<midfavila> and I don't make very good decisions when I'm tired
<midfavila> i'm sure I had a reason originally
<sad_plan> lol ok :p
<midfavila> a lot of my scripts in that repo haven't been touched in months
<midfavila> i'll probably rewrite them in rc soon
<midfavila> ...oh, you know what it was? i bet that was when I still bothered to use aliases in my shrc
<sad_plan> I see. Im just about starting to accumalate some scripts of my own. I really enjoy writing them once I sortof got the hang of writing scripts in general :p
<sad_plan> why rc?
<sad_plan> aaah, perhaps
<midfavila> because rc is the most efficient and useable job control language I've found to date
<midfavila> usable? w/e
<midfavila> but yeah, rc can run in under 100kb of memory when statically linked on my system
<sad_plan> but are they affected by your aliases? I never though they were really. unless you specify them in the scripts themselves
<sad_plan> thats nice though. hows the speed? I mean, compared to other fast shells like ash, or dash i.e.
<sad_plan> any difference at all?:p
<midfavila> sh usually requires a few hundred, if not a couple megs
<midfavila> and honestly it's been a while - I vaguely recall having conflicts where aliases or oneliners or *something* was giving me trouble
<midfavila> as for speed, idk, i'd say rc is reasonably quick. i haven't done anything particularly intensive in it yet since I'm still learning the language
<sad_plan> I actually did a speedtest for several shells once, and I didnt really find much difference that I would notice on a day to day basis anyway. even with bash vs dash :p
<midfavila> maybe I'll have it recursively evaluate some factorials as a benchmark or something, compare that to dash/bash/etc
<midfavila> actually that'd be interesting to see considering rc doesn't have arithmetic evaluation
<sad_plan> ah ok. ive been curious about rc for some time, but I dont think Im going to start mess with it just yet tbh :p
<midfavila> fair enough
<midfavila> there's a variant of it called es with support for metaprogramming and garbage collection if you want something a little more powerful to mess with
<midfavila> it doesn't have TCO though, unfortunately
gully has quit [Ping timeout: 256 seconds]
<sad_plan> I dont think I need anything in particular. I run dash as my sh, but zsh interactive shell. I have been planing to do a throurough test of oksh/mksh or something, as both are abit more slim to say the least..
<midfavila> yeah zsh is elephantine
<sad_plan> I dunno what TCO is ybh :p
<midfavila> only bash is larger iirc
<midfavila> oh, tail-call optimization
<sad_plan> perhaps fish too.
<midfavila> if you write a function in a language that calls itself as the last thing it does, then the language can rewrite that as a loop internally
<midfavila> helps prevent stack exhaustion
<midfavila> mandatory in scheme, common in lisp, and gcc also supports it
<sad_plan> I just find some of the bells and whissles on zsh quite usefull, so ive just gotten used to to. Ive gotten a fairly ok workflow with it, so Im a bit reluctant to switch :p
<sad_plan> I see
<midfavila> i've heard that from a lot of people. never really got that about zsh tbqh
<midfavila> i stand by my belief that tab-completion for commands is a meme
<midfavila> i guess there's oh-my-zsh themes but like
<midfavila> use tput and hooks
<sad_plan> I mean, Ive got this cdr thing, where it stores your last 20 dirs you visited, so you can just type cdr 5, and itll just hop to the 5th dir you where. or you can skip using cd, and just type the directory instead of cd first.
<midfavila> oh, that's trivial to do in rc
<midfavila> you can just keep appending to a list
<sad_plan> the tab-completetion is what most people seem to enjoy the most, myself included
<sad_plan> perhaps it is
<sad_plan> if thats the case, my arguments for using zsh compared to other shells, falls apart rather quickly
<midfavila> (dir1), have cd be an alias that calls cd and prepends dir2, (dir2 dir1), then so on and so forth
<midfavila> (dir3 dir2 dir1), (dir4 dir3 dir2 dir1), and so on
<midfavila> you could even access the elements of the list directly
<sad_plan> I also use vi mode alot, or a vim buffer really. spawns a vim buffer so you can edit the command, and save and hit enter to run it
<midfavila> so cd $dirs(5)
<sad_plan> hm, doesnt sound so complicated when you put it that way
<midfavila> it's not
<midfavila> rc is *extremely* simple
<sad_plan> I like simple
<sad_plan> hence me using KISS :p
<midfavila> >uses zsh
<midfavila> pretty sus ngl
<sad_plan> lol
<midfavila> but yeah rc is nice. it's very consistent
<sad_plan> oh, and while on the topic of 'sus' appearantly that meme distro 'amongOS', appearantly added crypto miners into the distro :p
<midfavila> good
<testuser[m]> Bruh that was for their html site and it was a dummy
<midfavila> oh, another thing that I really like about rc: you can conjugate lists, and if the size of the lists are unequal, it's distributive
<sad_plan> was it? I thought it was the actuall distro. I sortof just read the headlines tbh
<sad_plan> nice
<sad_plan> gotta try rc some day
<testuser[m]> Headlines are poz
<testuser[m]> Always check contents
<midfavila> just don't scrool newsfeeds
<sad_plan> I kinda know that, I just scrolled passed it while doing something else tbh :p
gully has joined #kisslinux
ehawkvu has quit [Remote host closed the connection]
gully has quit [Ping timeout: 256 seconds]
soliwilos has quit [Quit: nyaa~]
soliwilos has joined #kisslinux
ehawkvu[m] has quit [Ping timeout: 272 seconds]
ehawkvu[m] has joined #kisslinux
progenyx has quit [Quit: progenyx]
progenyx has joined #kisslinux
progenyx has quit [Client Quit]
progenyx has joined #kisslinux
ehawkvu[m] has quit [Read error: Connection reset by peer]
ehawkvu[m] has joined #kisslinux
gully has joined #kisslinux
Rohan has quit [Quit: Quit]
gully has quit [Ping timeout: 256 seconds]
gully has joined #kisslinux
mobinmob has joined #kisslinux
ehawkvu[m] has quit [Read error: Connection reset by peer]
ehawkvu[m] has joined #kisslinux
ehawkvu[m] has quit [Ping timeout: 256 seconds]
ehawkvu[m] has joined #kisslinux
ehawkvu[m] has quit [Read error: Connection reset by peer]
ehawkvu[m] has joined #kisslinux
gully has quit [Ping timeout: 252 seconds]
Rohan has joined #kisslinux
sad_plan has quit [Quit: zzz]
sad_plan has joined #kisslinux
Rohan has quit [Ping timeout: 250 seconds]
Digit has joined #kisslinux
mobinmob has quit [Quit: Connection closed for inactivity]
sad_plan has quit [Quit: nyaa~]
gully has joined #kisslinux
gully has quit [Ping timeout: 256 seconds]
ehawkvu[m] has quit [Ping timeout: 256 seconds]
ehawkvu[m] has joined #kisslinux
ehawkvu[m] has quit [Read error: Connection reset by peer]
ehawkvu[m] has joined #kisslinux
ehawkvu[m] has quit [Read error: Connection reset by peer]
ehawkvu[m] has joined #kisslinux
ehawkvu[m] has quit [Read error: Connection reset by peer]
ehawkvu[m] has joined #kisslinux