Hi Ihor,
At 2025-01-19T14:04:21+, 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::2: warning: cannot select font 'C'
> > One two thr
At 2025-01-20T03:27:07+0100, Ingo Schwarze wrote:
> > The definitions are generated automatically, so all manpages written
> > in mdoc benefit from it. I assume groff mdoc + man-db doesn't
> > implement this?
>
> Not that i know of. It would actually be much harder to implement
> in groff than i
Hi onf,
At 2025-01-20T01:48:19+0100, onf wrote:
> Actually, BSD mandoc does implement this, it's just documented at
> a poorly visible place in the docs. BSD mandoc's man(1):
> MANPAGER
> Any non-empty value of the environment variable MANPAGER is
> used instead of the standard pagin
At 2025-01-20T16:43:34-0600, G. Branden Robinson wrote:
> I'm attaching the current version of my "make-groff-fast" script,[1]
> which I run _all the time_.
Take a drink and/or claim your wager winnings.
Regards,
Branden
#!/bin/sh
set -e
: ${TAG:=HEAD}
: ${DESTDIR:=$HOME/groff-$TAG}
PROGNAME=$
Hello Tadziu,
Tadziu Hoffmann wrote on Tue, Jan 21, 2025 at 12:01:12AM +0100:
>> when designing a markup language, permitting the inclusion
>> of chunks written in a different markup language is usually
>> terrible language design.
> Isn't that what tbl, pic, chem, and all the rest are?
> So far
> when designing a markup language, permitting the inclusion
> of chunks written in a different markup language is usually
> terrible language design.
Isn't that what tbl, pic, chem, and all the rest are?
So far the idea has worked quite well over the years.
At 2025-01-20T12:38:24-0500, T. Kurt Bond wrote:
> I always install a personal copy of groff in a directory that my user
> owns, ensure that is in the path before the location of the system
> groff, and never use root access for installing fonts. I realize this
> may not be suitable for everyone.
At 2025-01-20T18:15:48+0100, Francesco Ariis wrote:
> Hello groff users,
>
> how to convert .tff fonts to something usable by `groff`, without
> sudo access?
In groff 1.23.0, both the grops(1) and gropdf(1) man pages document a
procedure for doing this. It is admittedly more tedious than usi
On Mon Jan 20, 2025 at 10:22 PM CET, Ingo Schwarze wrote:
> T. Kurt Bond wrote on Mon, Jan 20, 2025 at 12:57:16PM -0500:
> > Branden said:
> >> As far as I know, none of pod2man(1), asciidoctor(1), docutils(1),
> >> or pandoc(1) supports a syntax for inlining "raw" man(7)/*roff
> >> source into a d
Ingo says:
> Sure, if your personal task is to write one document with one single
output format in mind, even a tool containing that design mistake
can prove adequate and helpful in that particular case.
But that is not my personal task: my task is to generate output in multiple
formats, which raw
Hello,
T. Kurt Bond wrote on Mon, Jan 20, 2025 at 12:57:16PM -0500:
> Branden said:
>> As far as I know, none of pod2man(1), asciidoctor(1), docutils(1),
>> or pandoc(1) supports a syntax for inlining "raw" man(7)/*roff
>> source into a document.
Since this point keeps getting discussed, i'll br
Branden said:
> As far as I know, none of pod2man(1), asciidoctor(1), docutils(1), or
pandoc(1) supports a syntax for inlining "raw" man(7)/*roff source into a
document.
I'll note that this is a standard part of reStructuredText, which pandoc
supports, and while I have not used it with pandoc's ma
It seems the mailing list doesn't like my message for some reason.
Let me try again for the 3rd time...
Forwarded message from onf on Mon Jan 20, 2025 at 2:27 PM:
Hello Ingo,
On Mon Jan 20, 2025 at 3:27 AM CET, Ingo Schwarze wrote:
> onf wrote on Mon, Jan 20, 2025 at 01:48:19AM +0100:
> > On Mon
I always install a personal copy of groff in a directory that my user owns,
ensure that is in the path before the location of the system groff, and
never use root access for installing fonts. I realize this may not be
suitable for everyone.
T. Kurt Bond, tkurtb...@gmail.com, https://tkurtbond.git
Hello groff users,
how to convert .tff fonts to something usable by `groff`, without
sudo access?
I am learning groff and I feel thee need to use a fonts with more
glyphs than what standard fonts offer (e.g.: ◇ U+25C7, ❦ U+2766, etc.)
I came around the excellent `install-font.sh` [1]. It see
15 matches
Mail list logo
