Re: [2/2] [new port] multimedia/obs-studio

On Tue, Aug 18, 2026 at 11:24:33AM +0200, Nazarenko Mykyta wrote: > Fixed all of this stuff, now logic in frontend/utility/platform-x11.cpp > is looks pretty good, maybe import with that? Hi, looks good for me, thanks.

Re: some markup cleaning in the port-modules(5) manual

Hi Daniel, thanks for checking! Daniel Dickman wrote on Mon, Aug 17, 2026 at 08:41:25PM -0400: > I couldn't spot any issues in your proposed changes and seems like an > improvement to me. I'll commit tonight. >> . Ev MODWLROOTS_LIBDEP > > Should the space between "." and "Ev" be deleted while we're touching > this file? From a syntax perspective, it does not matter. In the roff(7) langauge, whitespace after the control character is ignored, see the roff(7) manual: REQUEST SYNTAX A request or macro line consists of: 1. the control character '.' or '\'' at the beginning of the line, 2. optionally an arbitrary amount of whitespace, 3. the name of the request or the macro, which is one word of arbitrary length, terminated by whitespace, 4. and zero or more arguments delimited by whitespace. Thus, the following request lines are all equivalent: .ig end .ig end . ig end From a style perspective, in complex roff(7) programs, people use whitespace after control characters in a way similar to indentation in C code. Here is an example from the file /usr/local/share/groff/1.24.0/tmac/doc.tmac which is an example of a very complicated macro definition file defining many complicated macros: .\" NS Ns user macro .\" NS remove space [...] .eo .de Ns . if !\n[doc-arg-count] \{\ . ie \n[.$] \{\ . ds doc-macro-name Ns . doc-parse-args \$@ . \} . el \ . doc-report-usage .Ns must be called with arguments . \} . . if \n[doc-arg-count] \{\ . nr doc-arg-ptr +1 . ie (\n[doc-arg-count] >= \n[doc-arg-ptr]) \ . doc-print-recursive . el \ . doc-reset-args . \} .. .ec Now, in contrast to macro programming, when writing manual pages, people should focus above all on good text, and then on sensible, simple markup, and avoid any kind of macro programming. Consequently, in a manual page, using this kind of indentation normally makes no sense - it certainly makes no sense in the instance you found, therefore i'll remove it. Then again, mandoc(1) does not even consider it important enough to issue a style message: $ grep '^\. ' port-modules.5 . Ev MODWLROOTS_LIBDEP $ mandoc -T lint port-modules.5 [... only messages about .Xr references to manuals pages that are parts of packages and aren't found in the base system] I don't think mandoc(1) should flag this stray blank, it really doesn't matter all that much. Yours, Ingo