On 05/02/2022 13:05, nick black wrote: > indeed, the cursor location report fix is only on a branch. i'll > go ahead and submit it to this other fork, and rebase mine off > of theirs. thank you likewise for bringing this to my attention! > i'm glad to see kmscon getting some love.That would be great. I'd like to ask Aetf for a versioned release as well, but first I'd like to get composing working. There's an open issue for that and I independently had a patch for that as well, so I'll see if I can get that upstreamed.
> i'm the maintainer and upstream author of Notcurses, and kmscon > is very much a target of mine. if you'd like to integrate any > Notcurses stuff into your testing, just hit me up; i'd be happy > to help!I would like something a bit more formal to test kmscon. So far I've just been testing out different modes and see if aptitude draws everything correctly, but that's hardly a decent compliance test.
On 05/02/2022 13:08, nick black wrote: > also, there is a kmscon repo under the auspices of the > freedesktop.org organization. i talked to the original author > about removing that if he wasn't going to be taking the project > forward, but it didn't go anywhere. if someone's really picking > kmscon up, they might want to go talk to the fdo people. On 05/02/2022 13:11, nick black wrote: > ahh, rereading your original ITP, i see you know all about the > fdo situation. good deal =]. i just killed my fork, and am going > to submit a PR to Aetf's fork.It would be great if it could be moved back under FDO auspices, but I haven't tried to contact them, yet. Going by your experiences that might not be worth the effort then.
Attachment:
OpenPGP_signature
Description: OpenPGP digital signature