From: Bevan Stanely <bevanstanely@iisc.ac.in>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: "zsh-workers@zsh.org" <zsh-workers@zsh.org>
Subject: Re: Proposal: Use Markdown syntax for README and other documentation
Date: Fri, 20 May 2022 05:43:48 +0000 [thread overview]
Message-ID: <MA1PR01MB2876908BC02B3B071E075A16E9D39@MA1PR01MB2876.INDPRD01.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <CAH+w=7atsvJv6aytmwKoUWsorFdmmFf=wQfWnGK8kmwfdjwUBA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 764 bytes --]
That's interesting. Thanks.
Bevan Stanely
bevs.xyz<https://bevs.xyz/>
________________________________
From: Bart Schaefer <schaefer@brasslantern.com>
Sent: Friday, May 20, 2022 12:12:01 AM
To: Bevan Stanely <bevanstanely@iisc.ac.in>
Cc: Peter Stephenson <p.w.stephenson@ntlworld.com>; zsh-workers@zsh.org <zsh-workers@zsh.org>
Subject: Re: Proposal: Use Markdown syntax for README and other documentation
External Email
On Thu, May 19, 2022 at 11:24 AM Bevan Stanely <bevanstanely@iisc.ac.in<mailto:bevanstanely@iisc.ac.in>> wrote:
Also one followup question, is yodl generating the documentation website as well? The .org and sourceforge ones.
Yodl generates the manual page HTML and the FAQ but the "front page" of each site is hand-coded.
[-- Attachment #2: Type: text/html, Size: 2068 bytes --]
next prev parent reply other threads:[~2022-05-20 5:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-18 15:41 Bevan Stanely
2022-05-19 1:10 ` Lawrence Velázquez
2022-05-19 4:02 ` dana
2022-05-19 4:26 ` Lawrence Velázquez
2022-05-19 6:04 ` Bevan Stanely
2022-05-19 8:55 ` Peter Stephenson
2022-05-19 15:10 ` Bevan Stanely
2022-05-19 15:16 ` Peter Stephenson
2022-05-19 15:22 ` Bevan Stanely
2022-05-19 18:23 ` Bevan Stanely
2022-05-19 18:42 ` Bart Schaefer
2022-05-20 5:43 ` Bevan Stanely [this message]
2022-05-19 4:29 ` Bart Schaefer
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=MA1PR01MB2876908BC02B3B071E075A16E9D39@MA1PR01MB2876.INDPRD01.PROD.OUTLOOK.COM \
--to=bevanstanely@iisc.ac.in \
--cc=schaefer@brasslantern.com \
--cc=zsh-workers@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).