00:08 <chipps> is it possible to drag windows from one output to another? right now although the pointer can move from a monitor to another, the windows seem to be confined to within the output

00:11 <ifreund> chipps: nope, not currently

00:12 <ifreund> we'll probably have that feature eventually though

00:13 <waleee> that is incredibly weird in hikari, the window doesn't move over to next monitor until the cursor is about center of said monitor

10:59 <novakane> weird thing again with bitwarden firefox addon, the dropdown menu appears at the other side of screen https://0x0.st/-hc-.png

11:00 <leon-p> might be a FF bug. It has issues before with popups on Wayland

11:00 <leon-p> s/has/had

11:01 <novakane> yeah I had all issues possible, I have no doubt it's a firfox problem as always, just report this here in case

12:18 <ifreund> I wonder if that's a firefox regression on a recent version

12:20 <novakane> can't really tell, not sure since when I have this, I don't add things like in bitwarden often

12:27 <novakane> hm firefox 94 is from like 1 month in void so I'm sure I didn't have this before though

12:28 <novakane> unrelated but do you guys know if this is a good bash syntax `all_but_toggle_tag=$((((1 << 32) - 1) ^ scratch_tag ^ chat_tag))`

12:29 <novakane> the double ^

12:29 <pkap> I had the same issue for several Firefox versions.

12:30 <novakane> pkap: ah well maybe I didn't notice before then

13:11 <Anderson-D> Is there some built-in layout configuration that will simply zoom all windows to fit screen instead of tiling?

13:11 <Anderson-D> I'm looking for smth like "zoom" in qtile or "max" in awesomewm

13:13 <novakane> Anderson-D: yes rivercarro can do this and IIRC stacktile too https://github.com/riverwm/river/wiki/Community-Layouts

13:21 <Anderson-D> novakane: thanks, stacktile seems nice!

13:22 <novakane> indeed, it is

13:22 <Anderson-D> Is there any way to set all_primary to true on startup?

13:22 <Anderson-D> It's missing from cli flags for some reason

13:23 <novakane> hm leon-p ^

13:26 <Anderson-D> If there's no specific reason why it's absent, I could submit a patch that implements this as a cli arg, leon-p

13:28 <Anderson-D> Also, please pardon my barbarism, but is there a specific reason why so much stuff is hosted on sourcehut nowadays?

13:28 <Anderson-D> I

13:28 <Anderson-D> I've never used it before so don't have any prior knowledge about this service

13:31 <novakane> Anderson-D: Beacause it's kinda different from other forge, usinge mail lists for patches and everything, 100% FOSS

13:31 <Anderson-D> Oh, I see. Makes a lot of sense

13:56 <Anderson-D> I've submitted a patch for this, I was not sure if sourcehut provides any pseudo-email addresses to send patches to so I've sent it to the one I found on Leon's website. Am I doing it right? :)

13:59 <pkap> What is the best way to send a list of strings over the wayland protocol with zig?

14:01 <Anderson-D> leon-p would you mind telling me which email to send patches to? The one I've used seems to be non-existent

14:01 <novakane> Anderson-D: yeah there is some mail list for example since stacktile doesn't have a dedicated one you can use the public-inbox one https://lists.sr.ht/~leon_plickat

14:02 <novakane> although I did send some mail to the adress use in `git log`

14:03 <novakane> so e.g you can use `~leon_plickat//public-inbox@lists.sr.ht`

14:04 <novakane> oops typo `~leon_plickat/public-inbox@lists.sr.ht`

14:04 <Anderson-D> Gotcha. Thanks! Just sent a patch

14:19 <leon-p> Anderson-D: there currently is no CLI flag for all_primary, because when I added the feature the use case I had in mind was toggling it at runtime. I would not mind a patch to add a flag.

14:19 <leon-p> For projects that do not have their own mailing list, you can just send me patches to one of my personal mail adresses or to my public-inbox

14:27 <leon-p> Anderson-D: I have applied your patch and will push it shortly. In the future, please do not include style fixes in feature patches and configure your editor to correctly do the tabs vs spaces thing.

14:28 <Anderson-D> leon-p: thanks! Sorry for the style fixes, I'll keep that in mind

14:29 <leon-p> don't worry, for such small patches I can easiely fix it. However it gets a bit annoying when a patch is more than 100 lines

14:31 <novakane> leon-p: could be great if you have a clang-format config

14:32 <leon-p> novakane: I tried multiple different formatters but none can be configured to reliably reproduce the C style I use in my projects. And at this point I am too stuborn to change my style :P

14:33 <novakane> leon-p: lol yeah I tried to make one with clang-format for river-tags-overlay once and saw that :P

14:34 <leon-p> I am of course not opposed to minor style changes, but a lot of the subtelty I have in my C style is so massively hard-wired into my brain it would be annoying to get used to something else

14:35 <novakane> yeah I get it though it's nice when you can use the format command from language server

14:38 <leon-p> Do the clang format people accept changes? If I get really bored one day I might be able to convince clang format to reproduce my code. But my schedule is a bit full atm and tbh even staring at a wall sounds more exciting

14:40 <novakane> no idea, it is already pretty configurable, I think some things that couldn"t be made was like using space betweeen brackets since like this, although there is so many options that maybe I missed it

14:42 <elshize> leon-p: just write your own formatter, duh :P

14:43 <leon-p> elshize: "before working on my project, please clone and build my formatter, which depends on my custom c tokenizer, which depends on my custom libc, which depends on the zig toolchain", yeah, sounds like a plan

14:44 <elshize> leon-p: hmm, I see what you mean.

14:44 <leon-p> to be fair, I had the idea before

14:45 <elshize> having your own specific style & no formatter is just fine if you're mainly working on your own, or with people who are willing to comply

14:45 <elshize> but in my experience, whenever there are more than a handful people, it's better to have a consistent formatter, even if it's not perfect

14:45 <novakane> just minimize everything to one line duh

14:46 <elshize> I have lots of issues with clang-format, but when writing c++, always use it.

14:46 <leon-p> I don't disagree. This is a problem I chose to have by using a non-standard style

14:49 <elshize> the thing is, there's no standard style in c or c++, and many other langs

14:49 <leon-p> not de-jure, but definitely de-facto

14:49 <novakane> that a thing I like with zig even though I don't agree with everything

14:50 <leon-p> yeah, I don't agree with the zig format, but I see the benefit of having a One Ture™ format, so I use it

14:50 <leon-p> s/Ture/True/

14:52 <elshize> I do the same with python at work, decided to use black formatter, and just go with it. not always perfect, but good enough and takes your mind off of formatting. saves time during code review for sure

14:53 <elshize> because some projects that don't use it are a big mess; I guess it comes down to self-discipline of contributors

14:54 <elshize> but there's always someone who will submit some code that looks like it was chewed up by a dog and spit back out.

15:09 <leon-p> So I tried GNU indent and it comes pretty close, maybe I'll use that. Needs more testing though