Re: Suggestion for improvement..
Bart Massey <[email protected]> Wed, 11 Feb 2026 23:17:20 -0800
| Newsgroups | gmane.comp.freedesktop.xcb |
|---|---|
| Message-ID | <CAA6gtpmLoQFLWrnCSREwG1we=HQenFXhe-eh6NHMsz9QtK3shQ@mail.gmail.com> |
--0000000000001b53ec064a9b48e5 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable The other things to keep in mind is that the XCB API is an extremely thin layer on top of the X Protocol. Generally the Protocol doc will tell you everything you need to know to use an XCB request. On Wed, Feb 11, 2026, 08:47 Robert Knutsson <[email protected]> wrote: > I can=E2=80=99t speak for why the request in question is t documented, bu= t in > general as the documentation part of the XML protocol descriptors was a > later addition (roughly 10 years after the initial implementation if memo= ry > serves), it=E2=80=99s a matter of someone just doing the work and migrati= ng any > existing documentation or writing new. > > Glad you found what you where looking for. > > If you feel important documentation is missing do create a merge request, > that=E2=80=99s the only way it will ever be improved > > Regards, > Robert > > > ons 11 feb. 2026 kl. 17:33 skrev Michael Jensen < > [email protected]>: > >> ya, google's ai has now provided an answer that at least seems >> plausible. I suppose that's why you don't get more complaints, nobody u= ses >> the manual anymore? >> >> On Tue, Feb 10, 2026 at 1:17=E2=80=AFPM Michael Jensen < >> [email protected]> wrote: >> >>> Greetings.. >>> >>> The Arch website tells me to contact you if I have any suggestions for >>> improvement. >>> Such suggestions are not hard to come by when there are large numbers o= f >>> things listed as: "TODO: NOT YET DOCUMENTED" >>> >>> The one I am particularly interested in is "exposures", from this page: >>> https://man.archlinux.org/man/xcb_clear_area.3.en >>> >>> I assume that this is not documented because people assume that it is >>> obvious. Or people are using ai to scour the web for the info. I gues= s >>> I'll try that next, seeing as an ordinary search doesn't seem to be >>> working. I can find the "official documentation" just fine.. >>> >>> -Michael.. >>> >> --0000000000001b53ec064a9b48e5 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"auto">The other things to keep in mind is that the XCB API is a= n extremely thin layer on top of the X Protocol. Generally the Protocol doc= will tell you everything you need to know to use an XCB request.</div><br>= <div class=3D"gmail_quote gmail_quote_container"><div dir=3D"ltr" class=3D"= gmail_attr">On Wed, Feb 11, 2026, 08:47 Robert Knutsson <<a href=3D"mail= to:[email protected]">[email protected]</a>> wrote:<br></div><blockquote= class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc soli= d;padding-left:1ex"><div dir=3D"auto">I can=E2=80=99t speak for why the req= uest in question is t documented, but in general as the documentation part = of the XML protocol descriptors was a later addition (roughly 10 years afte= r the initial implementation if memory serves), it=E2=80=99s a matter of so= meone just doing the work and migrating any existing documentation or writi= ng new.</div><div dir=3D"auto"><br></div><div dir=3D"auto">Glad you found w= hat you where looking for.</div><div dir=3D"auto"><br></div><div dir=3D"aut= o">If you feel important documentation is missing do create a merge request= , that=E2=80=99s the only way it will ever be improved=C2=A0=C2=A0</div><di= v dir=3D"auto"><br></div><div dir=3D"auto">Regards,</div><div dir=3D"auto">= Robert</div><div dir=3D"auto"><br></div><div><br><div class=3D"gmail_quote"= ><div dir=3D"ltr" class=3D"gmail_attr">ons 11 feb. 2026 kl. 17:33 skrev Mic= hael Jensen <<a href=3D"mailto:[email protected]" target=3D"_bl= ank" rel=3D"noreferrer">[email protected]</a>>:<br></div><block= quote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-w= idth:1px;border-left-style:solid;padding-left:1ex;border-left-color:rgb(204= ,204,204)"><div dir=3D"ltr">ya, google's ai has now provided an answer = that at least seems plausible.=C2=A0 I suppose that's why you don't= get more complaints, nobody uses the manual anymore?</div><br><div class= =3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Tue, Feb 10, 2026= at 1:17=E2=80=AFPM Michael Jensen <<a href=3D"mailto:mikethe1wheelnut@g= mail.com" target=3D"_blank" rel=3D"noreferrer">[email protected]</= a>> wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0p= x 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;padding-left:= 1ex;border-left-color:rgb(204,204,204)"><div dir=3D"ltr"><div>Greetings..</= div><div><br></div><div>The Arch website tells me to contact you if I have = any suggestions for improvement.</div><div>Such suggestions are not hard to= come by when there are large numbers of things listed as: "TODO: NOT = YET DOCUMENTED"</div><div><br></div><div>The one I am particularly int= erested in is "exposures", from this page: <a href=3D"https://man= .archlinux.org/man/xcb_clear_area.3.en" target=3D"_blank" rel=3D"noreferrer= ">https://man.archlinux.org/man/xcb_clear_area.3.en</a></div><div><br></div= ><div>I assume that this is not documented because people assume that it is= obvious.=C2=A0 Or people are using ai to scour the web for the info.=C2=A0= I guess I'll try that next, seeing as an ordinary search doesn't s= eem to be working.=C2=A0 I can find the "official documentation" = just fine..</div><div><br></div><div>-Michael..</div></div> </blockquote></div> </blockquote></div></div> </blockquote></div> --0000000000001b53ec064a9b48e5--