zsh-users
 help / color / mirror / code / Atom feed
From: "Nikolay Aleksandrovich Pavlov (ZyX)" <kp-pav@yandex.ru>
To: Sebastian Gniazdowski <psprint@zdharma.org>,
	Zsh Users <zsh-users@zsh.org>
Subject: Re: Doxygen for shell scripts
Date: Sun, 10 Sep 2017 12:43:54 +0300	[thread overview]
Message-ID: <2669581505036634@web1j.yandex.ru> (raw)
In-Reply-To: <etPan.59b4e3ca.42b18817.134@zdharma.org>

10.09.2017, 10:16, "Sebastian Gniazdowski" <psprint@zdharma.org>:
> Hello
> I've written a documentation generator for shell scripts. Example outputs:
>
> https://github.com/zdharma/zshelldoc/tree/master/examples
>
> It is based on (z) flag, works very robust. Supported are things like autoload functions and calls between scripts. I think the most power comes from call trees and comment extraction – this allows to analyze the code – but I plan to add some more things, like detection of usage of Zle, eval, add-zsh-hook, etc.
>
> --
> Sebastian Gniazdowski
> psprint /at/ zdharma.org

Why not a sphinx plugin? It is most logical: you need to teach it how to extract documentation comments and whatever those “more things” you want and it takes the job of yielding nicely formatted documentation in many different formats (one of which includes man pages), provides ability to host the generated documentation on readthedocs (but you still can have static pages on github.io or anwhere else if you want), TOC (table of contents) generating, cross-referencing, code highlighting (via pygments), searching (by default: local javascript-based search, not as good as google or properly configured another sphinx, but usable).


  reply	other threads:[~2017-09-10  9:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-10  7:03 Sebastian Gniazdowski
2017-09-10  9:43 ` Nikolay Aleksandrovich Pavlov (ZyX) [this message]
2017-09-11 12:15   ` Sebastian Gniazdowski
2017-09-11 20:37     ` Nikolay Aleksandrovich Pavlov (ZyX)

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=2669581505036634@web1j.yandex.ru \
    --to=kp-pav@yandex.ru \
    --cc=psprint@zdharma.org \
    --cc=zsh-users@zsh.org \
    /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://git.vuxu.org/mirror/zsh/

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).