From: dana <dana@dana.is>
To: Daniel Shahaf <d.s@daniel.shahaf.name>
Cc: zsh-users@zsh.org, lilydjwg <lilydjwg@gmail.com>
Subject: Re: Dangling reference in zshroadmap(1) (was: Re: test for newline in a variable--unexpected results sometimes)
Date: Sun, 16 Sep 2018 17:16:24 -0500 [thread overview]
Message-ID: <73DDD712-8DE5-4EA7-8488-5ED0A4EFB2A6@dana.is> (raw)
In-Reply-To: <1537134280.3026165.1510059848.0DC32D7A@webmail.messagingengine.com>
On 16 Sep 2018, at 16:44, Daniel Shahaf <d.s@daniel.shahaf.name> wrote:
>zshroadmap(1) refers to a "Shell Grammar" section, but there's no such
>section in the man pages:
Oh, i didn't notice because i always use the HTML version:
http://zsh.sourceforge.net/Doc/Release/Shell-Grammar.html
I guess it's designed with the sections that get separate pages (like
'Parameters') in mind? The top-level heading seems to be omitted if the first
immediate descendant is a sub-section. The same is true of other sections like
'Invocation', 'Files', and 'Jobs & Signals'.
Confusingly, the first two sections mentioned above each contain a sub-section
with the same name, so the exact part of the documentation being referred to is
unclear/inconsistent. (In the man pages, the top-level headings are missing, so
that leaves only the sub-headings. But in the HTML version, the links take you
to the top of the entire section.)
Not sure how to address that
dana
next prev parent reply other threads:[~2018-09-16 22:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-16 17:27 test for newline in a variable--unexpected results sometimes lilydjwg
2018-09-16 20:44 ` Daniel Shahaf
2018-09-16 20:53 ` dana
2018-09-16 21:44 ` Dangling reference in zshroadmap(1) (was: Re: test for newline in a variable--unexpected results sometimes) Daniel Shahaf
2018-09-16 22:16 ` dana [this message]
2018-09-16 22:56 ` Daniel Shahaf
2018-09-17 3:20 ` test for newline in a variable--unexpected results sometimes lilydjwg
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=73DDD712-8DE5-4EA7-8488-5ED0A4EFB2A6@dana.is \
--to=dana@dana.is \
--cc=d.s@daniel.shahaf.name \
--cc=lilydjwg@gmail.com \
--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).