From: zimoun <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 43482@debbugs.gnu.org
Subject: [bug#43482] [PATCH 1/3] doc: Update the master menu.
Date: Thu, 24 Sep 2020 17:28:57 +0200 [thread overview]
Message-ID: <CAJ3okZ37twEXmpC5a3prY78J+3bboTy3iBvZgGHe7Y6wob-2GQ@mail.gmail.com> (raw)
In-Reply-To: <87k0wj8bz6.fsf@gnu.org>
On Thu, 24 Sep 2020 at 16:51, Ludovic Courtès <ludo@gnu.org> wrote:
> How come it got this much out of sync? How did you update it? IME the
> Emacs thingie gets confused when some but not all the top-level nodes
> are in separate files.
I do not remember exactly how. Well, I have used the 'menu-bar' since
I never remember the TexInfo keys.
Then, I tried 'texinfo-master-menu' and 'texinfo-every-node-update'
and 'texinfo-all-menus-update' and manually checked with Magit the
diff.
For example, this commit b460ba7992 adds one node but does not update
the master menu; the TeXInfo workflow is a bit tedious and the mistake
always happens somehow.
Cheers,
simon
next prev parent reply other threads:[~2020-09-24 16:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-18 1:37 [bug#43482] [PATCH 0/3] doc: Reorder "Channels" section zimoun
2020-09-18 1:45 ` [bug#43482] [PATCH 1/3] doc: Update the master menu zimoun
2020-09-18 1:45 ` [bug#43482] [PATCH 2/3] doc: Add the "Channels" section menu zimoun
2020-09-24 14:52 ` Ludovic Courtès
2020-09-24 15:05 ` zimoun
2020-09-25 9:20 ` Ludovic Courtès
2020-09-18 1:45 ` [bug#43482] [PATCH 3/3] doc: Reorder the "Channels" section zimoun
2020-09-24 14:59 ` Ludovic Courtès
2020-09-24 15:13 ` zimoun
2020-09-24 14:51 ` [bug#43482] [PATCH 1/3] doc: Update the master menu Ludovic Courtès
2020-09-24 15:28 ` zimoun [this message]
2020-09-25 20:00 ` [bug#43482] [PATCH v2 1/2] " zimoun
2020-09-25 20:00 ` [bug#43482] [PATCH v2 2/2] doc: Promote "Channels" as chapter and reorder zimoun
2020-09-27 20:38 ` bug#43482: [PATCH v2 1/2] doc: Update the master menu Ludovic Courtès
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJ3okZ37twEXmpC5a3prY78J+3bboTy3iBvZgGHe7Y6wob-2GQ@mail.gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=43482@debbugs.gnu.org \
--cc=ludo@gnu.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.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).