<midfavila-laptop>
oh, you were referring to wolfram. yeah, no, that's fair
<midfavila-laptop>
i didn't really like that part of it, nor that it's only available via the web
<acheam>
oh yeah not sagemath
<acheam>
well there is mathematica which is offline
<midfavila-laptop>
yeah but I somehow doubt it runs on KISS
<midfavila-laptop>
:v
<midfavila-laptop>
or on ARM for that matter, which is an eventual concern of mine
<acheam>
just a slight doubt that they dont have static binaries
<acheam>
ew sagemath is python
<midfavila-laptop>
and Fortran, and Ruby, and Common Lisp, and C, and C++, and JavaScript...
<midfavila-laptop>
...and R...
<midfavila-laptop>
fortunately it has an emacs interface
<midfavila-laptop>
so no need to use its gross web frontend
<noocsharp>
one of the first things i'm gonna do when my language is mature enough is to write a math library with number theory stuff
<noocsharp>
so i can dogfood by doing project euler problems
<midfavila-laptop>
that sounds like it would be fun
<midfavila-laptop>
i've considered giving PE a shot but I don't think I understand mathematics enough to be able to solve problems of any real complexity
<acheam>
imagine doing math for fun
<noocsharp>
project euler is an excellent way to learn new math
<noocsharp>
well some number theory at least
<bibliocar>
project euler is all math with a little programming thrown in.
<midfavila-laptop>
imagine literally being acheam
<midfavila-laptop>
and yeah I have no doubt in my mind that PE is an excellent resource. it's on my list, but I have so much other stuff to get through first
<noocsharp>
dilyn: bruh how
<dilyn>
idk god. make; ./npm a test (y, test) results in this output
<dilyn>
s/god/guy/
<noocsharp>
lol, `tr` hangs when i try that
<noocsharp>
down the rabbit hole we go
<testuser[m]>
Hi
<acheam>
hello
mahmutov has quit [Ping timeout: 256 seconds]
<noocsharp>
oh dilyn, you have to run npm init
<noocsharp>
i should document that in the help
<dilyn>
:V
<dilyn>
kekv
<dilyn>
mfw
<noocsharp>
and i should check for that whenever the program starts
<sad_plan>
/quit
sad_plan has quit [Quit: nyaa~]
<midfavila-laptop>
>mfw >>kekv >>>mfw
<dilyn>
you heard me
<midfavila-laptop>
>mfw I didn't
<midfavila-laptop>
what are you gonna do about it dilyn
<midfavila-laptop>
send me to the dean's office?
ella-0_ has joined #kisslinux
<noocsharp>
try now, see if you get the same error
ella-0 has quit [Read error: Connection reset by peer]
<dilyn>
indeed, npm init lets me create passwords
<dilyn>
can't seem to retrieve them tho:P
<noocsharp>
yes, i screwed up the check on the last commit
<noocsharp>
force pull
<dilyn>
"/usr/bin/npm[276]: here document `EOF' unclosed" lmao
<noocsharp>
what command does this happen on?
<noocsharp>
wait i'm an absolute idiot
<noocsharp>
those tabs were there for a reason
<noocsharp>
maybe i should test it locally before i push commits
<opalvaults[m]>
dilyn: I'll give this a try! I have a couple of keys that I need to manage so just looking for something so I'm not constantly putting in a password..
<opalvaults[m]>
dilyn: how do you like ksh? I've been looking for a more minimal interactive shell.
<dilyn>
it works very well for me! slower than dash, but feels nice and homey
<opalvaults[m]>
Is it lighter than mksh?
<opalvaults[m]>
I'll give it a shot :) ty for the rec
<dilyn>
i never tested mksh but I think someone in here has... don't remember who tho
<testuser[m]>
mksh doesnt work
<testuser[m]>
with kiss the package manager
<dilyn>
f
<testuser[m]>
It was cuz of some glob thing
<opalvaults[m]>
gotcha. I'd love to use KISS again. It's been a couple years since I've touched it. Is encryption of the root partition easier now? I know illiliti had an encryption package that was fairly prototypical
<dilyn>
it's gotten easier!
<dilyn>
though the documentation might still be lacking @illiliti
<opalvaults[m]>
Hm, sounds like a good opportunity to contribute!
<dilyn>
op_4 who's not here right now just got it up and running with FDE last week
<dilyn>
yeah he'd probably appreciate it! XD
<opalvaults[m]>
last question! can I compile Emacs on KISS? I used to only use vim but I've been a convert to evil+emacs. I know KISS is pretty anti-GNU so it wouldn't surprise me if it wasn't possible.
<noocsharp>
emacs is in the community repo
<testuser[m]>
U can do anything on anything
<opalvaults[m]>
testuser: *with enough effort
<opalvaults[m]>
noocsharp: cool! was this repo always separate from KISS?
<noocsharp>
dylan used oversee it, but he disappeared for a while, kiss community took over both the main and community repo, and when he came back, he took over the main repo
<noocsharp>
s/used/used to/
<opalvaults[m]>
ah! didn't realize he came back. took a much needed break from software I imagine. :)
<opalvaults[m]>
I figured he went the way of that Void Linux creator and disappeared into the wildnerness never to be seen again.
<noocsharp>
well he's been gone recently too, hasn't come back from that afaik
<noocsharp>
but he was also gone for the first half of 2020
<opalvaults[m]>
Haven't talked to illiliti in a while either. Last I heard they were dreading conscription into the Russian military.
<noocsharp>
2021*
<opalvaults[m]>
noocsharp: not surprising! Software can really suck you in from the real-world. Glad he's up to other things these days. also glad to see this IRC still active (although moved from freenode as I can see)
<opalvaults[m]>
I think since KISS follows a minimalist/essentialist philosophy I think it's inevitable that a lot of its users abide by those same tenants and take much needed departures from constant technology-use.
<opalvaults[m]>
I think that's what drew me to KISS linux in the first place. The only distro (seemingly still) that is both extremely usable and minimal.
<noocsharp>
usable is relative
<noocsharp>
if you had a different definition of usable you could go more minimal
<noocsharp>
i imagine most people use software that wouldn't allow them to get away with using KISS
<opalvaults[m]>
noocsharp: right, but I think we're in good company when I use the term 'usable' here.
<noocsharp>
true
<testuser[m]>
Zoom moment
<noocsharp>
totally forgot, i still need to get my chroot working
<noocsharp>
or be stuck using a bootable arch stick for another semester
<noocsharp>
did you see my xorg log testuser[m]?
<noocsharp>
i don't know how to interpret it
<testuser[m]>
Oh sorry i missed it
<testuser[m]>
Waiy
<testuser[m]>
Wait
<noocsharp>
i sent it in the middle of a netsplit, so wouldn't be surprised if you never got it
<noocsharp>
i don't think dbus should affect input
<dilyn>
you'd be surprised
<dilyn>
I never needed dbus on host to launch chromium but I also never launched a desktop in my chroot so i'm not sure what fuckery might happen
<noocsharp>
i3 starts, but there's just no input
<dilyn>
which doesn't necessarily rule out dbus :V :V :V
<sad_plan>
noocsharp: what exacly are you trying to do? launch graphical enviroment in kiss from arch chroot? I havent been paying to much attention to it, so im just curious :p
<noocsharp>
i don't use udev, so there's no /run/udev
<phoebos>
noocsharp: did you upload your libtls patches to msmtp anywhere
mahmutov has joined #kisslinux
<phoebos>
oh upstream can use libtls
<sad_plan>
but if you did, would it solve your issue?
* sad_plan
shrugs
<sad_plan>
ffs. why does libtool complain about a library was moved?
<sad_plan>
im trying to build the recent release of xfsprogs, which suddenly require userspace-rcu. building it separatly work fine, but when trying to bundle it, it gives me issues..
<phoebos>
oh cool you put it in upstream
<phoebos>
doh
jdfkjsfi has joined #kisslinux
jdfkjsfi has quit [Client Quit]
bibliocar has joined #kisslinux
<op_4>
dilyn so zig has a repository called zig-boostrap (https://github.com/ziglang/zig-bootstrap) which goes from c compiler to statically linked zig. I'm trying to bundle this as a kiss package, would there be any interest in putting this into kiss-community?
<dilyn>
always!
<op_4>
great!
<op_4>
erm, so, there's a slight problem :p I'm wondering whether i might pick your brain. For whatever reason the build script works if *i* run it, but if kiss does then it becomes confused about sourcing the correct llvm. Context: it builds llvm from scratch, then uses that version. This is probably something about cmake, but i don't know where to start looking. I don't suppose i could drag you into this?
sad_plan has quit [Quit: nyaa~]
<op_4>
maybe this should be a discussion to have on a github pr?
<omanom>
it's fine to hold here, do you have a log file to look at showing that issue
<omanom>
or kiss output
<op_4>
omanom thanks :) i have a log file, do you have a preferred pastebin?
<op_4>
it's sources, depends, version, build, and finally log
<op_4>
i believe it failed at the first build of zig, just after building llvm
<dilyn>
bash is a dep for this project
<dilyn>
` LLVM (according to /usr/bin/llvm-config) is missing target AArch64.` it's having the same problem as always hmhm
<op_4>
dilyn thanks, i'll add bash. Anyway, if i do this build outside of this kiss env, as in run this script in an appropriate directory, it passes that point
<op_4>
because it references the correct llvm version (the one it just built)
<dilyn>
presumably it's setting $PATH at some point?
<dilyn>
it fails because it's using /usr/bin/llvm-config instead of the one you built
<dilyn>
change path to $ROOTDIR/out/host/usr/bin:$PATH or w/e it is
<op_4>
ooooh
<op_4>
incidentally, i'm sure we could inline some of the bash specific stuff in this script and avoid the dependency
<dilyn>
but also because you're just running builds manually and not using whatever script this repo bundles you won't need bash
<op_4>
right
<op_4>
so yeah, i don't really know what i'm doing, but i think this is pretty close to a solution (not a great one, but /a/ solution)
<op_4>
alright, well i've changed PATH at the first point in the script and i'll re-run the build to see. Unfortunately building LLVM on my laptop takes ~4 hours :/
<dilyn>
oh jeez lol
Ralph1977 has joined #kisslinux
<op_4>
dilyn in the mean time, would kiss-community be interested in mksh?