Hi Alex,
At 2024-12-01T15:17:22+0100, Alejandro Colomar wrote:
> I was wondering if it would be good to nest SY/YS.
>
> What do you think of this?:
>
> .SY void\~*bsearch (
> .BI const\~void\~ key [. size ],
> .BI const\~void\~ base [. size \~*\~. n ],
> .BI si
Hi Branden,
I was wondering if it would be good to nest SY/YS.
What do you think of this?:
.SY void\~*bsearch (
.BI const\~void\~ key [. size ],
.BI const\~void\~ base [. size \~*\~. n ],
.BI size_t\~ n ,
.BI size_t\~ size ,
.br
-.BI int\~(* compar )(const\~void\~[. size ],
+.SY int\~(*\f
On Sat, Jul 13, 2024 at 10:46:17AM GMT, G. Branden Robinson wrote:
> Hi Alex,
Hi Branden,
> At 2024-07-13T17:38:17+0200, Alejandro Colomar wrote:
> > > Try the attached patches.
> >
> > They don't seem to apply.
>
> Alas, that's life when you're not on my working copy.
:-)
> You'll have to
>
Hi Alex,
At 2024-07-13T17:38:17+0200, Alejandro Colomar wrote:
> > Try the attached patches.
>
> They don't seem to apply.
Alas, that's life when you're not on my working copy. You'll have to
either chop out the changes to ChangeLog, or wait for me to push.
That may be as soon as today, since
Try the attached patches.
They don't seem to apply.
Applying: Test `YS` macro harder.
error: patch failed: ChangeLog:1
error: ChangeLog: patch does not apply
Patch failed at 0001 Test `YS` macro harder.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When y
1
From: "G. Branden Robinson"
Date: Sat, 13 Jul 2024 09:57:08 -0500
Subject: [PATCH 1/2] [man]: Test `YS` macro harder.
* tmac/tests/an-ext_SY-and-YS-work.sh: Test new behavior of `YS` when
given an argument.
Test fails at this commit.
---
ChangeLog | 5
Hi Alex,
At 2024-07-13T15:23:19+0200, Alejandro Colomar wrote:
> Was the trailing dummy string for YS to allow alignment finally merged?
Yes, sort of--it seems I managed to screw it up. On top of that I wrote
a particularly dumb test for it.
.B int
.SY a2s (
.B TYPE,
.BI TYPE\~*restrict\
Hi Branden,
Was the trailing dummy string for YS to allow alignment finally merged?
I built groff(1) from git HEAD and lost that functionality.
Below is the head of a manual page for libs, a string library that I'm
writing:
$ cat stpeprintf.3
.\" Copyright 2024
Hi Branden,
On 3/23/23 22:22, G. Branden Robinson wrote:
> Hi Brian,
>
> At 2023-03-16T19:39:27-0600, Brian Inglis wrote:
>> Output of man pages with lengthy synopses from grohtml do not disable
>> adjustment and hyphenation as for tty, breaking long options between
>> the hyphens and anywhere el
At 2023-03-23T16:22:51-0500, G. Branden Robinson wrote:
> I am attaching the [...] output from groff compiled from the tip of the
> 'branden-post-1.23.0' Git branch,
Today I learned that the GNU mailing list management software strips
HTML attachments.
Let me know if you need it.
Regards,
Brande
Hi Brian,
At 2023-03-16T19:39:27-0600, Brian Inglis wrote:
> Output of man pages with lengthy synopses from grohtml do not disable
> adjustment and hyphenation as for tty, breaking long options between
> the hyphens and anywhere else available.
[snip]
I cannot reproduce this problem with groff Gi
B\-\-sheetname sheetname
.OP \-i\fR|\fB\-\-ignoreempty
.OP \-\-skipemptycolumns
.OP \-p\fR|\fB\-\-sheetdelimiter sheetdelimiter
.OP \-q\fR|\fB\-\-quoting quoting
.OP \-s\fR|\fB\-\-sheetid sheetid
.OP \-\-include\-hidden\-rows
.I xlsxfile
.RI [ outfile ]
.SY xlsx2csv
.BR \-h | \-\-help
.SY xlsx2csv
presentational markup when output to PostScript
* allows semantic analysis
* is portable ..."[1]
> Please, Branden, bring us good ideas. Discovering the .SY/.YS and .OP
> macros made my SYNOPSIS sections much more consistent. Yes, I had a
> couple of cases where .OP does
* On 2018 27 Jun 11:52 -0500, G. Branden Robinson wrote:
> > I'm still hoping that at some point, we may be able to get the
> > groff manual pages at least half-portable, even though that may
> > still be a long way. Use of .SY/.YS is a major step backwards.
>
>
At 2018-06-27T16:13:09+0200, Ingo Schwarze wrote:
> Hi Branden,
>
> G. Branden Robinson wrote on Wed, Jun 27, 2018 at 09:16:18AM -0400:
>
> > I'm in the midst of preparing a commit to make sure all the groff
> > man pages have Synopsis sections that (1) use .
Hi Branden,
G. Branden Robinson wrote on Wed, Jun 27, 2018 at 09:16:18AM -0400:
> I'm in the midst of preparing a commit to make sure all the groff
> man pages have Synopsis sections that (1) use .SY and .YS (and .OP
> where feasible),
Must you really do that?
I'm still
16 matches
Mail list logo
