snakedye has quit [Read error: Connection reset by peer]
snakedye has joined #river
waleee has quit [Ping timeout: 240 seconds]
waleee has joined #river
waleee has quit [Ping timeout: 268 seconds]
notzmv has joined #river
notzmv has quit [Read error: Connection reset by peer]
notzmv has joined #river
snakedye has quit [Read error: Connection reset by peer]
snakedye has joined #river
snakedye has quit [Ping timeout: 256 seconds]
snakedye has joined #river
snakedye has quit [Read error: Connection reset by peer]
snakedye has joined #river
snakedye has quit [Ping timeout: 240 seconds]
zdykstra has quit [Changing host]
zdykstra has joined #river
snakedye has joined #river
snakedye has quit [Ping timeout: 240 seconds]
snakedye has joined #river
snakedye has quit [Ping timeout: 256 seconds]
priner has quit [Quit: You have been kicked for being idle]
snakedye has joined #river
Guest70 has joined #river
Guest70 has quit [Client Quit]
Guest70 has joined #river
Guest70 has quit [Client Quit]
lgflorentino has joined #river
<lgflorentino>
Where is the best resource for learning about using XWayland. I don't know enough to debug this X11 program that is throwing errors and won'
<lgflorentino>
t start
<leon-p>
a good first thing to do would be to say what errors you have, maybe someone will have an idea
<lgflorentino>
it runs on a awesomewm install but I haven't used that wm last couple of years
<lgflorentino>
My understanding is that XWayland is automatically used when I try to run an X11 program. Is that correct ?
<ifreund>
Pretty much, if you have xwayland enabled both $WAYLAND_DISPLAY and the X11 $DISPLAY are exposed
<ifreund>
X11 clients will connect to xwayland's DISPLAY
<ifreund>
anyhow, if your IDE is segfaulting that's most likely a bug with the IDE tbh
<ifreund>
the first step would be getting a backtrace to try and gain more information
tiziodcaio has left #river [#river]
<lgflorentino>
Thanks for that. It's the IDE but i wanted to make sure XWayland is working correctly on River before I give up. Backtrace I don't think I can do. closed source from the vendor side and in gdb there are no debugging symbols :( it only spits out the same message.
Grawp has joined #river
<ifreund>
lgflorentino: I don't have much experience debugging X11 stuff, x11trace can show you the X11 protocol messages between your IDE and Xwayland I believe
<ifreund>
almost all the code dealing with Xwayland on river's side is in wlroots not river itself
<ifreund>
debugging proprietary stuff is never easy though :/
<ifreund>
you could also try it under gnome or weston to see if works with their xwayland implementation
<lgflorentino>
I see. I'm still not sure xwayland is working correctly. The $DISPLAY is not in the output from env command
<lgflorentino>
eg running gimp i get 'Cannot open display:'
<ifreund>
lgflorentino: did you build river with xwayland support enabled?
<lgflorentino>
I'll check the build logs
<ifreund>
(the -Dxwayland flag)
<lgflorentino>
most likely not. I'll try rebuild with that flag. Thanks!
lgflorentino has quit [Quit: leaving]
<andrea>
Hello, i've made a statusbar for river. Still in early development, but I hope you like it :)
<andrea>
Thanks :) Let me take some other university exams and I'll sure keep working on it.
<leon-p>
andrea: nice. it works quite well!
<leon-p>
also good job centering the clock in the middle. Most bars center based on the available free space, yours correctly centers based on output width
<leon-p>
that was like my number one complaint with any bar back when I still used a bar :P
<leon-p>
it does not like overly long status string though, I got it to crash by piping fortune into it
<andrea>
Thanks. I would have neve thought clock centering would be such a killer feature haha
<leon-p>
also the bar will never display if the pipe is closed, like `echo hello | ./levee`
<andrea>
Yep, don't really know how to solve it thou
bfiedler has quit [Ping timeout: 250 seconds]
bfiedler has joined #river
Nulo has joined #river
pkap has joined #river
<ghostbuster>
hmm so i've done something strange to tag 2
<ghostbuster>
my understanding is that mod+shift+n tags the focused window with tag n, and mod+n displays all windows tagged with tag n, and mod+ctrl+n displays the currently display windows AND the windows tagged with tag n
<ghostbuster>
is that about right?
pkap has quit [Quit: Client closed]
<ifreund>
I can't say what things you've got bound to what, but if mod+shift+n is set-view-tags, mod+n set-focused-tags and mod+ctrl+n toggle-focused-tags that's mostly right
<ifreund>
your description of toggle-focused-tags isn't entirely accurate though, if the given tag is already part of the visible set it will instead be hidden
<ifreund>
and toggle-view-tags also exists but wasn't mentioned
<ifreund>
have you read the section on tags in the riverctl man page?
<ghostbuster>
i'm a bit confused by the terminology there.. i feel like the definition of 'focus' is different than what i think of focus as meaning in a window manager
<ghostbuster>
i'm using the default bindings
<ghostbuster>
and i assume that a view is an output? or is a view a single window ie. an application
<ifreund>
ghostbuster: In retrospect I should have probably went with set-output-tags and toggle-output-tags
<ifreund>
view is a window
<ghostbuster>
naming is hard :)
<ifreund>
"view" is bad terminology that we appear to have inherited from weston through wlroots
<ifreund>
I plan on fixing that at some point, but haven't managed to yet
<ghostbuster>
is there ever a situation where a view is not synonymous with a window?
<ifreund>
hmm, depends on what you mean by window
<ifreund>
the X11 likely has a very different definition than you do, pretty much everything is a window (e.g. right click menus)
<ghostbuster>
i see
<ifreund>
view directly corresponds to what we call a "toplevel" in wayland protocols
<ghostbuster>
as an side it's funny to hear that wlroots works on views because sway and wlr-randr work on outputs
<ghostbuster>
can a toplevel get "encapsulated" or become a sub-window of another new toplevel
<ifreund>
I don't think wlroots uses the word view anywhere it it's source, I was talking about the tinywl example
<ifreund>
and river has outputs too
<ghostbuster>
oh so it does
snakedye has quit [Ping timeout: 240 seconds]
<ghostbuster>
would you be interested in adding a section on terminology to the man page?
snakedye has joined #river
<ifreund>
I wouldn't mind it, the status quo obiviously isn't perfect
<ifreund>
long term I'd rather find the correct terminology that makes a definitions section unnecessary
<ghostbuster>
i think the term 'focus' is overloaded as well.. a set of tags aren't 'focused' so much as they're displayed, right? at any given time only one toplevel can be truly focused
<ghostbuster>
not trying to criticize btw, coming from sway I am really enjoying using river so far :)
<ifreund>
ghostbuster: one small note: keyboard focus isn't strictly tied to pointer focus in wayland and in river
<ifreund>
i guess from the users perspective though it does follow pretty closely, especially if focus-follows-cursor is enabled
<leon-p>
the difference becomes clear if you try to scroll with your mouse in a window that does not have keyboard focus
<ghostbuster>
ah, yeah i enabled focus-follows-cursor but that's off by default
<tiosgz`>
i think i got infected with automatic tiling, now i wish (n)vim had it too :D
<leon-p>
tiosgz`: sounds like you need some kakoune in your life. Instead of having it's own internal window system like (n)vim, it allows you to have multiple connected windows so you can just use rivers window management
<tiosgz`>
hah, just today (or was it yesterday) i was considering trying it out. with this new info… only waiting for a big enough time window
<leon-p>
if you are used to vim, kakounes keybinds will come pretty naturally
<ifreund>
yeah, vim to kakoune isn't too bad
RawFiend has joined #river
<ghostbuster>
is it a plugin for vim or does it replace vim?
<leon-p>
ghostbuster: it's like vim, but if the keybinds made sense
<leon-p>
so yeah, another modal editor, but a better designed one IMO
<ghostbuster>
blasphemy :P
<ghostbuster>
cool though, may have to check it out at some point
<novakane>
kakoune is the official editor of river, you need to use it to code for it :P
<snakedye>
Someone shilled me helix as being kak but the keybindings make sense. I don't know what is real anymore
<ghostbuster>
lol novakane
<ifreund>
helix is kakoune but without the unix philosophy
<ifreund>
aka it's shit :P
<novakane>
last time I try helix half of things wasn't working so...
RawFiend has quit []
<leon-p>
whenever I read the term UNIX philosphy I have the urge to quote the UNIX haters handbook.
<leon-p>
although to be fair, what we see today is a bit of a bastardization of the idea
<snakedye>
The UNIX philosophy is a buzz term on the same level as RIIR. At least how it's used now.
<leon-p>
the general concept of small pluggable components is pretty great, but some people use it to justify writing code that is barely more than a proof of concept and then go on about "minimalism vs bloat"
<elshize>
I've considered trying kakoune, even tried it for a bit, and I really like it, I admit it makes sense, and all... the problem is that vim is everywhere, like on some web editors I'm forced to use -- the key bindings are supported and in other software. I'm afraid once I switch to kakoune, I'll lose all that because I'll struggle in vim; does it make sense?
<elshize>
does anyone here have issues goign to vim after getting comfortable in kakoune?
<leon-p>
elshize: I actually face that problem a lot
<leon-p>
mostly when I have a lab partner who demands we use ShareLaTeX. That horribly web-editor has a vim mode but no kak mode.
<novakane>
leon-p: can't you just change your lab partner? :P
<leon-p>
^^
<elshize>
leon-p: right, that's a perfect example
<leon-p>
but it's doable. Superficially they are similar enough that I don't mind, for me it's still worth it
<leon-p>
like the difference is less annoying then vim vs old school vi
<elshize>
it's the same thing with me switching to ortholinear split keyboard. I literally can't type on anything else :D
<leon-p>
well, at this point my computer being usable for others is a lost cause anyway, so that kind of keyboard is also on my try list :P
<elshize>
oh, yeah, if my wife comes to my work station, all she says is "what is all this?" and shrugs
<elshize>
I'm saying, I can't use my laptop keyboard
<ghostbuster>
my wife gets tripped up that my capslock key is rebound to ctrl
<ifreund>
Well, I only get like 30 to 40 wpm on a "normal" qwerty layout keyboard now instead of 80-100 on my custom split colemak thing
<ifreund>
but honestly that ok
<ifreund>
same with being forced to use editors that aren't kakoune, as long as only have to do it like 1% of the time it's not to annoying
<ifreund>
s/to/too/
notzmv has quit [Ping timeout: 268 seconds]
<elshize>
ifreund, leon-p: darn, I suppose I have no excuse then; either of you have some public dotfiles I could use to help set up LSP?
<leon-p>
my config is public, but I don't use LSP
<elshize>
do you use anything for, say, jumping do definitions and such?
<elshize>
or live type-checking for that matter?
<leon-p>
not at the moment. The last few months I only worked on code bases I already know inside-out, so it was never an issue
<leon-p>
and for live type-checking, I find things lighting up while I type a bit annyoing, so I don't do that either
<leon-p>
I think you could probably configure it to lint syntax with zig fmt, but I have not looked into that yet
<ifreund>
I do use LSP with kakoune
<ifreund>
leon-p: zig ast-check is better for that task (new since 0.9.0)
<leon-p>
cool!
<ifreund>
it checks for unused variables as well as parse errors
<ifreund>
and a few other things I believe
<novakane>
wait what, I missed this in the changelog
<leon-p>
yeah, ast-check works, now I only need to find out how to make kakoune interpret the input
<leon-p>
s/input/output/
<elshize>
novakane, ifreund: thanks for the links, much appreciated
<novakane>
leon-p: with lintcmd?
<leon-p>
novakane: yes, I set lintcmd to `zig ast-check`, but I think I need to redirect it's output to stdout instead of stderr
<leon-p>
yup, that works
<leon-p>
although I wonder if one can interpret the output of zig-fmt as a linter as well, since it runs everytime on save anyway
<novakane>
I mean yeah kinda usually with an error zig fmt doesn't works
<leon-p>
but it prints useful information about what went wrong
<leon-p>
try breaking the syntax, run zig fmt on save and then look into the *debug* buffer
<novakane>
yeah probably not enough though
<leon-p>
well, I mean if I /really/ cared about detailled information, I would have set up LSP
<novakane>
fair
<novakane>
ast-check is cool, tried it with lintcmd too, that good to have as some builtin
<novakane>
since makecmd works great with zig build you can really have a great zig setup with just kakoune builtin, that's nice
<elshize>
ok, I figured out a foolproof way of making sure I stick to kak for a while: alias vim kak
<leon-p>
there is also a kaktutor file, analog to vimtutor, floating around somewhere
<elshize>
leon-p: yeah, saw that one, I think I've actually gone through it a while back, so I'm not totally clueless; it's more about remembering and muscle memory
<novakane>
kakoune wiki is a great way to see some diff with vim, it really help me