13:53 <Guest84> ChatGPT said tag=2 would send an application to the correct desktop but it doesn't is ChatGPT wrong?

13:57 <TheAnachron> when in doubt, chatGPT is always wrong.

13:57 <TheAnachron> If you could tell us what you are doing, what you expected to happen and what happened instead, that would be quite helpful

13:59 <TheAnachron> Ohh, I was 2 minutes too late. Guess people nowadays have zero patience.

14:01 <Nickli> 4 seconds awway from 2 minutes

14:02 <Nickli> ..even

14:16 <leon-p> I am genuinely confused why people would rather ask overconfident-idiot-as-a-service than read the docs. I get that the man page format isn't exactly great, but we also have other forms of (unofficial/informal) documentation and we put a significant amount of time into making them understandable

14:19 <TheAnachron> if you dont like the manpage format, you can use pandoc or just use something like https://manpages.debian.org/unstable/aerc/aerc-config.5.en.html that everybody is used to read

14:19 <leon-p> also still wondering how the wording around tags can be improved, since it seems to confuse a lot of people. it's hard to know in what sense something is complicated to understand when you already know it well, but I am genuinely baffled none of the explanations we had were good enough

14:20 <leon-p> TheAnachron: you don't even need pandoc, man itself can convert to other formats

14:20 <TheAnachron> leon-p: never used the -T argument, but good to know it exists!

14:21 <leon-p> I wish there was a better man page viewer. emacs of course as two built in, both better than terminal man, but it's still not quite as good as it could be

14:21 <TheAnachron> How would that look like?

14:22 <leon-p> one major improvement would be an automatically generated outline of all sections

14:22 <leon-p> proper resize handling

14:23 <leon-p> the ability to have hyperlinks to other man pages

14:23 <Nickli> that sounds like a wiki

14:24 <TheAnachron> Agreed, whats wrong with the online manpages which do all of that?

14:24 <leon-p> also the "best practices" need updating: most man pages are just reference docs, however proper documentation should also include some form of a "getting started" guide and similar for commonly encountered questions

14:24 <leon-p> TheAnachron: because their online

14:25 <leon-p> see info / texinfo for how a good man replacement could look like, with the caveat that info is held back by it's miserable UI

14:27 <TheAnachron> leon-p: I find it confusing on when to look at what manpage. Different maintainers use different numbers for the same purpose.

14:28 <leon-p> there is supposed to be a standard, but not everyone always follows it :/

14:29 <leon-p> you can use the `apropros <keyword>` command, not ideal but better than nothing

14:30 <TheAnachron> there is also tldr which is community based

14:32 <leon-p> anyway, this is off-topic and I technically have work to do, so...

14:37 <leon-p> I procrastinated a bit further and seems like river is now also an officially supported wayland server for lxqt in addition to xfce. neat

14:45 <Nickli> that's some mighty procrastination

14:47 <leon-p> (note I didn't do that, just discovered it)

15:34 <The_Buhs> can you europeans adopt me please I can clean

19:45 <Guest27> Hello. I've got a question regarding the tag system in river and possibly the river-status-unstable-v1 protocol (if I'm correct). Is there a way to retrieve information about which tags the currently focused view is assigned to? So far I tried river-bedload, ristate and lswt. They do different things but together they are able to retrieve the title

19:45 <Guest27> and state (focused, maximized, ...) of views and the state of tags in general (occupied, urgent, ...). As far as I can tell none of these tools retrieves the information I'm seeking. Did I miss something? Or is it not possible to get that information?

19:53 <novakane> Guest27: it's not possible to get this information currently

19:56 <Guest27> Thanks.