04:34 <pltrz> I'm not understanding why my `bemenu` colour flags are not being respected in river's `init` script

04:35 <pltrz> ```

04:35 <pltrz> * ```

04:36 <pltrz> * ```

04:37 <pltrz> `riverctl map normal $mod+Shift P spawn 'bemenu-run -H 32 --tb $base00 --tf $base05 --fb $base00 --ff $base05 --nb $base00 --nf $base05 --hb $base04 --hf $base00'`

04:38 <pltrz> looks like my `-H 32` flag is being respected - but not the other colours (and yes, those variables, ex. $base00 are defined in the beginning of the init script)

04:39 <pltrz> such as `export base00="#263238"`

04:40 <pltrz> this bemenu invocation seems to work correctly when I run it outside of river's init

07:03 <novakane> pltrz: you should try to quote your spawn command with double quote instead

08:29 <ifreund> pltrz: yeah, if you're using a posix shell it won't expand variables inside a single quoted string

10:38 <novakane> I was looking at using river-layout-v3 installed by river and I feel like users would need to use the same install prefix for river and 3rd party program or it gonna be annoying

10:39 <ifreund> novakane: this is probably solved with pkg-config

10:39 <ifreund> that would be a nice thing to implement if you want to give it a go

10:39 <ifreund> see how we get the wayland-protocols directory from pkg-config in zig-wayland

10:40 <ifreund> looks like their pkg-config file is generated from this: https://gitlab.freedesktop.org/wayland/wayland-protocols/-/blob/main/wayland-protocols.pc.in

10:41 <ifreund> and then with export PKG_CONFIG_PATH="${HOME}/.local/lib/pkgconfig"

10:42 <ifreund> you should be good to go with river installed to ~/.local

10:42 <ifreund> if you see a better way I'd be happy to hear it though :D

10:43 <novakane> hmm yeah I don't know much about pkg-config but I'll have a look because currently I don't think it's ideal

10:44 <novakane> I mean it works fine if you use the same prefix but I guess it could be better

11:09 <novakane> I have a problem to select text with the mouse now

11:09 <novakane> looks like selecting anything with the mouse in fact because it doesn't works in pcmanfm too

11:18 <novakane> I need to move away but I'm interested if someone else has this issue

12:14 <elshize> ifreund: fyi the fix didn't help with my thing. but still can't figure out when exactly it happens. I'll let you know if I do.

12:19 <ifreund> elshize: too bad, please do let me know if you figure out any thing else that might help me reproduce or fix it :)

12:19 <elshize> ifreund: sure thing

13:31 <leon-p> so after our talk about shells here recently, I started working on a little experiment. My conclusion is that I changed my mind completely on LISP like syntax for shells. S-Expressions are easy to parse and a pretty good way to handle command nesting, but for shell control flow they are not great. The evaluator would have to be way more complex than a simple tree-flattener and shell stuff like piping and

13:31 <leon-p> return values would get weird.

13:31 <leon-p> https://git.sr.ht/~leon_plickat/quetzal , should anyone be interested, although It really does not do anything yet.

13:48 <pltrz> novakane, ifreund: thanks for the tip! didn't seem to work this way - now `bemenu` does not even run

13:49 <ifreund> pltrz: are you on river master? Is anything printed to river's stderr?

13:50 <ifreund> leon-p: neat! I'm interested to see where you go with it

13:50 <ifreund> S-Expressions seem like they might be slightly verbose/annoying for interactive usage as well IMO

13:50 <ifreund> though I can't say I've had the chance to use a s-expr shell yet

13:50 <ifreund> actually, I think I saw something like that in janet

13:51 <leon-p> It's great for command nesting, like (echo (date) (acpi))

13:51 <leon-p> but for control flow it is probably a bit annoying

13:51 <ifreund> https://github.com/andrewchambers/janetsh

13:52 <ifreund> also if you haven't yet seen this list: https://github.com/oilshell/oil/wiki/Alternative-Shells

13:53 <leon-p> ifreund: I know that list, I check it every now and then to see if something interesting pops up

13:55 <pltrz> ifreund: yes, latest master as of now `[ae871c2]` produces same behaviour - let me check stderr

14:04 <ifreund> pltrz: here's a good way to debug actually, set WAYLAND_DEBUG=1 for the riverctl invocation you are having issues with and give me the output of that

14:10 <elshize> ifreund: leon-p: what shell are you using for daily work?

14:10 <leon-p> elshize: usually bash, currently trying elvish

14:12 <ifreund> elshize: I'm currently on zsh for interactive usage and dash for scripting

14:13 <elshize> I've been meaning to try some new shells, but I'm not sure which ones are worth looking into for more structured type of workflow

14:14 <pltrz> <ifreund "pltrz: here's a good way to debu"> thanks - here's the output (https://dpaste.org/o38r)

14:15 <pltrz> I've also been playing around with some of those shells from oilshell's wiki too :)

14:16 <leon-p> elshize: for interactive usage, the language is actually pretty irrelevant, as long as you can type it fast. What matters more is the interface. As an example, I have realy grown to like elvish's ctr-l keybind, which oens a prommpt where I can quickly select and cd to any directory I have opened so far.

14:19 <pltrz> <leon-p "elshize: for interactive usage, "> I actually found the same for `elvish` - that feature is so neat. little tui file browser is absolute genius for an interactive shell

14:19 <leon-p> yup, haven't touched ranger in a week

14:20 <pltrz> ifreund: i notice from my paste - `bemenu-run: option '--tb' requires an argument` is bemenu's error

14:21 <pltrz> at first I thought the variable wasn't expanded, but looks like it was

14:22 <pltrz> `[1321988.268] -> zriver_control_v1@5.add_argument("BEMENU_BACKEND=wayland bemenu-run -H 32 --tb #263238 --tf #EEFFFF --fb #263238 --ff #EEFFFF --nb #263238 --nf #EEFFFF --hb #B2CCD6 --hf #263238")`

14:23 <leon-p> pltrz: that is passed to `sh -c`, which thinks you want to start a comment with the first # and discards the rest of the line

14:24 <leon-p> we /really/ should change the colour format

14:24 <pltrz> <leon-p "pltrz: that is passed to `sh -c`"> that would make sense!

14:24 <pltrz> ughhhh

14:25 <pltrz> maybe I can use backslash to signify literal #

14:26 <leon-p> you can also quote them. Just make sure to escape the quotes since the entire command is quoted

14:26 <leon-p> i.e. " \"#rrggbb\" "

14:27 <ifreund> welcome to posix shell, an exercise in quoting hell

14:28 <ifreund> and yeah, I think everything should stop using # for colors, including river

14:28 <leon-p> I'll steel that quote

14:29 <ifreund> :D

14:30 <pltrz> <emersion "stops processing the sentence at"> what do you mean here?

14:31 <emersion> i mean that i'm posix certified

14:31 <emersion> (it's a joke)

14:31 <pltrz> lol

14:31 <pltrz> i thought might have to do with `mrsh`

14:32 <pltrz> btw emersion - did you guys still have plans to work on `imrsh` ?

14:32 <emersion> eh :P

14:33 <emersion> no plans in the near future, sorry

14:33 <emersion> shells are just too annoying to build

14:33 <pltrz> no reason to apologize

14:33 <pltrz> how I read it: "there are more entertaining priorities" lol

14:34 <emersion> pretty much!

15:15 <elshize> ifreund: I keep getting weird crashes now sometimes when I close windows... I accidentally overwritten the log file, I'm waiting for another crash to get the logs.

15:18 <novakane> leon-p: I was looking at lisp shell after you conversation, that's cool! Did you forget to include the deps folder though?

15:18 <novakane> s/you/our/

15:18 <leon-p> novakane: yeah, forgot to add the submodule. You can just clone it into deps/ manually though: https://github.com/joachimschmidt557/linenoize

15:19 <leon-p> note that it does not actually execute commands yet, I am only working on the evaluator rn

15:22 <novakane> leon-p: thanks, I'll have a look

15:32 <novakane> RE: my mouse problem, so nobody has any issue with selecting things with the mouse here?

15:32 <leon-p> novakane: selecting things via pointer works in both firefox and foot

15:34 <novakane> damn so it could be from something else than river, well time to investigate

15:39 <elshize> novakane: I don't have any problems either

15:50 <novakane> :/

15:58 <novakane> what's cursor down mode?

17:05 <ifreund> elshize: that's no good, they're definitely new after a recent commit though? A stack trace would be very useful in any case

17:05 <ifreund> novakane: I can't reproduce any mouse issues

17:05 <ifreund> cursor down mode is when a button is held down as we keep sending events to a client while the button is held down until it is released even if the cursor moves outside of the surface

17:05 <elshize> ifreund: can't be sure if they're new, at least I just noticed them today. I'll grab the logs once it crashes again

17:06 <ifreund> that'd be great, thanks

17:26 <novakane> ifreund: ok thanks for the explanation, well for whatever reason it works again now, no idea why

17:29 <novakane> looks like this line was here but I don't have it anymore

17:30 <novakane> `debug(wlroots): [xwayland/xwm.c:1475] unhandled X11 event: SelectionClear (29)`

17:30 <novakane> also looks like my mouse was only on down mode when I double clicked but not for selecting something

17:39 <ifreund> weird, well if you find any way to reproduce it please open an issue or otherwise let me know

17:40 <ifreund> ok, so since I'm dropping the '#' for colors, do people prefer 0xRRGGBBAA or just plain RRGGBBAA

17:42 <leon-p> I use 0x in all my projects, but both are perfectly fine IMO

17:43 <novakane> I don't have any preference both are fine for me too

17:47 <pltrz> agree, both fine. 0x prefix is kinda nice because 1. it’s explicit in describing the type and 2. is consistent with Zig hex formatting

18:39 <ifreund> 0x is is

18:39 <ifreund> s/is/it/

19:02 <novakane> hey we didn't have any issues with the new spawn command, are river users the best? :P

19:03 <ifreund> maybe they actually read the commit logs

19:04 <novakane> so this confirms that river users are the best then :P

19:07 <ifreund> :)

20:54 <elshize> ifreund: I figured out how to reproduce the border issue: https://github.com/ifreund/river/issues/375

20:55 <elshize> seems that only qt apps are affected (I don't actually get it with firefox, as I previously said, must have remembered wrong)

21:13 <ifreund> elshize: nice! I'll take a look when I have a minute