unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Hartmut Goebel <h.goebel@crazy-compilers.com>
Cc: 56145@debbugs.gnu.org
Subject: [bug#56145] [PATCH 0/5] Add menus to Services sub-sections
Date: Mon, 04 Jul 2022 22:08:47 +0200	[thread overview]
Message-ID: <87a69o8wts.fsf@gnu.org> (raw)
In-Reply-To: <92089bc8-c60e-aa33-b285-807d4fc7992f@crazy-compilers.com> (Hartmut Goebel's message of "Mon, 4 Jul 2022 16:30:14 +0200")

Hi,

Hartmut Goebel <h.goebel@crazy-compilers.com> skribis:

> Am 03.07.22 um 12:38 schrieb Ludovic Courtès:
>
>> I’m less convinced about this one.  I wonder if, instead of adding
>> anchors, we should add proper sectioning at the same level as the
>> existing sections (“Base Services”, etc.).
> I don't actually understand what you mean. Currently each section
> described one or more services. The section groups the services into
> „all LDAP related‘, „all X11 related“, etc. This patch basically adds
> the anchors, whereas the other patch uses the anchors that already
> exist. So basically they result in the same.
>
> Do you suggest to split „Base Services” into several sections? (Like
> „Console service“, “Randow data services‘, etc.)
>
>> Also, I don’t think we need one section (or anchor) per service:
>
> Having a TOC of all services is my actual intention. I want to have a
> list which

(Incomplete sentence.)

To be clear: I think we must not abuse sectioning to make an index;
there’s already an index, and we can add concept index entries if that’s
what’s missing.

However, what we could/should do is improve structure.  We can do that
by grouping related services together, essentially splitting existing
sections into finer-grain sections—e.g., ‘Base Services’ might be split
into two or three sections.  That’s not the same as adding one heading
and one anchor for each service.

Does that make sense?

Thanks,
Ludo’.




  reply	other threads:[~2022-07-04 20:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-22 14:45 [bug#56145] [PATCH 0/5] Add menus to Services sub-sections Hartmut Goebel
2022-06-22 15:55 ` [bug#56145] [PATCH 1/5] doc: Add menus to Services sub-sections (part 1/2) Hartmut Goebel
2022-07-03 10:33   ` [bug#56145] [PATCH 0/5] Add menus to Services sub-sections Ludovic Courtès
2022-06-22 15:55 ` [bug#56145] [PATCH 2/5] doc: Add menus to Services sub-sections (part 2/2) Hartmut Goebel
2022-07-03 10:38   ` [bug#56145] [PATCH 0/5] Add menus to Services sub-sections Ludovic Courtès
2022-07-04 14:30     ` Hartmut Goebel
2022-07-04 20:08       ` Ludovic Courtès [this message]
2022-06-22 15:55 ` [bug#56145] [PATCH 3/5] doc: Fix a URL Hartmut Goebel
2022-06-22 15:55 ` [bug#56145] [PATCH 4/5] doc: Small rewording Hartmut Goebel
2022-06-22 15:55 ` [bug#56145] [PATCH 5/5] doc: Add a URL link Hartmut Goebel
2022-06-22 18:59 ` [bug#56145] [PATCH 0/5] Add menus to Services sub-sections Maxime Devos

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=87a69o8wts.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=56145@debbugs.gnu.org \
    --cc=h.goebel@crazy-compilers.com \
    /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).