<leon-p>
I wonder if we'll ever get proper dark/light mode switching. Works for GTK and river, since those colours can be changed live with a command, but not for the terminal, desktop widgets, terminal-applications...
<leon-p>
and I mean proper, so no hacks like a script that changes the config files
<leon-p>
yeah, I know about that trick, but I consider that to be hack
<NickH>
Fair enough
<leon-p>
just because something /can/ be scripted doesn't mean a script is the best solution, or even a remotely good solution at all
<NickH>
What I'd really like is a terminal multiplexer that supports all the same features of the terminal that its running in.
<leon-p>
river multiplexes my terminals just fine, although that's probably not what you mean :D
<leon-p>
you could run a nested river session though
<NickH>
I run most of my main terminal progreams, in a tmux session: mutt, ikhal, senpai etc.
<NickH>
Mainly so that if I'm away from my main machine I can ssh in and attach to them.
<RZ_MJ[m]>
I've already wondered if there is a terminal emulator that runs in a server-client style and allows switching between shell sessions and preserves non-displayed shell sessions in the background (even when all clients are closed). It wouldnt have to do tiling, nested tiling gets to small anyways.
<leon-p>
there actually is: emacs
<leon-p>
by default it can only do two shell sessions (eshell and shell), but with a plugin you can have an infinite amount
<leon-p>
alternatively, nested river session
<NickH>
I use emacs, but only as an editor not as a shell...
<NickH>
Maybe I should dig a little deeper.
<NickH>
I do already run it as a daemon though.
<RZ_MJ[m]>
I don't get how a nested river session helps here. I would still want to have multiple clients in what I described, with all clients sharing a pool of background shell sessions.
<RZ_MJ[m]>
And once again emacs lures me. So far I never ended up actually learning it though. Seemes so much to learn when I do fine without it.
<aktina>
nested river session ???, what is that, i am currently struggling to find a good terminal multiplexer
<aktina>
i used to use tmux, but i wanted something minimal, dvtm seems kind of too much for what i wish for, and it kind of messes up when i have syntax highlighting in zsh
Guest80 has joined #river
<Guest80>
I wanted to clarify some things:
<Guest80>
I am running void and I followed their handbook. I chose to install seatd instead of elogind (systemd-logind alternative) I enabled seatd and add my user to _seatd group. I am still unable to start river...
<Guest80>
However, I can easily start it when I install elogind, even without enabling elogind service (seatd is still enabled though if that matters)
<Guest80>
My question is: if I just keep using elogind, do I need to have seatd installed or am I safe to remove it?
<Guest80>
This short page is what they had to say on the topic. I followed everything so I don't understand why I can't just use seatd:
<novakane>
Guest80: you can safely remove seatd if you're using elongind
<novakane>
have you set XDG_RUNTIME_DIR with seats?
<Guest80>
novakane thanks for the advice. Just to double-check: By removing seatd, I am not risking any potential application missing it, right? I assume such an app will pull it as a dependency if necessary
<Guest80>
Yes, I do have XDG_RUNTIME_DIR owned by my user with 700
<novakane>
Guest80: probably not. if seatd works when you're installing elongind maybe it's because it installs some dependency you were missing?
<Guest80>
novakane The only dependency that seatd has is glibc (used by almost all programs I have as well). My system is showing that nothing depends on seatd at the moment.
<Guest80>
For elogind, it's not showing that anything depends on it nor does it depend on anything
<aktina>
you can safely remove seatd, if i am not wrong, you can actually have only one
<aktina>
if you want to run both as a service, i don't think it is possible
<novakane>
Guest80: what errors did you have? not sure if you already posted a log
<aktina>
i use voidlinux, with seatd+greetd, if that can help
<novakane>
fwiw there is a package from ifreund for XDG_RUNTIME_DIR, dumb_runtime_dir that make it easy to manage it
<novakane>
you may need polkit too, I don't know if elongind or seatd installed it but other than that I don't think there is a lot of deps needed
<aktina>
if you want to use seatd, you must have lots of other apps, or hacks
<Guest80>
I did not post a log. It was hard to see as 90% of my tty was filled with some generic error.
<Guest80>
I think I figured out what is happening. I will restart and confirm in the chat for archive purposes. I moved by dotfiles and config scripts from FreeBSD and I didn't notice the subtle difference:
<Guest80>
XDG_RUNTIME_DIR over there had to be at VAR -> run -> user... and on void linux just /run/user. And every time I would check it happened to be so during the session when I was running elogind so I didn't realize. I figured out by noticing that /run/user/1000 was created today for the first time which was a hint as I installed void a few days ago.
<Guest80>
But But based on what I am reading online and what @akitna said, I might just keep using elogind to avoid hassle and other potential hacks
<Guest80>
Sorry to waste your time, I didn
<aktina>
no wait Guest80
<novakane>
Guest80: yeah honestly install dumb_runtime_dir and you will never have to think about that again
<Guest80>
didn't realize I made a mistake with the path
<aktina>
you have two options, one is using a single line script, other is using some plethora of applications
<aktina>
in single line script, have something like a river-run script (i do that with the case of dwl)
<Guest80>
I am all ears @aktina. I am curious as to what is a better approach.
<aktina>
idk if it'd work, the above one worked for me, and i didn't think of changing
<Guest80>
Okay, I will reboot my computer and test it right now and I will post the results. The issue I think I have was that I was copying these configs from my FreeBSD where XDG_RUNTIME_DIR had to be in /var/run/user/ instead of /run/user
<aktina>
the other choice, is using seatd+greetd+pamd+dumb_runtime_dir
<Guest80>
But thanks anyway
<Guest80>
I will explore this over time and see if using seatd over elogind ends up being a hassle in other aspects
Guest80 has quit [Quit: Client closed]
Guest80 has joined #river
<Guest80>
Just wanted to confirm (mainly for archive purposes) that I was able to start river with no errors using only seatd.
<Guest80>
I created XDG_RUNTIME_DIR at /run/user/$(id -u) made sure my user is the owner of it and that permissions are set to 700.
<Guest80>
Then I exported the XDG_RUNTIME_DIR environmental variable in my shell's rc file.
<Guest80>
Also, my user had to be the part of _seatd group.
<Guest80>
Thanks everyone for the advice along the way
jao has joined #river
waleee has joined #river
Guest80 has quit [Quit: Client closed]
ccha has quit [Quit: WeeChat 3.8]
ccha has joined #river
waleee has quit [Ping timeout: 245 seconds]
taupiqueur has joined #river
leopoldek has joined #river
alexherbo2 has joined #river
JustineSmithies has joined #river
<JustineSmithies>
I'm currently running the stable release of River on Void but I'm thinking of just building from git the latest and just keeping that upto date manually. How many others here are running with the latest git version of River ?
<JustineSmithies>
I'm already running it on my test machine just wondered about doing the same on my daily ?
<dnkl>
JustineSmithies: I do, and have been doing that for a very long time. Usually no problems what so ever.
<JustineSmithies>
dnkl: Ok cool and thank you.
<JustineSmithies>
dnkl: Can I ask what --prefix you use when building for it to install too and does it install the man pages too ?
<novakane>
if you have something like ~/. local/bin in your $PATH, it's a good place to use as a prefix
<novakane>
and yeah it install man pages
<dnkl>
JustineSmithies: I build and install it as an AUR package
<JustineSmithies>
Cool thanks novakane and dnkl ;)
<novakane>
JustineSmithies: wait my message is confusing, if you want to use ~/.local/bin the prefix is just ~/.local
<JustineSmithies>
Cool got it installed now on my test laptop as I was just running river out of the zig-out directory which wasn't right. Now it's installed and I have my MANPATH set everything is perfect.
<JustineSmithies>
novakane: Yeah I realised what you meant but thanks anyway.
<JustineSmithies>
See when there are new changes committed to Rivers git and i do a git pull should I always do a git submodule update --init before building ?
<JustineSmithies>
I think that's what I've understood ?
<novakane>
You can use `git submodule update --recursive` to update submodules, personally I like the nuclear option of `git submodule deinit -f .` and after `git submodule update --init` :P
<novakane>
just because submodules are messed up too often, but if you're not using a fork it's probably fine
<JustineSmithies>
novakane: Thank you
<ifreund>
git pull --recurse-submodules also works
<JustineSmithies>
ifreund: Cool thanks
<ifreund>
and you can pass --recurse-submodules to pretty mich every command and it will work more like you expect
<ifreund>
there's a git config option to make it the default too
alexherbo2 has quit [Remote host closed the connection]
<JustineSmithies>
Back in a minute just building River and away to run up again hopefully ;)
JustineSmithies has quit [Quit: WeeChat 4.0.0]
JustineSmithies has joined #river
<JustineSmithies>
And I'm back running 0.3.0-dev.117+0b142bd