Hi Alex,
At 2025-05-02T17:34:41+0200, Alejandro Colomar wrote:
> On Fri, May 02, 2025 at 09:51:04AM -0500, G. Branden Robinson wrote:
> > ---snip---
> > PDP-11 simulator V3.8-1
> > Disabling XQ
> > @boot
> > New Boot, known devices are hp ht rk rl rp tm vt
> > : rl(0,0)rl2unix
> > mem = 177856
> >
On 3/5/25 10:34, G. Branden Robinson wrote:
As I conceptualize it, no. The line is already in perfect adjustment.
Relatedly, the `distribute_space()` function in GNU troff returns early
if (1) there amount of space required to bring the output line up to the
configured line length is zero; (2)
Hi Alex,
At 2025-05-02T16:59:58+0200, Alejandro Colomar wrote:
> On Fri, May 02, 2025 at 09:19:48AM -0500, G. Branden Robinson wrote:
> > Your grog executable may be out of sync with the man page you're
> > reading.
> >
> > Compare `type grog` with `man -w grog`.
>
> H.
>
> alx@devuan:~$ wh
Hi Doug,
At 2025-05-02T19:47:45-0400, Douglas McIlroy wrote:
> > To illustrate, in the following "A" means an output line requiring
>> adjustment; "F" a line that is "full" and does not; and "L" and "R"
>> indicate distribution of adjustment spaces from the left and right,
>> respect
[adding Joey Hess to CC to refresh my memory on bricktext--see below]
At 2025-05-02T20:46:47+0200, Martin Lemaire wrote:
> Although Gutenberg had a major impact on printing in the 15th century,
> there are traces in Asia of xylogprahy[1] as early as the 6th century.
> It is argued that western ed
> To illustrate, in the following "A" means an output line requiring
> adjustment; "F" a line that is "full" and does not; and "L" and "R"
> indicate distribution of adjustment spaces from the left and right,
> respectively.
> groff 1.22.4groff 1.23.0
> ---
Although Gutenberg had a major impact on printing in the 15th century,
there are traces in Asia of xylogprahy[1] as early as the 6th century.
It is argued that western educations give the guy too much credit.
His contribution to the craft was more about crafting inks allowing the
printing on both
On Fri, May 2, 2025 at 8:07 AM Martin Lemaire wrote:
> Off-topic to Alejandro's initial question but related to the subject of
> justifying text set in monospace, do we owe this typographic gesture to
> the early *roff formaters or was it already a thing in previous
> publication tool, either soft
Hi Branden,
On Fri, May 02, 2025 at 09:51:04AM -0500, G. Branden Robinson wrote:
> At 2025-05-02T15:06:46+0200, Martin Lemaire wrote:
> > Thank you Branden for those historical insights.
> > Off-topic to Alejandro's initial question but related to the subject of
> > justifying text set in monospa
Hi Branden,
On Fri, May 02, 2025 at 09:29:07AM -0500, G. Branden Robinson wrote:
> At 2025-05-02T14:42:12+0200, Alejandro Colomar wrote:
> > By default, I prefer keeping adjustment. Often, I want to see changes
> > in adjustment too as part fo the diff. Maybe I should add an option to
> > disabl
Hi Branden,
On Fri, May 02, 2025 at 09:19:48AM -0500, G. Branden Robinson wrote:
> Hi Alex,
>
> At 2025-05-02T14:26:23+0200, Alejandro Colomar wrote:
> > On Fri, May 02, 2025 at 07:01:39AM -0500, G. Branden Robinson wrote:
> > > [2] $ type mailman
> > > mailman is a function
> > > mailman ()
> >
At 2025-05-02T15:06:46+0200, Martin Lemaire wrote:
> Thank you Branden for those historical insights.
> Off-topic to Alejandro's initial question but related to the subject of
> justifying text set in monospace, do we owe this typographic gesture to
> the early *roff formaters or was it already a
Hi Alex,
At 2025-05-02T14:42:12+0200, Alejandro Colomar wrote:
> By default, I prefer keeping adjustment. Often, I want to see changes
> in adjustment too as part fo the diff. Maybe I should add an option to
> disable adjustment optionally, which could be useful in those cases
> where the diff i
Hi Alex,
At 2025-05-02T14:26:23+0200, Alejandro Colomar wrote:
> On Fri, May 02, 2025 at 07:01:39AM -0500, G. Branden Robinson wrote:
> > [2] $ type mailman
> > mailman is a function
> > mailman ()
> > {
> > local cmd=;
> > case "$1" in
> > -*)
> > opts="$opts $1";
> >
Thank you Branden for those historical insights.
Off-topic to Alejandro's initial question but related to the subject of
justifying text set in monospace, do we owe this typographic gesture to
the early *roff formaters or was it already a thing in previous
publication tool, either software or hard
Hi Branden,
On Fri, May 02, 2025 at 07:01:39AM -0500, G. Branden Robinson wrote:
> At 2025-05-02T12:56:51+0200, Alejandro Colomar wrote:
> > I'd like to understand why groff(1) formats differently a paragraph
> > depending on the previous ones. I sometimes experience different
> > placement of sp
Hi Branden,
On Fri, May 02, 2025 at 07:01:39AM -0500, G. Branden Robinson wrote:
> [2] $ type mailman
> mailman is a function
> mailman ()
> {
> local cmd=;
> case "$1" in
> -*)
> opts="$opts $1";
> shift
> ;;
> esac;
> set -- $(man -w "$@");
Hi Alex,
At 2025-05-02T12:56:51+0200, Alejandro Colomar wrote:
> I'd like to understand why groff(1) formats differently a paragraph
> depending on the previous ones. I sometimes experience different
> placement of spaces for an unchanged paragraph. I use a script to
> diff manual pages at diffe
Hi Branden,
I'd like to understand why groff(1) formats differently a paragraph
depending on the previous ones. I sometimes experience different
placement of spaces for an unchanged paragraph. I use a script to diff
manual pages at different commits, which is useful to quickly see the
effects of
19 matches
Mail list logo
