From: "Daniel Shahaf" <d.s@daniel.shahaf.name>
To: zsh-workers@zsh.org
Subject: Re: install.info failure
Date: Tue, 25 May 2021 16:47:29 +0000 [thread overview]
Message-ID: <6928a890-4805-49a5-89ae-7c2645bbb7d6@www.fastmail.com> (raw)
In-Reply-To: <790340D6-F96D-4A63-A6AD-5B4BF24BAEC0@kba.biglobe.ne.jp>
Jun T wrote on Tue, 25 May 2021 08:25 +00:00:
> I tried adding a prefix SS- to the subsection anchor name:
>
> def(subsect)(1)(\
> NL()\
> anchor(SS-ARG1)NL()\
> NOTRANS(@subsection )ARG1+NL()\
> NOTRANS(@noindent)\
> )
>
> but still got may (16?) duplicated names like:
>
> ./zsh.texi:10007: @anchor `SS-Completion' previously defined
> ./zsh.texi:586: here is the previous definition as @anchor
>
> subsect(Completion) is in 4 files:
> options.yo
> roadmap.yo
> zftpsys.yo
> zle.yo
>
> I can't find a way to automatically assign unique (but easy to refer)
> anchor name.
Change the definition of sect() to store the section title in a (yodl or
TeX) macro, and then use that when calling anchor() in subsect()? Or
change subsect() to take two arguments, an anchor id and a title, and
update all uses of it (there are no compatibility concerns)?
Actually, something like this might already exist, since the PDF
manual's page headers _already_ include the chapter's number and name.
next prev parent reply other threads:[~2021-05-25 16:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-22 13:11 Vin Shelton
2021-05-22 13:23 ` Daniel Shahaf
2021-05-24 20:22 ` Daniel Shahaf
2021-05-25 4:00 ` Jun T
2021-05-25 6:48 ` Bart Schaefer
2021-05-25 8:25 ` Jun T
2021-05-25 16:00 ` Bart Schaefer
2021-05-25 16:47 ` Daniel Shahaf [this message]
2021-05-25 20:58 ` Marlon Richert
2021-05-25 21:54 ` Bart Schaefer
2021-05-25 22:16 ` dana
2021-05-27 18:26 ` Marlon Richert
2021-05-31 22:33 ` Bart Schaefer
2021-06-01 10:44 ` Marlon Richert
2021-06-02 6:33 ` Bart Schaefer
2021-06-04 21:49 ` dana
2021-06-05 16:09 ` Bart Schaefer
2021-06-13 18:23 ` [PATCH] " Bart Schaefer
2021-06-05 10:47 Thomas Paulsen
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=6928a890-4805-49a5-89ae-7c2645bbb7d6@www.fastmail.com \
--to=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).