recommendations are not yet implemented, due to lack
of Tuits - assistance with improvements would certainly be
welcome.)
Alexis.
er.
Sure; as i said, i'll remove that text. When i was putting that
piece together, i was primarily focused on trying to demonstrate
how mdoc(7) _macros_ are used to write man pages, not "this is how
to write a man page in general, using mdoc(7)". Yet the title i
used for the document was "Writing man pages with mdoc(7)". :-P So
i need to change that title, and perhaps i should just use lorem
ipsum in the contents of the example man page
Alexis.
between them).
Sure.
When you write:
Note that we made no roff requests directly; only roff macros
were
used.
I feel like s/roff/mdoc/2 would convey the meaning better.
Yeah, fair enough.
I can also imagine that a section about tbl would come in handy.
In a complete guide to writing man pages with mdoc,
definitely. :-) But yeah, as i wrote above, i'm just trying to
give people the flavour of writing man pages with mdoc, hopefully
convincing them that it's not as scary and difficult as they might
have thought. :-)
Thanks for the feedback!
Alexis.
ded semantics and particular presentational markup to be
discouraging. i don't know how i stumbled across mdoc(7), but
once i did, and discovered that it could be used for man pages on
Linux via groff, i focused on learning and using mdoc(7).
To try to demystify it for others, i wrote this quickstart guide:
https://github.com/flexibeast/guides/blob/master/mdoc-quickstart.md
Alexis.
API documentation for something like 15 years.
i'm sure "contributions are welcome" - you have nothing else on
your plate, so why not become familiar with the codebase and write
the documentation based on your understanding of how it all seems
to work? /snark
Alexis.
t (setting aside case):
man(7) 'SY', Synopsis Start, vs mdoc(7) 'Sy', Symbolic
i.e. boldface. Use man(7) or mdoc(7), but if you're writing
mdoc(7), write mdoc(7). :-)
Alexis.
i don't have any projects on GitLab myself, but do their
heuristics look for a file named LICENSE, rather than one named
COPYING?
"G. Branden Robinson" writes:
This seems a bit dubious. I'm logged in and can't see how to
fix it.
I guess GitLab is doing their part is the glorious strugg
Gáspár Gergő writes:
Maybe it's just some issue with the Void gsfonts package then.
What's the output of `xbps-query -f gsfonts`?
Alexis.
On Thu, Apr 04, 2024 at 08:26:44PM -0500, G. Branden Robinson wrote:
> Alexis, would you like to look into this more deeply, and maybe find a
> solution that will enable us to use ps2ps after all?
Of course, Branden. Just to be sure I use the same code-path as you
did which command(s) did y
n name,
but a different email address.
The important bit is: the change is coming to Groff :)
Best
Alexis
¹
https://git.savannah.gnu.org/cgit/groff.git/commit/?id=3bde75a958f5f3eea84f1e0098c7b457358792b3
st be given in
increasing order, you cannot process pages out of order or repeat pages
and this will generate an error."²
Do let me know if you desire or require further testing or changes, or
if I can be helpful in other ways to drive this change forward.
Best
Alexis
¹ Checking the differences
d to serve as a reference?
And what is preferred procedure to propose a change to groff if it's
not through patches to this list?
Grüße vom Landwehrkanal
Alexis
detail which parts of the documentation
exactly you were referring to and how they explain your disapproval to
the proposed change?
Best
Alexis
le's thoughts on this?
And what have I possibly overlooked that this isn't already the case?
Best
Alexis
diff --git a/tmac/papersize.tmac b/tmac/papersize.tmac
index e10219ad5..e1eab7c03 100644
--- a/tmac/papersize.tmac
+++ b/tmac/papersize.tmac
@@ -126,11 +126,13 @@
.ie '\
sk the groff developers to incorporate it, either via a Savannah
> ticket or this mailing list.
Will do
> If you read through the thread starting at
> https://lists.gnu.org/archive/html/groff/2021-01/msg4.html
That's very helpful!
Thanks,
Alexis
Here's the din-5008-dimensions.roff I forgot
to attach in my previous mail.
Best Alexis
\# Use the following command to typeset this document:
\# groff -Tpdf -p -dpaper=a4 -P-pa4 din-5008-dimensions.roff > din-5008-dimensions.pdf
.nop \X'ps: exec 2 setlinecap'
.nop \X'ps:
est-practices from long-term users and macro package
developers and maintainers is especially welcome and much appreciated!
Best
Alexis
¹ using the special print bundle of the DIN 5008
https://www.beuth.de/de/publikation/paket-din-5008-das-praxispaket/321130650
² Also happy to share my previous
/bookworm/ffmpeg/ffmpeg.1.en.html
Alexis.
perhaps by default) to support at-spi
services.
Alexis.
.
It seems I need to understand a bit more about gnulib and its role
when building groff.
Best
Alexis
¹ https://nixos.org/manual/nix/stable/command-ref/new-cli/nix3-develop.html
² https://nixos.org/manual/nix/stable/command-ref/new-cli/nix3-build.html
³ https://github.com/NixOS/nixpkgs/blob/master/p
Hi Deri,
thank you for addressing this so quickly. Unfortunately I have yet to
succeed in building groff from the deri-gropdf-ng branch using nixpgs,
yet am happy to report back once I do.
Best
Alexis
able to use a4l for both is very convenient.
Looking forward to seeing further improvements the
deri-gropdf-ng branch brings once it's merged.
If I can help with the -P-l investigation or testing
the deri-gropdf-ng branch please let me know.
Best
Alexis
Hi all,
when drawing rounded box corners with the pic preprocessor using the
pdf device while orienting the document in landscape format the arcs
for the rounded corners are misplaced (see attached box_rad_devpdf.pdf).
The issue does not occur when using the ps device (see attached
box_rad_devps.p
grohtml is invoked
in a common groff pipeline or can be invoked manually for testing
purposes.
Anyone willing to share some insights or ideas?
Best
Alexis
diff --git a/src/preproc/html/pre-html.cpp b/src/preproc/html/pre-html.cpp
index cbcc2ccda..1668c9f67 100644
--- a/src/preproc/html/pre-html
off, ghostscript, and psselect.
The support for pdf conversion is added for those who have the
(mis)fortune of working on macOS, which sadly has removed support
for PostScript.
Best
Alexis
PAGENO := 3
TOTAL_PAGES := 9
all: psPageName.pdf
# Extract page PAGENO from the multi-page example do
ted in Ingo's answer here, but in that
specific case, i'd simply leave 'Li' out, as it's not required. (i
presume because the 'Oo' has effectively "opened a new formatting
context" in which text is literal until a new macro is invoked,
but i'd be happy to be corrected.)
Alexis.
.
On Gentoo as well (and i switched to it myself).
Alexis.
r now then.
> Anyone who'd need to be involved in this follows this email list, so
> you're covered there.
Great!
> Thanks for offering a patch!
My pleasure. Happy to continue to work on this with the guidance of
groff developers and the community :)
Best
Alexis
ave a GitHub account, stating your
interest on the PR might help in getting it merged and a new release out.
Best
Alexis
¹ https://github.com/fukuchi/libqrencode/pull/208
nt for myself on savannah.gnu.org to
continue the conversation there or is this mailing list the
right place for this?
Which other people should be contacted and get involved?
Best
Alexis[
te and possibly even improve the current definition of paper sizes
and whether there is merit to an approach as proposed by the prototype.
How could something like this be done in a way that possibly better fits
groff's development philosophy? Does autoconf support code generation?
Should pape
.
Best
Alexis
this introduces a
little inconsistency with other paper format specifications.
What are your thoughts about naming the argument for the papersize
control command `paper-size` to distinguish it from the `paper-format`
argument of the -p option?
Best
Alexis
argument handling code a bit more in line with the code handling
the -p option argument.
Should my current understanding of groff and the implementation have
lead me astray to falsely believe there is an issue where in fact
things work the way they are supposed to I'd appreciate explanations
and
Thank you for the clarification, Deri, that makes a lot of sense.
I should've read pdf.tmac more closely and not just grep'ed for
'^\.defcolor' before making such a claim :)
macro implementations to learn more about groff and its capabilities.
Best
Alexis
ects and things in regards to
the aforementioned inconsistency and things are as they should be.
In that case I'd appreciate pointers that would help me understand why
the things are the way they are.
Otherwise please find attached a patch that removes the leading period
`.` from the \n[lsn] a
Thank you, Colin.
For folks interested to follow along or participate in the conversation
the related man-db issue is:
https://gitlab.com/man-db/man-db/-/issues/25
the right place for this
conversation or whether it should rather be held elsewhere.
Best,
Alexis
on on the PR now needs to be around what the
default output format for manpages on NixOS should be default, i.e.
SGR and OSC enabled vs legacy, i.e. SGR and OSC shut off.
This is likely going to be an interesting conversation. Happy to report
back once there is a path forward.
Thanks again!
A
ake on it and how to possibly fix the test failures
should they be related to the update to groff 1.23.0?
Regardless of any NixOS/nixpkgs related woes:
Thank you for all the work and effort put into the release!!
Best
Alexis
¹ https://github.com/NixOS/nixpkgs/pull/241870
² https://savannah.gnu.org/bugs/?61561
e parts might need changing and possible have
a first go at it.
What are your thoughts?
Best
Alexis
# Generate Computer Modern Unicode font files for use with groff
# https://cm-unicode.sourceforge.io/
VERSION := 0.7.0
HASH:= f7c9209524dfe1dd40e680139645d07b2c34b187a4121ec444909d6429e2c76e
tion file validation[1] than
> 1.22.4 did.
It seems I was using groff 1.22.4 the whole time while working on this
unaware that groff 1.23.0 does a lot more validation.
> Maybe the Makefile from this thread should be updated to run sed(1) on
> the generated font description file--just a guess, I haven't even looked
> at it yet.
I'll look into changing the Makefile to work better with groff 1.23.0.
Alexis
e. `-mcmu` or from within your document via
`.mso cmu.tmac`.
As an example the following command produces the documentation
for the ms macro package using Computer Modern Unicode:
% groff -Tpdf -t -ms -mcmu doc/ms.ms > doc/ms.pdf
Hope this helps
Alexis
¹ For those wondering: The Makefile
13578&w=2
and in particular Ingo's comment:
https://marc.info/?l=mandoc-discuss&m=160668087317110&w=2
(This is all a result of my stubborn insistence on using mandoc on
Gentoo. :-) )
Alexis.
#c1
On Gentoo, man page compression is affected by user-specified
values for PORTAGE_COMPRESS and PORTAGE_COMPRESS_EXCLUDE_SUFFIXES;
PORTAGE_COMPRESS is set to 'bzip2' by default.
Alexis.
y were still doing so as late as
glibc 2.30,
3 years ago.)
Does this help?
Thanks, i've just opened a bug on the Gentoo bug tracker about
this, "man pages for alternatives: Use of .so instead of symlink
creates issue when using mandoc":
https://bugs.gentoo.org/905624
in which i reference this thread.
Alexis.
Ping. Does anyone have any thoughts on this? It's a small but
persistent irritation on my system. :-)
Alexis writes:
[1. text/plain]
Hi all,
On my Gentoo system, awk.1 simply contains an .so request whose
argument is the man page for the actual awk implementation in
use,
i.e.
t .so in the mandoc TODO
list[b].
i've no idea what the 'correct' behaviour 'should' be, from
whatever perspective (historical / security / groff-compatibility
/ etc.), so am cross-posting to what i believe to be the relevant
lists.
Alexis.
[a]
https://cvsweb.bs
pp-text/mandoc bzip2 support"
https://bugs.gentoo.org/854267
"Remove /usr/share/man from default inclusion list for docompress"
https://bugs.gentoo.org/836367
Alexis.
lob/master/minimal-epub.md
together with an accompanying POSIX shell script:
https://github.com/flexibeast/epub-create
Alexis.
ROR: 0
I'd be happy to answer all your questions in your previous email if you
see value in it. Otherwise in the interest of your valuable time I'll
keep it short :)
Cheers
Alexis
=groff
Please find attached the mentioned test-suite.log.
Happy to answer any questions regarding my build and test setup and test
patches as needed.
Hope this helps!
Alexis
===
GN
m documentation, and not
only managed to tag releases without crucial Makefile changes, but
also amended the commits instead of tagging new releases. :-/
Release process checklist updated. :-P
Alexis.
as intrigued by that one, and did some research. The
gss-group1-sha1-* algorithms were deprecated via a "SHOULD NOT" in
RFC8732, published in February 2020, due to having "small key
lengths and are no longer strong in the face of brute-force
attacks":
https://www.rfc-editor.org/rfc/rfc8732#name-deprecated-algorithms
Alexis.
g, or not
doing something right?
Alexis.
man-group1-sha1
i believe the relevant ssh option is 'KexAlgorithms', e.g.:
ssh -o KexAlgorithms=diffie-hellman-group1-sha1
Alexis.
lt.nix
$ ls -lsa outputs/out/bin/groff
416 -rwxr-xr-x 1 $USER staff 209808 Feb 10 07:21 outputs/out/bin/groff
$ ./outputs/out/bin/groff --version | head -1
GNU groff version 1.23.0.rc2.22-55d3
Best
Alexis
html
More generally, refer to:
https://wiki.musl-libc.org/compatibility.html
Or have I mis-understood
i understood Alejandro to be talking about a 'modularised' libc,
i.e. one containing multiple components ('microlibraries'), but
i'll let Alejandro clarify.
Alexis.
Engine.cc:
fprintf(stderr, "some font thing failed\n");
Alexis.
05
i doubt i'd have had as much enthusiasm for creating the man page
ports of s6-related documentation if i'd had to use DocBook,
rather than being able to use mdoc(7). In fact i probably wouldn't
have done them at all.
Alexis.
not ideal. If
this
is any
use you can build the pdf with:-
gunzip mom-book.mom.gz
pdfmom mom-book.mom > mom-book.pdf
Oh wow, thank you! Very kind of you. :-)
Alexis.
Peter Schaffter writes:
Thanks for the doc fixes for mom. I've been meaning to get out
the
broom and clean them up. This is a great help.
Ah good! You're welcome. :-)
Alexis.
t allowed in this
context" and "Unknown element" errors. The latter were caused by
the use of ''; i gather one one is supposed to instead use
the 'white-space' CSS property.
Alexis.
diff --git a/contrib/mom/momdoc/docelement.html b/contrib/mom/momd
laggy Word
and inconsistent styling issues. I don’t want KOMA-Script woes and
minutes–long compile times. I want something simple that works:
groff!"
-- https://jstutter.netlify.app/#220721-writing-my-phd-using-groff
Alexis.
65 matches
Mail list logo
