Hey Alex,
Thanks a lot for the clarifications, I agree with your reasoning.
On Mon, May 1, 2023 at 8:30 PM Alejandro Colomar wrote:
> What is ventilated in the context of prose? Not too clear to me just by
> reading dict(1).
Regarding "Ventilated Prose", it's more of an endearing figure of spe
On 5/1/23, Oliver Corff wrote:
Also, how do I force a column to break? .bp forces a page break, it
does not break a column.
...
> I found that me has a .bc macro which simply is defined as .sp 24i and
> it works as desired.
It works as desired in many situations, and this is how -me def
On 5/2/23 00:21, josh wrote:
> Hi, I'm here with a quick tangent.
Hi Josh,
>
> It turns out that there is a lot of discourse out there about "semantic
> newlines", under a few different names. So far the names I've seen are:
>
> - One Sentence Per Line (OSPL)
This forgets about clauses and phr
Hi, I'm here with a quick tangent.
It turns out that there is a lot of discourse out there about "semantic
newlines", under a few different names. So far the names I've seen are:
- One Sentence Per Line (OSPL)
- Semantic Line Breaks (SemBr)
- Semantic Linefeeds
- Ventilated Prose
- Semantic newli
Hi Peter,
On 30/04/2023 02:15, Peter Schaffter wrote:
Also, how do I force a column to break? .bp forces a page break, it
does not break a column.
Mom has .COL_NEXT (quad and break) and .COL_BREAK (force justify
["spread"] and break).
I found that me has a .bc macro which simply is defined
Hi Ralph,
On 30/04/2023 10:33, Ralph Corderoy wrote:
Hi Oliver,
BTW, are you subscribed to groff@gnu.org? If so, I'll stop mailing you
directly too.
Indeed I am subscribed to groff@gnu.org --- I simply hit "Reply All"
because currently your address is in the "To:" field while the mailing
list
Hi Dave,
On 30/04/2023 04:22, Dave Kemper wrote:
On 4/29/23, Oliver Corff wrote:
Is there any possibility to count leading spaces in groff?
See the documentation for the \n[lsn] register. I've never used it,
but its description sounds like what you're looking for.
I'll have a look at that.
Hi Branden,
On 30/04/2023 15:35, G. Branden Robinson wrote:
At 2023-04-29T21:38:53-0500, Dave Kemper wrote:
On 4/29/23, Oliver Corff wrote:
Would it be a feasible option to use UTF-8 throughout the inner
workings of a future groff,
I'm going to phrase this more confrontationally than it need
Hi Branden,
On 30/04/2023 14:50, G. Branden Robinson wrote:
At 2023-04-29T21:22:00-0500, Dave Kemper wrote:
On 4/29/23, Oliver Corff wrote:
Is there any possibility to count leading spaces in groff?
See the documentation for the \n[lsn] register. I've never used it,
but its description sou
Hi Branden,
On 30/04/2023 00:07, G. Branden Robinson wrote:
There's no inherent support for this. It afflicts multiple macro
packages, though I don't know what mom(7) does.
Thank you for the clarification.
The problem is that it is hard to say under that circumstance what the
right thing to
On Monday, 1 May 2023 13:11:39 BST G. Branden Robinson wrote:
> We might need to start thinking about loosening the invariant that the
> default family is always 'T'. The formatter could still start up that
> way, but maybe the ja.tmac and zh.tmac (and potential future ko.tmac)
> localization macr
At 2023-04-30T21:21:11+0100, Deri wrote:
> When viewing Japanese man pages it used to be necessary to pass the
> flag -f setting the default font family to a Japanese font which
> affected both the body of a man page and the headings, in bold, when
> viewing the grops output of a japanese man page.
Hi Alex,
At 2023-05-01T00:15:55+0200, Alejandro Colomar wrote:
> You could try it (but C++ will only work as long as it resembles C;
> and you need to specify the file suffix).
I prefer C to C++ when I have a choice. groff doesn't give me one. ;-)
But I'm also accustomed to ctags(1) and cscope
13 matches
Mail list logo
