zsh-workers
 help / color / mirror / code / Atom feed
From: dana <dana@dana.is>
To: Daniel Shahaf <d.s@daniel.shahaf.name>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: Dangling reference in zshroadmap(1) (was: Re: test for newline in a variable--unexpected results sometimes)
Date: Sun, 16 Sep 2018 18:33:53 -0500	[thread overview]
Message-ID: <895B1E5B-58E1-448A-9B8A-2E758FAF8796@dana.is> (raw)
In-Reply-To: <1537138615.3041549.1510092752.5632AB35@webmail.messagingengine.com>

(This belongs in workers now, yeah?)

On 16 Sep 2018, at 17:56, Daniel Shahaf <d.s@daniel.shahaf.name> wrote:
>I don't understand the last sentence?

I haven't bothered to look at the actual source (and don't know it well from
memory yet), but just from the end result, it seems that it's set up so that if
a chapter has no sub-sections (like 'Command Execution') or if it has some
introductory text before the sub-sections (like 'Functions'), the top-level
heading is preserved. For chapters like 'Jobs & Signals', where the first bit of
content is a sub-heading, that top-level heading goes away, so as not to have
two consecutive headings.

On 16 Sep 2018, at 17:56, Daniel Shahaf <d.s@daniel.shahaf.name> wrote:
>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.

For cases like the 'Shell Grammar' reference you found, it seems like there are
basically two kinds of options: Either change the reference to point to a
specific section instead of a whole chapter, or change the structure of the
pages to include the chapter heading. Assuming that's true, only the latter is
appropriate here, right?

I'm probably speaking out of turn, though, tbh; i know way less about how this
works than you.

dana


       reply	other threads:[~2018-09-16 23:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20180916172716.GA27892@lilyforest.localdomain>
     [not found] ` <20180916204433.6k36inmuekgqp3a2@tarpaulin.shahaf.local2>
     [not found]   ` <DC89977C-A130-483E-A631-E7A2CD6AE7A0@dana.is>
     [not found]     ` <1537134280.3026165.1510059848.0DC32D7A@webmail.messagingengine.com>
     [not found]       ` <73DDD712-8DE5-4EA7-8488-5ED0A4EFB2A6@dana.is>
     [not found]         ` <1537138615.3041549.1510092752.5632AB35@webmail.messagingengine.com>
2018-09-16 23:33           ` dana [this message]
2018-09-17  0:04             ` Daniel Shahaf

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=895B1E5B-58E1-448A-9B8A-2E758FAF8796@dana.is \
    --to=dana@dana.is \
    --cc=d.s@daniel.shahaf.name \
    --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).