From: Alex Kost <alezost@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Formatting lists in descriptions (was: [PATCH] gnu: Document xorg packages.)
Date: Tue, 14 Jul 2015 11:32:45 +0300 [thread overview]
Message-ID: <87wpy3xhoy.fsf_-_@gmail.com> (raw)
In-Reply-To: <877fq4yol1.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Mon, 13 Jul 2015 19:06:18 +0200")
Ludovic Courtès (2015-07-13 20:06 +0300) wrote:
> Alex Kost <alezost@gmail.com> skribis:
[...]
>> And one more thing: there are "windowswmproto" and "libwindowswm"
>> packages that have something to do with MS Windows and Cygwin. Do we
>> need them?
>
> If that’s really what they are, let’s remove them.
OK, I'll sent a patch for that and it may be discussed there, if there
will be objections.
>> From 9b0d9bec0e1b1a3ce949f7d93a6598b75b050c86 Mon Sep 17 00:00:00 2001
>> From: Alex Kost <alezost@gmail.com>
>> Date: Sun, 12 Jul 2015 19:47:39 +0300
>> Subject: [PATCH] gnu: Document xorg packages.
>>
>> * gnu/packages/xorg.scm: Add/imrove 'synopsis'/'description' fields of
>> many packages.
>
> OK!
>
>> + (description
>> + "XExtProto provides the following extensions:
>> +
>> +DOUBLE-BUFFER
>> +DPMS
>> +Extended-Visual-Information
>> +Generic Event Extension
>> +LBX
>> +MIT-SHM
>> +MIT-SUNDRY-NONSTANDARD
>> +Multi-Buffering
>> +SECURITY
>> +SHAPE
>> +SYNC
>> +TOG-CUP
>> +XC-APPGROUP
>> +XTEST")
>
> Formatting will be lost in UIs, so this should be a comma-separated list
> instead.
Currently the formatting is not lost in Emacs UI, but I agree on this one.
>> + (description
>> + "XKBUtils is a collection of small utilities for X Keyboard (XKB)
>> +extension to the X11 protocol. It includes:
>> +
>> + - xkbbell - generate XKB bell events;
>> + - xkbvleds - display the state of LEDs on an XKB keyboard in a window;
>> + - xkbwatch - reports changes in the XKB keyboard state.")
>
> Likewise.
What about separating such entries with newspaces as it is done in some
other packages (e.g., 'signing-party') to prevent the format breaking?:
+ (description
+ "XKBUtils is a collection of small utilities for X Keyboard (XKB)
+extension to the X11 protocol. It includes:
+
+ - xkbbell: generate XKB bell events;
+
+ - xkbvleds: display the state of LEDs on an XKB keyboard in a window;
+
+ - xkbwatch: reports changes in the XKB keyboard state.")
If this is acceptable, I can send a patch to fix the list formatting for
other packages (guile-json, libotr, …)
And as I have an unhealthy desire to organize the same things in the
same manner, what variant to choose for formatting lists? Should the
list items begin with "-" or "+" or "*" or "•" and should there be spaces
before the chosen symbol or maybe there should be just a couple of
spaces without any marker?
I think the following variant is more or less the standard way:
--8<---------------cut here---------------start------------->8---
Our 'foobarbaz' consists of:
- foo: does some fooing;
- bar: bars everything;
- baz: useless component.
--8<---------------cut here---------------end--------------->8---
However I like how the description of 'libdaemon' looks (I would rather
added periods in the end of all sentences), but someone probably
wouldn't like using "•" or other unusual symbols.
--
Alex
next prev parent reply other threads:[~2015-07-14 8:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-12 17:41 [PATCH] gnu: Document xorg packages Alex Kost
2015-07-13 17:06 ` Ludovic Courtès
2015-07-14 8:32 ` Alex Kost [this message]
2015-07-14 13:23 ` Formatting lists in descriptions Ludovic Courtès
2015-07-14 18:58 ` Cook, Malcolm
2015-07-15 14:28 ` Ludovic Courtès
2015-07-15 15:01 ` Alex Kost
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=87wpy3xhoy.fsf_-_@gmail.com \
--to=alezost@gmail.com \
--cc=guix-devel@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).