From: Felipe Contreras <felipe.contreras@gmail.com>
To: Jeff King <peff@peff.net>, Felipe Contreras <felipe.contreras@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] doc: manpage: remove maximum title length
Date: Wed, 03 May 2023 11:09:46 -0600 [thread overview]
Message-ID: <6452955ade0c9_1df7294b9@chronos.notmuch> (raw)
In-Reply-To: <20230503164354.GC1789686@coredump.intra.peff.net>
Jeff King wrote:
> On Tue, May 02, 2023 at 11:29:26PM -0600, Felipe Contreras wrote:
>
> > DocBook Stylesheets limit the size of the manpage titles for some
> > reason.
> >
> > Even some of the longest git commands have no trouble fitting in 80
> > character terminals, so it's not clear why we would want to limit titles
> > to 20 characters, especially when modern terminals are much bigger.
>
> Makes sense.
>
> Since the manpage header shows the name twice, along with "Git Manual",
> the practical limit for an 80-column terminal is somewhere around 35
> characters. If it's not hard to do, it might be worth setting the value
> there,
It's not hard to do, but that would create a discrepancy with asciidoctor
manpage backend, which doesn't do that.
> I could also see an argument that the truncation is worse than any
> wrapping or other ugliness that the user might see on a smaller
> terminal, which implies that "no limit" as you have here is the best
> option.
I think it's best to remove the limit so there are no surprises and the output
is consistent among tools.
> > For example:
> >
> > --- a/git-credential-cache--daemon.1
> > +++ b/git-credential-cache--daemon.1
> > @@ -1,4 +1,4 @@
> > -GIT-CREDENTIAL-CAC(1) Git Manual GIT-CREDENTIAL-CAC(1)
> > +GIT-CREDENTIAL-CACHE--DAEMON(1) Git Manual GIT-CREDENTIAL-CACHE--DAEMON(1)
> >
> > NAME
> > git-credential-cache--daemon - Temporarily store user credentials in
> > @@ -24,4 +24,4 @@ DESCRIPTION
> > GIT
> > Part of the git(1) suite
> >
> > -Git omitted 2023-05-02 GIT-CREDENTIAL-CAC(1)
> > +Git omitted 2023-05-02 GIT-CREDENTIAL-CACHE--DAEMON(1)
>
> Your patch can't be applied by "git am" because of this diff in the
> commit message (it thinks the commit message stops at the first diff,
> even if it is before a "---" marker). The usual practice is to indent
> the included diff.
All right, I'll send an update.
--
Felipe Contreras
next prev parent reply other threads:[~2023-05-03 17:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-03 5:29 [PATCH] doc: manpage: remove maximum title length Felipe Contreras
2023-05-03 16:43 ` Jeff King
2023-05-03 17:09 ` Felipe Contreras [this message]
2023-05-03 17:16 ` [PATCH v2] " Felipe Contreras
2023-05-03 17:58 ` Junio C Hamano
2023-05-03 17:43 ` [PATCH] " Junio C Hamano
2023-05-03 17:49 ` Junio C Hamano
2023-05-08 0:19 ` Felipe Contreras
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6452955ade0c9_1df7294b9@chronos.notmuch \
--to=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).