pitillo changed the topic of #crux-arm to: CRUX-ARM 3.8 Released! - http://crux-arm.nu/Documentation/ReleaseNotes3-8 | Logs: https://libera.irclog.whitequark.org/crux-arm/
<hermit_crab> well, xorg works well but evilwm not found fonts.
<r0ni> oh an hour ago you said "xorg cannot open display" -- that's working now?
<r0ni> fonts need "fc-cache -f" to be ran (I think it's -f) man page lists specifics
<hermit_crab> Xorg works now! But fonts (on evilwm) not work. Already was used the "fc-cache -f".
<hermit_crab> OWW. "fc-cache -f" saves me :O
<hermit_crab> LOL
<hermit_crab> thanks r0ni
<hermit_crab> :-)
hermit_crab has quit [Quit: hermit_crab]
jaeger has quit [Server closed connection]
jaeger has joined #crux-arm
<r0ni> I'd gave up with trying out tea (and gitui is broken) but using regular git I was able to access the repo properly, I just need to learn how to properly use git lol when the repo asks for my password, it wants my token, so at least I figured that out... I need to create myself a little workflow doc describing all the commands i need to use each time and I should be good to go eventually heh
<jaeger> Feel free to ask questions too :)
<beerman> indeed
<beerman> i'll start: what exactly are you trying to do? Because not everything requires a token. You can push a ssh key to git and authenticate against that, which is very convenient if you have a keyring that has your unlocked key for you
<r0ni> uhhh i dunno, i'm trying to use git, rather than use github-desktop which i don't have to think about, i know what i'm doing with that lol but I pushed keys to the gitea, ssh/gpg and tea make me make a token and I found using git cli commands that git wants that token as my password
<jaeger> Depends on your remote
<r0ni> i *think* I saved my login info so it's just doing things now, but working git from cli is very obnoxious i guess heh
<r0ni> i forked the repos i work with, so I can do PRs against them and the PR to real repos as well
<jaeger> I use it almost exclusively from the cli for what that's worth
<r0ni> like if i'm pushing a update to a port I use my fork, make a new branch with the port name, push my changes, and do a PR against that to the official repo. thats generally what i do
<r0ni> i'm just not used to git on cli, i'm sure i'll get there eventually... i'm basically reading some giant book at git-scm.org and just searching for the command i'm looking for, cuz i don't need the entire book, prob use like 5 commands overall
<jaeger> No worries, you should definitely use whatever's most comfortable
<jaeger> I have a coworker who uses vscode for all his git interactions
<r0ni> I'd literally always just used the github app, it's stupid simple, so actually using real git is like learning an all new thing heh
<jaeger> fair enough
<r0ni> someone out there should make a git gui app that is stupid simple but actually teaches the real git commands as you go, that'd be hotcakes and it'd help the world be a better place by moving people off github.
<beerman> heh, is gitui broken? I dont really use it but it appears working everytime i open it
<jaeger> what's gitui? another app?
<beerman> i assume he means contrib/gitui, its a rust tool that actually does use a rust library to do your git actions
<jaeger> Ah, ok. I'd never heard of that
<beerman> Well, I can't say you are missing out exactly, but I am sad to say it. The tui is nice, I just didn't find it super useful
<beerman> maybe there is workflows where its fitting better but I don't have em
<r0ni> it don't build, but i found a bin, but it says it don't support the auth method being used on git.crux.nu
<r0ni> not sure if the app itself don't or the pre-built don't
<r0ni> i think its rust? the port didnt build, I do know that, but being on arm... that happens a lot
<beerman> uhm, ok, it should work I think but I can't say I tried
<r0ni> it could be a local issue, given my lack of knowledge with git, i can't say the program don't work, just it didn't with my setup
<beerman> you do mean that rust tui application?
<r0ni> yeah the 'rustui' port
<r0ni> no shi the 'gitui'
<beerman> lol ok
<beerman> weird
<r0ni> i figured maybe rust 1.89 changed someth or a dep was changed upstream