[bug #64018] [man, mdoc] decide on a common base paragraph indentation

Follow-up Comment #26, bug #64018 (project groff): Not really relevant to this bug, but since all the relevant matters appear to have been addressed: [comment #15 comment #15:] > Dave Kemper and I (both Americans) have different views on > how wide the space after a sentence should be, We certai

[bug #64018] [man, mdoc] decide on a common base paragraph indentation

Update of bug #64018 (project groff): Item Group: Rendering/Cosmetics => Feature change Status: In Progress => Fixed Open/Closed:Open => Closed

[bug #64018] [man, mdoc] decide on a common base paragraph indentation

Update of bug #64018 (project groff): Status: Confirmed => In Progress Planned Release:None => 1.24.0 ___ Follow-up Comment #24: Working on this.

[bug #64018] [man, mdoc] decide on a common base paragraph indentation

Follow-up Comment #23, bug #64018 (project groff): Thanks for the history! I also don’t see it used anywhere really. >By the way, do we still have that ancient README file in the groff git tree? >I think that OpenBSD still has it lying around in the source tree in >/usr/src/share/tmac/mdoc/README

[bug #64018] [man, mdoc] decide on a common base paragraph indentation

Follow-up Comment #22, bug #64018 (project groff): [comment #15 comment #15:] > > > > We cannot, obviously, have three-letter requests. > > > Nope. Like I said, there's room for `Cq`, `Co`, and `Cc`. > > > > Indeed, I see only Co used grepping through all tmacs: > > tmac.doc.old has it as macro

[bug #64018] [man, mdoc] decide on a common base paragraph indentation

Follow-up Comment #21, bug #64018 (project groff): Regarding editing manual page source code in such a way as to avoid particularly ugly line breaks in standard-width 80 column terminal windows: [comment #12 comment #12:] > Possibly, _mdoc_(7) page authors knew this and carefully edited the ones

[bug #64018] [man, mdoc] decide on a common base paragraph indentation

Follow-up Comment #20, bug #64018 (project groff): Hmh. I personally don’t care about the obsolete/legacy man(7) macropackage, only mdoc(7), but 7n sounds like *quite* a lot, and I would rather mdoc(7) stick to 5n as it used to. ___ Reply

[bug #64018] [man, mdoc] decide on a common base paragraph indentation

Update of bug #64018 (project groff): Status: Need Info => Confirmed ___ Follow-up Comment #19: Alex's case of cringe at my `is_family_valid` function has been raised on the _groff_ development

[bug #64018] [man, mdoc] decide on a common base paragraph indentation

Follow-up Comment #18, bug #64018 (project groff): [comment #9 comment #9:] > [comment #8 comment #8:] > What do you mean by "very narrow"? Over the decades man pages have "bloated" from an expected line length of 65n to more like 78n, and even then there are many carelessly composed tbl(1) table

[bug #64018] [man, mdoc] decide on a common base paragraph indentation

Follow-up Comment #17, bug #64018 (project groff): [comment #15 comment #15:] > I regret that the implementation language makes _groff_ so stinky for people. Having seen the problems it was solving, I can understand why Clark selected it over the just-born ANSI C. It's much closer to application

[bug #64018] [man, mdoc] decide on a common base paragraph indentation

Follow-up Comment #16, bug #64018 (project groff): My stance on that is: you can do two spaces after a full stop if you want (I won’t as I’m continental-european), but not in fixed-width / monospaced settings, as the dot is already widened there by necessity. But I was just using the terms america

[bug #64018] [man, mdoc] decide on a common base paragraph indentation

Follow-up Comment #15, bug #64018 (project groff): [comment #14 comment #14:] > > Possibly, _mdoc_(7) page authors knew this and carefully edited the > > ones that did, so that now no one sees them. > > Exactly, we do that… I recently also begun rewording things to > avoid hyphenation as well, al

[bug #64018] [man, mdoc] decide on a common base paragraph indentation

Follow-up Comment #14, bug #64018 (project groff): > Possibly, _mdoc_(7) page authors knew this and carefully edited the > ones that did, so that now no one sees them. Exactly, we do that… I recently also begun rewording things to avoid hyphenation as well, although only with “french” spacing (

[bug #64018] [man, mdoc] decide on a common base paragraph indentation

Follow-up Comment #13, bug #64018 (project groff): [comment #11 comment #11:] > The codebase is the “last” nroff I could use under the Caldera licence, i.e. that was shipped with a BSD covered by these. The macropackages are a conglomerate from the TUHS archives and pre-mdocml OpenBSD’s, Is there

[bug #64018] [man, mdoc] decide on a common base paragraph indentation

Follow-up Comment #12, bug #64018 (project groff): [comment #10 comment #10:] > Merely ugly. [...] > Very ugly though ;-) Wow, you're not kidding. That's pretty awful. But given that the change in indentation amount is all it took to produce this yuckiness, I would think there have to be synops

[bug #64018] [man, mdoc] decide on a common base paragraph indentation

Follow-up Comment #11, bug #64018 (project groff): Oh sorry, submitted too early. The codebase is the “last” nroff I could use under the Caldera licence, i.e. that was shipped with a BSD covered by these. The macropackages are a conglomerate from the TUHS archives and pre-mdocml OpenBSD’s, but I

[bug #64018] [man, mdoc] decide on a common base paragraph indentation

Follow-up Comment #10, bug #64018 (project groff): Merely ugly. Old: SYNOPSIS mksh [-+abCefhiklmnprUuvXx] [-+o option] [-T [!]tty|-] [file [arg1 ...]] mksh [-+abCefhiklmnprUuvXx] [-+o option] [-T [!]tty|-] -c cmd [arg0 ...] mksh [-+abCefhiklmnprUuvXx] [-+o option] [-T [!]tty|-] -s

[bug #64018] [man, mdoc] decide on a common base paragraph indentation

Follow-up Comment #9, bug #64018 (project groff): [comment #8 comment #8:] > Just chiming in that the change from GNU groff 1.22.x to 1.23 in GNU mdoc is wrapping all my manpages badly because it reduces the already very narrow screen estate. Are the lines breaking in inappropriate places, as in

[bug #64018] [man, mdoc] decide on a common base paragraph indentation

Follow-up Comment #8, bug #64018 (project groff): Just chiming in that the change from GNU groff 1.22.x to 1.23 in GNU mdoc is wrapping all my manpages badly because it reduces the already very narrow screen estate. I’m using AT&T nroff with UCB mdoc to write my manpages, but make their rendering

[bug #64018] [man, mdoc] decide on a common base paragraph indentation

Follow-up Comment #7, bug #64018 (project groff): Not yet; I am hoping Bertrand will have some RC4 work for me today. Also, I'm not settled yet on these register names. I don't expect this change to become available until 1.23.1 or 1.24, whichever we have. _

[bug #64018] [man, mdoc] decide on a common base paragraph indentation

Follow-up Comment #6, bug #64018 (project groff): LGTM. Do you have something to test in a branch? ___ Reply to this item at: ___ Message sent via Sava

[bug #64018] [man, mdoc] decide on a common base paragraph indentation

Follow-up Comment #5, bug #64018 (project groff): To summarize, this ticket contemplates two new registers for man(7), and restricted meaning for the `IN` register, first exposed/documented by Documenter's Workbench (DWB) 1.0 in 1984. * BP: base paragraph indentation configures how far the left m

[bug #64018] [man, mdoc] decide on a common base paragraph indentation

Follow-up Comment #4, bug #64018 (project groff): [comment #3 comment #3:] > I see no reason why the standard indentation of running text from the left margin of the paper and the default indentation inside a tagged paragraph need to be related in any way. In fact, in 1990 Kernighan troff, the f

[bug #64018] [man, mdoc] decide on a common base paragraph indentation

Follow-up Comment #3, bug #64018 (project groff): I see no reason why the standard indentation of running text from the left margin of the paper and the default indentation inside a tagged paragraph need to be related in any way. In fact, in 1990 Kernighan troff, the former was \n(IN and the latt

[bug #64018] [man, mdoc] decide on a common base paragraph indentation

Follow-up Comment #2, bug #64018 (project groff): [comment #1 comment #1:] > The setting ".nr IN 7.2n" is present since the beginning of the groff repository, i.e. groff-1.06, Sep 1 12:28:08 1992, file tmac/tmac.an . [...] > Consequently, it is almost certain that it was James Clark who changed fr

[bug #64018] [man, mdoc] decide on a common base paragraph indentation

Follow-up Comment #1, bug #64018 (project groff): The setting ".nr IN 7.2n" is present since the beginning of the groff repository, i.e. groff-1.06, Sep 1 12:28:08 1992, file tmac/tmac.an . The groff-1.01 released by James Clark on Mar 13 12:49:40 1991 and declared as a "beta-test version" that i

[bug #64018] [man, mdoc] decide on a common base paragraph indentation

URL: Summary: [man,mdoc] decide on a common base paragraph indentation Group: GNU roff Submitter: gbranden Submitted: Sun 09 Apr 2023 08:24:42 PM UTC Category: Macro - others/