On Sun Jan 19, 2025 at 5:38 PM CET, onf wrote:
> On Sun Jan 19, 2025 at 3:04 PM CET, Ihor Radchenko wrote:
> > "onf" writes:
> > >> I am wondering if the situations like the above should be caught by
> > >> groff linter. Currently, t
On Sun Jan 19, 2025 at 3:04 PM CET, Ihor Radchenko wrote:
> "onf" writes:
> >> I am wondering if the situations like the above should be caught by
> >> groff linter. Currently, they seem not.
> >
> > They actually are:
> > ...
> > troff:
On Sun Jan 19, 2025 at 8:43 AM CET, Ihor Radchenko wrote:
> "G. Branden Robinson" writes:
> >> What about \fC\f[CR]Lorem\fP\fP?
> >
> > Unreliable. As onf pointed out, not only is the font selection not
> > backed up by a stack, but it the identity of &qu
Hi Branden,
On Sat Jan 4, 2025 at 7:37 AM CET, G. Branden Robinson wrote:
> At 2025-01-04T01:23:02+0100, onf wrote:
> [...]
> > Speaking of the left italic correction (\,), could you please give me
> > some example(s) where it's actually useful? I have yet to see a singl
Hi Branden,
On Fri Jan 3, 2025 at 9:38 AM CET, G. Branden Robinson wrote:
> At 2025-01-02T15:29:59+0100, onf wrote:
> > I don't know why it took me so long, but I think what you're looking
> > for is this:
> > \fC\f(CRLorem\fR
>
> Not a bad idea, but while
On Thu Jan 2, 2025 at 6:47 PM CET, Ihor Radchenko wrote:
> "onf" writes:
> [...]
> > It's important to understand that troff commands don't really use
> > nesting or a stack as one might be used to from HTML and similar
> > markup languages. That's
Hi Ihor,
On Wed Jan 1, 2025 at 1:30 PM CET, onf wrote:
> On Wed Jan 1, 2025 at 10:38 AM CET, Ihor Radchenko wrote:
> > >> Also, what if we leave \fC and add \f[CR]/.EX on top?
> > >> AFAIU, the worst case scenario for \fC is that it does nothing. By
> > >&g
acing and sometimes ignored?
>
> Yes. A blank line is ignored when the formatter's "no-space mode" is
> enabled.
>
> [...]
Just to clarify, .sp is ignored in such cases as well.
~ onf
add blank after blocks (or displays) of code. Extra
> vertical space after seems to be reasonable.
They are equivalent as far as troff formatters are concerned. The question
is whether they are equivalent to the various other programs that attempt
to interpret man source code directly. So I guess this depends on whether
you're targetting only troff (+ BSD mandoc) or not. Branden will likely
tell you more about this topic.
~ onf
t blank line is sometimes interpreted as
> vertical spacing and sometimes ignored?
A blank input line is equivalent to .sp unless the .blm request was called
to change this behavior. .blm is groff's invention (see groff_diff(7)).
~ onf
On Tue Dec 31, 2024 at 7:42 PM CET, onf wrote:
> Branden will likely provide you with a more detailed description, but
> in short, displays are text that is set off from the rest. Example from
> groff(7):
> [...]
> Checking the manpage's source shows that this is done precise
11 matches
Mail list logo
