git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: paul@pauldsmith.org.uk
Cc: git@vger.kernel.org
Subject: Re: Support 'help' for custom/alias commands
Date: Sun, 9 Feb 2020 16:38:57 +0000	[thread overview]
Message-ID: <20200209163857.GA7054@camp.crustytoothpaste.net> (raw)
In-Reply-To: <00df01d5df4a$e422af70$ac680e50$@pauldsmith.org.uk>

[-- Attachment #1: Type: text/plain, Size: 1258 bytes --]

On 2020-02-09 at 13:14:42, paul@pauldsmith.org.uk wrote:
> Brian,
> 
> Thanks for considering this.  I've not tried MANPATH but will take a look - my employers use both Linux and Windows so this would only address half the issue but I also understand your comments on "one config to rule them all" and the HTML/MAN issue.
> 
> I've used ASCIIDOCTOR already to create config but I feel it would be nice if that could be rolled up into some sort of bundle but it users don't want Ruby then yes, it's not going to work for them.  My personal take is that anyone wanting docs for their custom applications should create them like core Git does - and with Docker and similar it's easy to isolate an environment so perhaps a Docker image might be the way to go.

I don't see a problem with us shipping the stylesheets and tooling we
use for our conversions as something people can use, and then if they
want to install AsciiDoc or Asciidoctor, they can use the same scripts.
That wouldn't be that hard to do.

Personally, though, I find that I don't benefit from them much when I
write documentation, and so I don't use them.  Other people may feel
differently, though.
-- 
brian m. carlson: Houston, Texas, US
OpenPGP: https://keybase.io/bk2204

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 868 bytes --]

      reply	other threads:[~2020-02-09 16:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <VI1P192MB025548BB0508125DF9B5852DC81C0@VI1P192MB0255.EURP192.PROD.OUTLOOK.COM>
2020-02-07 10:42 ` Support 'help' for custom/alias commands paul
2020-02-07 11:29   ` Konstantin Khomoutov
2020-02-09 13:16     ` paul
2020-02-07 23:46   ` brian m. carlson
2020-02-09 13:14     ` paul
2020-02-09 16:38       ` brian m. carlson [this message]

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200209163857.GA7054@camp.crustytoothpaste.net \
    --to=sandals@crustytoothpaste.net \
    --cc=git@vger.kernel.org \
    --cc=paul@pauldsmith.org.uk \
    /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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).