G. Branden Robinson to Anton Shepelev:
> > `export | grep -i sgr' finds nothing, unfortu-
> > nately. Where else can I look for the reason of
> > -man treating my virtual terminal as a printer?
> > Once I find it, I will bring it up with the ad-
> > ministrator of that system, and then pe
Hi Anton,
At 2023-11-20T18:38:19+0300, Anton Shepelev wrote:
> G. Branden Robinson to Anton Shepelev:
> > If you're still using groff 1.22.4, some distribu-
> > tions used a device control command to tell
> > grotty(1) to shut off SGR support.
>
> Indeed. /etc/groff/man.local contains:
>
Dear All,
in April 29, I asked whether there is a possibility to resume one-column
text after a two-column text on the same page. Your answers, uni sono,
said what the the manual says: returning to one-column mode will always
finish the page and begin a new one.
The reason for this behaviour is
Dear All,
in a follow-up to myself:
If I understood where the whole .1C definition ends, I could copy that
block into an own macro definition and from there eliminate just those
commands which flush the old page and begin a new page. I could even
ignore the tests for floats and footnotes because
Another follow-up:
I just checked the one-column mode across the macro packages ms, me and
mm, and lo and behold, the mm man page tells me:
1C [1] Begin one-column processing. A 1 as an argument disables
the page break. Use wide footnotes, small foot‐
notes may be overprinted
Dear All,
I tried the mm macros.
In general, the idea to have a horizontal object spanning the full page
width between two portions of text in two columns can be realized with mm.
The .1C 1 macro with the argument "1" does the trick. There is one
caveat, though. mm does not balance columns, so
Dear All,
I am not going to bother you anymore with my column journey.
.NCOL
in the mm package does the trick. It allows breaking a column, and since
this is a one-time task, I do not mind searching for the optimal
breakpoint by hand.
All my questions of April 29 answered! Thank you all for yo
