ChanServ changed the topic of #river to: river - a dynamic tiling Wayland compositor || https://codeberg.org/river/river || channel logs: https://libera.irclog.whitequark.org/river/
Guest55 has left #river [#river]
catman has quit [Remote host closed the connection]
gera has quit [Quit: gera]
gera has joined #river
lxkraken has quit [Quit: Client closed]
twelve has quit [Remote host closed the connection]
sentry has quit [Ping timeout: 248 seconds]
Snetry has joined #river
dbuckley has quit [Ping timeout: 260 seconds]
mohan43u has quit [Quit: WeeChat 4.6.3]
haliucinas2 has joined #river
haliucinas has quit [Read error: Connection reset by peer]
haliucinas2 is now known as haliucinas
Nosrep has quit [Ping timeout: 276 seconds]
letherlick has joined #river
letherlick has quit [Quit: Client closed]
Keeto has joined #river
Keeto has quit [Ping timeout: 260 seconds]
Keeto has joined #river
Ireozar has quit [Read error: Connection reset by peer]
Ireozar has joined #river
Keeto has quit [Ping timeout: 265 seconds]
Keeto has joined #river
<pkap> seems like river does not implement ext_foreign_toplevel_list_v1? How does lswt work without this protocol?
<pkap> ah I assume with wlr foreign toplevel management
twelve has joined #river
ramblurr has quit [Ping timeout: 248 seconds]
Keeto has quit [Ping timeout: 252 seconds]
<leon-p> pkap: yes, lswt can just fall back to the older protocol
Keeto has joined #river
twelve has quit [Ping timeout: 260 seconds]
<sewn> leon-p: but why doesn't river implement the somewhat standardized protocol?
<ifreund> because nobody did the work yet
<leon-p> last time I was interested in that protocol, it wasn't even in a wlroots release yet 🤷
<leon-p> and since then the WM protocol happened which is a lot more powerful w.r.t. adding custom behaviour to river, which really was the only reason I was interested in ext-foreign-toplevel-list in the first place
mohan43u has joined #river
<ifreund> we have now reached the point in time I forsaw, where we only want ext-foreign-toplevel-list as a dependency of toplevel screecopy
<ifreund> which is why I pushed so hard to strip it down in functionality
<pkap> I'll probably work on the toplevel-list protocol soon because as ifreund just mentioned it's a requirement for the new toplevel-capture stuff which I need.
<ifreund> cool :)
<pkap> I'm a bit exicted about the toplevel catpure stuff. Wayland/river almost perfect for me for many years now with only this one feature missing. Can't believe this is finally on the horizon.
<leon-p> that's how I am feeling about eh WM protocol :)
<pkap> leon-p: will you make a stacktile port to the new wm protocol?
<leon-p> no, I am writing a WM from scratch
<leon-p> stacktiles intricate ways of defining tiled layouts is massive overkill considering the vast majority of time I only ever have a single window on screen
<leon-p> so I decided I'll experiment with non-tiling window management for a while
<vyivel> heh
<vyivel> all those window management types and people just have 1-2 windows at a time anyway
<pkap> I see. But I suspect there will be WM implmentations that support a stacktile-like layout.
<leon-p> probably, there is always someone willing to write yet another dwm clone :)
Keeto has quit [Ping timeout: 260 seconds]
coreopen has quit [Remote host closed the connection]
Keeto has joined #river
Nosrep has joined #river
Keeto has quit [Remote host closed the connection]
Keeto has joined #river
elagost has quit [Quit: WeeChat 4.4.3]
<LarstiQ> vyivel: alas, I often enough run over five
<vyivel> i mean visible at the same time
<LarstiQ> yes
<vyivel> unless you have 5 visible in which case i presume they're all terminal emulators
<LarstiQ> terminal emulators, browsers and emacs
<vyivel> on a single screen?
<LarstiQ> yeah
<vyivel> ultrawide?
<LarstiQ> laptop
<vyivel> wow
elagost has joined #river
<LarstiQ> it's not pleasant so I try not to do it for long
<vyivel> browser+emacs+terminals on a single 16:9 screen would give me instant claustrophobia
<ifreund> I often have more than 3 terminals visible but only ever really interact with the top 1 or 2 in the stack
<ifreund> the rest just kindof sit off to the side and get ignored
<FireFly> browser+two terminals (with vim open in one of them) is reasonably common for me tbh, or similar kinds of layouts..
<FireFly> sometimes with the occasional short-lived floating terminals or so as well
<leon-p> I have moved a lot of things into emacs pop-up windows, which removed basically all transient windows I usually had open. Now it's just firefox, a few emacs frames and IRC
<ifreund> if only emacs had a decent text editor, I wouldn't be trying to hack a decent repl into kakone right now...
<leon-p> true
<vyivel> vscode💪
<leon-p> although I've grown to like structured editing. for lisp things, paredit is actually superior to kakoune keybinds IMO
<leon-p> wish there was something similar for C-likes
<ifreund> leon-p: parinfer has been working pretty well in combination with kakone bindings for me so far
<ifreund> way better than just plain kakoune for wrangling a lisp ast
<ifreund> there are similar things for C-like languages based on tree-sitter emerging in recent years
<ifreund> I suspect they'll never be as nice as lisp structural editing though
Keeto has quit [Quit: Lost terminal]
ramblurr has joined #river
twelve has joined #river
twelve has quit [Remote host closed the connection]
letherlick has joined #river
letherlick has quit [Ping timeout: 272 seconds]
letherlick has joined #river
letherlick has quit [Client Quit]
letherlick has joined #river
Guest5 has joined #river
Guest5 has quit [Client Quit]
letherlick has quit [Ping timeout: 272 seconds]
twelve has joined #river
mekeor has joined #river
twelve has quit [Remote host closed the connection]
twelve has joined #river
twelve has quit [Remote host closed the connection]
Guest0 has joined #river
Guest0 has quit [Client Quit]
letherlick has joined #river
letherlick has quit [Ping timeout: 272 seconds]
twelve has joined #river