unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Bruno Victal <mirai@makinata.eu>
To: 60582@debbugs.gnu.org
Cc: Bruno Victal <mirai@makinata.eu>
Subject: [bug#60582] [PATCH] Properly format list of packages & sync lightdm documentation.
Date: Thu,  5 Jan 2023 21:01:42 +0000	[thread overview]
Message-ID: <cover.1672951913.git.mirai@makinata.eu> (raw)

The first patch allows generate-documentation to properly format a list of packages.
Previously these had to be cleaned up by hand which was error-prone.

Sample snippets:

Before:

--8<---------------cut here---------------start------------->8---
@item @code{assets} (default: @code{(#<package adwaita-icon-theme@@42.0 gnu/packages/gnome.scm:2870 7f018c9fd630> #<package gnome-themes-extra@@3.28 gnu/packages/gnome.scm:12233 7f018ca2f0b0> #<package hicolor-icon-theme@@0.17 gnu/packages/gnome.scm:3042 7f018c9fd2c0>)}) (type: list-of-file-likes)
--8<---------------cut here---------------end--------------->8---

After:

--8<---------------cut here---------------start------------->8---
@item @code{assets} (default: @code{(adwaita-icon-theme gnome-themes-extra hicolor-icon-theme)}) (type: list-of-file-likes)
--8<---------------cut here---------------end--------------->8---


The second patch syncs the documentation with the source code and fixes some mistakes.



Bruno Victal (2):
  services: configuration: Format a list of packages by their names.
  services: lightdm: Sync documentation with source.

 doc/guix.texi                  | 4 ++--
 gnu/services/configuration.scm | 3 +++
 gnu/services/lightdm.scm       | 2 +-
 3 files changed, 6 insertions(+), 3 deletions(-)


base-commit: 80902fc210d8dc28e14d63d68f398aef796b5838
-- 
2.38.1





             reply	other threads:[~2023-01-05 21:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-05 21:01 Bruno Victal [this message]
2023-01-05 21:06 ` [bug#60582] [PATCH 1/2] services: configuration: Format a list of packages by their names Bruno Victal
2023-01-13 20:29   ` [bug#60582] [PATCH] Properly format list of packages & sync lightdm documentation Maxim Cournoyer
2023-01-13 20:34     ` Bruno Victal
2023-01-05 21:06 ` [bug#60582] [PATCH 2/2] services: lightdm: Sync documentation with source Bruno Victal
2023-01-06 14:10 ` [bug#60582] [PATCH v2 1/2] services: configuration: Format a list of packages by their names Bruno Victal
2023-01-06 14:10   ` [bug#60582] [PATCH v2 2/2] services: lightdm: Sync documentation with source Bruno Victal
2023-01-13 21:34 ` [bug#60582] [PATCH v3 1/2] services: configuration: Format a list of packages by their names Bruno Victal
2023-01-13 21:34   ` [bug#60582] [PATCH v3 2/2] services: lightdm: Sync documentation with source Bruno Victal
2023-02-09  3:39     ` [bug#60582] [PATCH] Properly format list of packages & sync lightdm documentation Maxim Cournoyer
2023-02-09 16:17       ` Bruno Victal
2023-02-09 16:42         ` Maxim Cournoyer
2023-02-09  4:00     ` bug#60582: " Maxim Cournoyer

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=cover.1672951913.git.mirai@makinata.eu \
    --to=mirai@makinata.eu \
    --cc=60582@debbugs.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).