zsh-users
 help / color / mirror / code / Atom feed
From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: dana <dana@dana.is>
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 22:56:55 +0000	[thread overview]
Message-ID: <1537138615.3041549.1510092752.5632AB35@webmail.messagingengine.com> (raw)
In-Reply-To: <73DDD712-8DE5-4EA7-8488-5ED0A4EFB2A6@dana.is>

dana wrote on Sun, 16 Sep 2018 17:16 -0500:
> 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.

I don't understand the last sentence?

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

On the other hand, redirect.yo explicitly adds a sect() in man page format
only.  The net effect is that the heading "Redirection" is shown as a
chapter heading in html/pdf but as a section heading in man.

> (In the man pages, the top-level headings are missing,

That's because zman.yo defines chapter() to expand to nothing.

> so that leaves only the sub-headings. But in the HTML version, the
> links take you to the top of the entire section.)
> 

Yes, the texinode() directives are placed on the chapter(), not on the
sect() with the same name.

The mapping between chapter() nodes and man pages is not one to one;
there are more chapters than man pages.

> Not sure how to address that

What end result would we like to achieve?  Once we nail that down we can
think how to implement it.

At least, we could grep for any instances of ifnzman(see the section
`foo'...) where `foo' is a texinode() of a chapter(), and fix them.

Or we could hack at the yodl to reduce the differences between the
various output formats.

There are probably other options 

Daniel

  reply	other threads:[~2018-09-16 22:57 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
2018-09-16 22:56         ` Daniel Shahaf [this message]
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=1537138615.3041549.1510092752.5632AB35@webmail.messagingengine.com \
    --to=d.s@daniel.shahaf.name \
    --cc=dana@dana.is \
    --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).