* [bug#38108] [PATCH] doc: Fix typos.
2019-11-07 18:50 [bug#38108] [PATCH] doc: Fix typos zimoun
@ 2019-11-08 14:10 ` Giovanni Biscuolo
2019-11-09 11:40 ` zimoun
2019-11-08 22:41 ` Ludovic Courtès
` (3 subsequent siblings)
4 siblings, 1 reply; 23+ messages in thread
From: Giovanni Biscuolo @ 2019-11-08 14:10 UTC (permalink / raw)
To: zimoun, 38108
[-- Attachment #1: Type: text/plain, Size: 455 bytes --]
Hi zimoun
zimoun <zimon.toutoune@gmail.com> writes:
[...]
> @@ -4457,7 +4457,7 @@ The main options are:
>
> @table @code
> @item --export
> -Export the specified store files or packages (see below.) Write the
> +Export the specified store files or packages (see below) Write the
^ missing point?
[...]
Thanks! Gio'
--
Giovanni Biscuolo
Xelera IT Infrastructures
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
^ permalink raw reply [flat|nested] 23+ messages in thread* [bug#38108] [PATCH] doc: Fix typos.
2019-11-07 18:50 [bug#38108] [PATCH] doc: Fix typos zimoun
2019-11-08 14:10 ` Giovanni Biscuolo
@ 2019-11-08 22:41 ` Ludovic Courtès
2019-11-09 12:14 ` zimoun
2019-11-11 20:11 ` [bug#38108] [PATCH] doc: Fix typos zimoun
` (2 subsequent siblings)
4 siblings, 1 reply; 23+ messages in thread
From: Ludovic Courtès @ 2019-11-08 22:41 UTC (permalink / raw)
To: zimoun; +Cc: Julien Lepiller, 38108
Hello!
zimoun <zimon.toutoune@gmail.com> skribis:
> * doc/guix.texi: Fix typos.
> ---
> doc/guix.texi | 78 +++++++++++++++++++++++++--------------------------
> 1 file changed, 39 insertions(+), 39 deletions(-)
>
> diff --git a/doc/guix.texi b/doc/guix.texi
> index 3a9d206b9f..5a5c54702e 100644
> --- a/doc/guix.texi
> +++ b/doc/guix.texi
> @@ -585,7 +585,7 @@ you may have to run @code{su -} or @code{sudo -i}. As @code{root}, run:
>
> This creates @file{/gnu/store} (@pxref{The Store}) and @file{/var/guix}.
> The latter contains a ready-to-use profile for @code{root} (see next
> -step.)
> +step).
So, is it this simple? :-)
I checked what people say and found this:
https://blog.apastyle.org/apastyle/2013/03/punctuation-junction-periods-and-parentheses.html
https://english.stackexchange.com/questions/6632/where-does-the-period-go-when-using-parentheses/6633
(I wanted to check the Chicago Manual of Style but it’s now behind a
paywall.)
It would seem that “see next step” (for example) does not count as a
parenthetical sentence (it’s not a sentence because it doesn’t start
with a capital letter), and thus the period should go outside the
parens.
In short, it looks like most or all of the changes you made are
“correct”, but you might want to double-check, also to account for the
typo Giovanni noticed.
I think this will invalidate translations of the affected paragraphs.
Is that a big deal, Julien, or is it easily resolved?
Typographically yours,
Ludo’.
^ permalink raw reply [flat|nested] 23+ messages in thread* [bug#38108] [PATCH] doc: Fix typos.
2019-11-08 22:41 ` Ludovic Courtès
@ 2019-11-09 12:14 ` zimoun
2019-11-09 21:53 ` Ludovic Courtès
0 siblings, 1 reply; 23+ messages in thread
From: zimoun @ 2019-11-09 12:14 UTC (permalink / raw)
To: Ludovic Courtès; +Cc: Julien Lepiller, 38108
Hi Ludo,
On Fri, 8 Nov 2019 at 23:41, Ludovic Courtès <ludo@gnu.org> wrote:
> So, is it this simple? :-)
The real hard part is about quoting mark: ." or ". ;-)
The Guardian has some explanations.
https://www.theguardian.com/guardian-observer-style-guide-q
https://www.theguardian.com/media/mind-your-language/2011/may/19/mind-your-language-punctuation-quotations
> (I wanted to check the Chicago Manual of Style but it’s now behind a
> paywall.)
I have gone with the free trial ;-)
6: Punctuation
6.13: Periods in relation to parentheses and brackets
--8<---------------cut here---------------start------------->8---
When an entire independent sentence is enclosed in parentheses or square
brackets, the period belongs inside the closing parenthesis or bracket. When
matter in parentheses or brackets, even a grammatically complete sentence, is
included within another sentence, the period belongs outside (but see also
6.98). Avoid enclosing more than one complete sentence within another
sentence. In the third example, two periods are required—one for the
abbreviation etc. and one for the sentence as a whole, outside the parentheses
(see also 6.14, 6.123). For periods relative to quotation marks, see 6.9.
Fiorelli insisted on rewriting the paragraph. (His newfound ability to type
was both a blessing and a curse.)
Felipe had left an angry message for Isadora on the mantel (she noticed it
while glancing in the mirror).
His chilly demeanor gave him an affinity for the noble gases (helium, neon,
etc.).
There were many groundbreaking moments in All in the Family. (The one
featuring “the kiss,” with Sammy Davis Jr., springs to mind.)
“All the evidence pointed to the second location [the Lászlós’ studio].”
--8<---------------cut here---------------end--------------->8---
> In short, it looks like most or all of the changes you made are
> “correct”, but you might want to double-check, also to account for the
> typo Giovanni noticed.
When searching inspiration for another commit message, I reached this
commit ba7ea5ce33 changing some '.)' to ').'.
As you know, I am not native English speaker (french Sud-Ouest power!
;-)) so then I checked on the random Internet and asked on #guix
channel what it is rule. I initially thought an US vs UK specificity.
But not.
Quoting IRC log [1]:
<smithras>zimoun: hmm I'm from the US and I've always put the dot
after the closing paren
<alextee[m]>parenthesis end goes before period in both US and UK
english i think zimoun
<xd1le>zimoun: yes. basically the sentence should be valid if you
remove the parens and everything inside them.
<xd1le>if the sentence in parentheses is on its own, the period i
think should be inside the parentheses
<xd1le>if it's a sentence*
<xd1le>but that example is not on its own
[1] http://logs.guix.gnu.org/guix/2019-11-07.log
Currently the manual contains the both style -- .) and )..
Well, I will triple check because it is tricky and update the patch.
> I think this will invalidate translations of the affected paragraphs.
> Is that a big deal, Julien, or is it easily resolved?
From a quick check, it is already resolved using the correct french
style (from my knowledge). But I have not checked everything in the
manual nor in the "Lexique des règles typographiques en usage à
l'Imprimerie nationale". No idea about the other translations.
Thank you.
simon
ps:
I feel like cutting the hair in small pieces ;-)
But I always interesting the typo. :-)
^ permalink raw reply [flat|nested] 23+ messages in thread* [bug#38108] [PATCH] doc: Fix typos.
2019-11-09 12:14 ` zimoun
@ 2019-11-09 21:53 ` Ludovic Courtès
2019-11-11 20:52 ` zimoun
0 siblings, 1 reply; 23+ messages in thread
From: Ludovic Courtès @ 2019-11-09 21:53 UTC (permalink / raw)
To: zimoun; +Cc: Julien Lepiller, 38108
Hello!
zimoun <zimon.toutoune@gmail.com> skribis:
> On Fri, 8 Nov 2019 at 23:41, Ludovic Courtès <ludo@gnu.org> wrote:
>
>> So, is it this simple? :-)
>
> The real hard part is about quoting mark: ." or ". ;-)
> The Guardian has some explanations.
> https://www.theguardian.com/guardian-observer-style-guide-q
> https://www.theguardian.com/media/mind-your-language/2011/may/19/mind-your-language-punctuation-quotations
Oh. :-)
>> (I wanted to check the Chicago Manual of Style but it’s now behind a
>> paywall.)
>
> I have gone with the free trial ;-)
>
>
> 6: Punctuation
> 6.13: Periods in relation to parentheses and brackets
You’ve convinced me that most or all of the things you fixed needed fixing!
>> In short, it looks like most or all of the changes you made are
>> “correct”, but you might want to double-check, also to account for the
>> typo Giovanni noticed.
>
> When searching inspiration for another commit message, I reached this
> commit ba7ea5ce33 changing some '.)' to ').'.
Fun.
> Well, I will triple check because it is tricky and update the patch.
Sure; do send an update when you think it’s ready!
>> I think this will invalidate translations of the affected paragraphs.
>> Is that a big deal, Julien, or is it easily resolved?
>
>>From a quick check, it is already resolved using the correct french
> style (from my knowledge). But I have not checked everything in the
> manual nor in the "Lexique des règles typographiques en usage à
> l'Imprimerie nationale". No idea about the other translations.
Sorry, what I mean is not that the French translation needed to be
adjusted, but rather that changing the English source will make the
translated versions “outdated” from the point of view of xgettext, which
is annoying.
Thanks,
Ludo’.
^ permalink raw reply [flat|nested] 23+ messages in thread
* [bug#38108] [PATCH] doc: Fix typos.
2019-11-09 21:53 ` Ludovic Courtès
@ 2019-11-11 20:52 ` zimoun
2019-12-02 12:57 ` zimoun
0 siblings, 1 reply; 23+ messages in thread
From: zimoun @ 2019-11-11 20:52 UTC (permalink / raw)
To: Ludovic Courtès; +Cc: Julien Lepiller, 38108
Hi Ludo,
On Sat, 9 Nov 2019 at 22:53, Ludovic Courtès <ludo@gnu.org> wrote:
> > Well, I will triple check because it is tricky and update the patch.
>
> Sure; do send an update when you think it’s ready!
I sent an updated patch.
However, I have missed the option --reroll-count with Magit so it does
not appear with the correct subject [PATCH v2]. Hope that is fine.
> >> I think this will invalidate translations of the affected paragraphs.
> >> Is that a big deal, Julien, or is it easily resolved?
> >
> >>From a quick check, it is already resolved using the correct french
> > style (from my knowledge). But I have not checked everything in the
> > manual nor in the "Lexique des règles typographiques en usage à
> > l'Imprimerie nationale". No idea about the other translations.
>
> Sorry, what I mean is not that the French translation needed to be
> adjusted, but rather that changing the English source will make the
> translated versions “outdated” from the point of view of xgettext, which
> is annoying.
Sorry. My bad! Too slow to understand. :-)
@Julien: Please tell me if it is annoying and I will participate, to
reduce the annoyance. At least for the French translation.
All the best,
simon
^ permalink raw reply [flat|nested] 23+ messages in thread
* [bug#38108] [PATCH] doc: Fix typos.
2019-11-11 20:52 ` zimoun
@ 2019-12-02 12:57 ` zimoun
2019-12-13 10:19 ` Julien Lepiller
0 siblings, 1 reply; 23+ messages in thread
From: zimoun @ 2019-12-02 12:57 UTC (permalink / raw)
To: Ludovic Courtès; +Cc: Julien Lepiller, 38108
Hi,
Friendly ping. :-)
Because the doc is moving forward and so some extra work will be
required to push this boring patch.
On Mon, 11 Nov 2019 at 21:52, zimoun <zimon.toutoune@gmail.com> wrote:
> @Julien: Please tell me if it is annoying and I will participate, to
> reduce the annoyance. At least for the French translation.
For full context:
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=38108
Cheers,
simon
^ permalink raw reply [flat|nested] 23+ messages in thread
* [bug#38108] [PATCH] doc: Fix typos.
2019-12-02 12:57 ` zimoun
@ 2019-12-13 10:19 ` Julien Lepiller
2019-12-13 11:27 ` zimoun
0 siblings, 1 reply; 23+ messages in thread
From: Julien Lepiller @ 2019-12-13 10:19 UTC (permalink / raw)
To: zimoun, Ludovic Courtès; +Cc: 38108
Le 2 décembre 2019 13:57:50 GMT+01:00, zimoun <zimon.toutoune@gmail.com> a écrit :
>Hi,
>
>Friendly ping. :-)
>Because the doc is moving forward and so some extra work will be
>required to push this boring patch.
>
>
>On Mon, 11 Nov 2019 at 21:52, zimoun <zimon.toutoune@gmail.com> wrote:
>
>> @Julien: Please tell me if it is annoying and I will participate, to
>> reduce the annoyance. At least for the French translation.
>
>For full context:
>https://debbugs.gnu.org/cgi/bugreport.cgi?bug=38108
>
>
>Cheers,
>simon
Sorry I didn't see the message before!
I'm fine with the changes. For now, our workflow is to translate only on a short period of time before each release. This kind of change will invalidate the translation of all affected sentences until the next translation round, which is annoying, but as long as you don't fix the manual for 1.0.1, it should be fine.
I'd like to improve our workflow at some point, but that's another discussion :)
^ permalink raw reply [flat|nested] 23+ messages in thread
* [bug#38108] [PATCH] doc: Fix typos.
2019-12-13 10:19 ` Julien Lepiller
@ 2019-12-13 11:27 ` zimoun
2019-12-13 11:55 ` Julien Lepiller
0 siblings, 1 reply; 23+ messages in thread
From: zimoun @ 2019-12-13 11:27 UTC (permalink / raw)
To: Julien Lepiller; +Cc: Ludovic Courtès, 38108
Hi Julien and Ludo,
On Fri, 13 Dec 2019 at 11:19, Julien Lepiller <julien@lepiller.eu> wrote:
> Sorry I didn't see the message before!
I fully understand! :-)
Busy by more important and interesting stuff (phd, jres, etc.)
> I'm fine with the changes. For now, our workflow is to translate only on a short period of time before each release. This kind of change will invalidate the translation of all affected sentences until the next translation round, which is annoying, but as long as you don't fix the manual for 1.0.1, it should be fine.
The patches does not apply anymore because the doc has changed in the
meantime. Life happens. :-)
I can send another patch that will apply... but because it is boring
and not fun at all, are the "pushers" not too busy now? to avoid to do
again the boring-and-not-fun stuff.
> I'd like to improve our workflow at some point, but that's another discussion :)
If you are coming to the Guix Days, we could arrange a slot to discuss
what could be improved and how. :-)
Cheers,
simon
^ permalink raw reply [flat|nested] 23+ messages in thread
* [bug#38108] [PATCH] doc: Fix typos.
2019-12-13 11:27 ` zimoun
@ 2019-12-13 11:55 ` Julien Lepiller
2020-05-22 0:01 ` [bug#38108] doc: Fix typos -- parenthesis dot zimoun
0 siblings, 1 reply; 23+ messages in thread
From: Julien Lepiller @ 2019-12-13 11:55 UTC (permalink / raw)
To: zimoun; +Cc: Ludovic Courtès, 38108
Le 13 décembre 2019 12:27:40 GMT+01:00, zimoun <zimon.toutoune@gmail.com> a écrit :
>Hi Julien and Ludo,
>
>On Fri, 13 Dec 2019 at 11:19, Julien Lepiller <julien@lepiller.eu>
>wrote:
>
>> Sorry I didn't see the message before!
>
>I fully understand! :-)
>Busy by more important and interesting stuff (phd, jres, etc.)
>
>> I'm fine with the changes. For now, our workflow is to translate only
>on a short period of time before each release. This kind of change will
>invalidate the translation of all affected sentences until the next
>translation round, which is annoying, but as long as you don't fix the
>manual for 1.0.1, it should be fine.
>
>The patches does not apply anymore because the doc has changed in the
>meantime. Life happens. :-)
>I can send another patch that will apply... but because it is boring
>and not fun at all, are the "pushers" not too busy now? to avoid to do
>again the boring-and-not-fun stuff.
>
>> I'd like to improve our workflow at some point, but that's another
>discussion :)
>
>If you are coming to the Guix Days, we could arrange a slot to discuss
>what could be improved and how. :-)
>
>
>Cheers,
>simon
You can send your patch, I'll push it this evening. I won't be at the guix days, but I talked a bit on irc this morning and will propose a plan soon.
^ permalink raw reply [flat|nested] 23+ messages in thread
* [bug#38108] doc: Fix typos -- parenthesis dot
2019-12-13 11:55 ` Julien Lepiller
@ 2020-05-22 0:01 ` zimoun
2020-05-22 0:08 ` zimoun
0 siblings, 1 reply; 23+ messages in thread
From: zimoun @ 2020-05-22 0:01 UTC (permalink / raw)
To: Julien Lepiller; +Cc: Ludovic Courtès, 38108
Hey Julien,
Sorry for the delay.
On Fri, 13 Dec 2019 at 12:55, Julien Lepiller <julien@lepiller.eu> wrote:
> You can send your patch, I'll push it this evening. I won't be at the guix days, but I talked a bit on irc this morning and will propose a plan soon.
Now, I do not know which evening you were talking about. ;-)
The v2 of the patch [1] applies against the commit cf1518f581.
[1] http://issues.guix.gnu.org/38108#12
Tell me if something is wrong. I have triple check but some mistakes
could remain.
Cheers,
simon
^ permalink raw reply [flat|nested] 23+ messages in thread
* [bug#38108] doc: Fix typos -- parenthesis dot
2020-05-22 0:01 ` [bug#38108] doc: Fix typos -- parenthesis dot zimoun
@ 2020-05-22 0:08 ` zimoun
2020-05-22 1:31 ` Julien Lepiller
0 siblings, 1 reply; 23+ messages in thread
From: zimoun @ 2020-05-22 0:08 UTC (permalink / raw)
To: Julien Lepiller; +Cc: Ludovic Courtès, 38108
On Fri, 22 May 2020 at 02:02, zimoun <zimon.toutoune@gmail.com> wrote:
> The v2 of the patch [1] applies against the commit cf1518f581.
Sorry, the commit message was wrong in v2; forgot to add
contributing.texi. See v3 [3] or tweak v2. :-)
[3] http://issues.guix.gnu.org/38108#14
Sorry again.
Cheers,
simon
^ permalink raw reply [flat|nested] 23+ messages in thread
* [bug#38108] doc: Fix typos -- parenthesis dot
2020-05-22 0:08 ` zimoun
@ 2020-05-22 1:31 ` Julien Lepiller
2020-05-22 8:01 ` zimoun
0 siblings, 1 reply; 23+ messages in thread
From: Julien Lepiller @ 2020-05-22 1:31 UTC (permalink / raw)
To: zimoun; +Cc: Ludovic Courtès, 38108
Le 21 mai 2020 20:08:05 GMT-04:00, zimoun <zimon.toutoune@gmail.com> a écrit :
>On Fri, 22 May 2020 at 02:02, zimoun <zimon.toutoune@gmail.com> wrote:
>
>> The v2 of the patch [1] applies against the commit cf1518f581.
>
>Sorry, the commit message was wrong in v2; forgot to add
>contributing.texi. See v3 [3] or tweak v2. :-)
>
>[3] http://issues.guix.gnu.org/38108#14
>
>Sorry again.
>
>Cheers,
>simon
Isn't it normal in English to end a sentence inside the parenthesis?
^ permalink raw reply [flat|nested] 23+ messages in thread
* [bug#38108] doc: Fix typos -- parenthesis dot
2020-05-22 1:31 ` Julien Lepiller
@ 2020-05-22 8:01 ` zimoun
2020-05-22 18:32 ` Leo Famulari
0 siblings, 1 reply; 23+ messages in thread
From: zimoun @ 2020-05-22 8:01 UTC (permalink / raw)
To: Julien Lepiller; +Cc: Ludovic Courtès, 38108
Hi Julien,
On Fri, 22 May 2020 at 03:31, Julien Lepiller <julien@lepiller.eu> wrote:
> Isn't it normal in English to end a sentence inside the parenthesis?
No, it is not what the rule of typos say, both in American and British
English. This message [1] of the thread summarizes the arguments: the
Chicago Manual of Style (holy bible of english typo) is pretty clear,
The Guardian too and discussion on IRC with natives confirmed.
Well, as you and Ludo too, I thought that the English convention was
always '.)' in all the cases but not; see example in [1]. Because we
are all three French, maybe teachers at school lied us. ;-)
[1] http://issues.guix.gnu.org/38108#4
Cheers,
simon
^ permalink raw reply [flat|nested] 23+ messages in thread
* [bug#38108] doc: Fix typos -- parenthesis dot
2020-05-22 8:01 ` zimoun
@ 2020-05-22 18:32 ` Leo Famulari
2020-05-25 9:43 ` zimoun
0 siblings, 1 reply; 23+ messages in thread
From: Leo Famulari @ 2020-05-22 18:32 UTC (permalink / raw)
To: zimoun; +Cc: Julien Lepiller, Ludovic Courtès, 38108
On Fri, May 22, 2020 at 10:01:50AM +0200, zimoun wrote:
> Hi Julien,
>
> On Fri, 22 May 2020 at 03:31, Julien Lepiller <julien@lepiller.eu> wrote:
>
> > Isn't it normal in English to end a sentence inside the parenthesis?
>
> No, it is not what the rule of typos say, both in American and British
> English. This message [1] of the thread summarizes the arguments: the
> Chicago Manual of Style (holy bible of english typo) is pretty clear,
> The Guardian too and discussion on IRC with natives confirmed.
>
> Well, as you and Ludo too, I thought that the English convention was
> always '.)' in all the cases but not; see example in [1]. Because we
> are all three French, maybe teachers at school lied us. ;-)
It's standard in American English to end the sentence outside of the
parentheses (like this). Maybe "Continental English" is different, I
don't know :)
^ permalink raw reply [flat|nested] 23+ messages in thread
* [bug#38108] doc: Fix typos -- parenthesis dot
2020-05-22 18:32 ` Leo Famulari
@ 2020-05-25 9:43 ` zimoun
2020-05-25 13:23 ` bug#38108: " Julien Lepiller
2020-05-25 17:33 ` Leo Famulari
0 siblings, 2 replies; 23+ messages in thread
From: zimoun @ 2020-05-25 9:43 UTC (permalink / raw)
To: Leo Famulari; +Cc: Julien Lepiller, Ludovic Courtès, 38108
Hi Leo,
On Fri, 22 May 2020 at 20:33, Leo Famulari <leo@famulari.name> wrote:
> It's standard in American English to end the sentence outside of the
> parentheses (like this). Maybe "Continental English" is different, I
> don't know :)
It is not different. :-)
The rule is:
This is an example (and here some words).
or
This is an example. (This is a full sentence.) The words still fly.
However, some English teachers in France say that the rule is:
This is an example (and here some words.)
which is wrong -- at least -- in US and UK English, as you confirm for US. :-)
The patch fixes the issue and now the manual is compliant with the
standard. Feel free to push it. ;-)
All the best,
simon
^ permalink raw reply [flat|nested] 23+ messages in thread
* bug#38108: doc: Fix typos -- parenthesis dot
2020-05-25 9:43 ` zimoun
@ 2020-05-25 13:23 ` Julien Lepiller
2020-05-26 7:57 ` [bug#38108] " zimoun
2020-05-25 17:33 ` Leo Famulari
1 sibling, 1 reply; 23+ messages in thread
From: Julien Lepiller @ 2020-05-25 13:23 UTC (permalink / raw)
To: zimoun; +Cc: Ludovic Courtès, 38108-done, Leo Famulari
Le Mon, 25 May 2020 11:43:57 +0200,
zimoun <zimon.toutoune@gmail.com> a écrit :
> Hi Leo,
>
> On Fri, 22 May 2020 at 20:33, Leo Famulari <leo@famulari.name> wrote:
>
> > It's standard in American English to end the sentence outside of the
> > parentheses (like this). Maybe "Continental English" is different, I
> > don't know :)
>
> It is not different. :-)
>
> The rule is:
>
> This is an example (and here some words).
>
> or
>
> This is an example. (This is a full sentence.) The words still
> fly.
>
> However, some English teachers in France say that the rule is:
>
> This is an example (and here some words.)
>
> which is wrong -- at least -- in US and UK English, as you confirm
> for US. :-)
>
>
> The patch fixes the issue and now the manual is compliant with the
> standard. Feel free to push it. ;-)
>
> All the best,
> simon
Pushed as ba2104aaa378bda6075a2093a4fc4851505aa789, thank you!
^ permalink raw reply [flat|nested] 23+ messages in thread
* [bug#38108] doc: Fix typos -- parenthesis dot
2020-05-25 9:43 ` zimoun
2020-05-25 13:23 ` bug#38108: " Julien Lepiller
@ 2020-05-25 17:33 ` Leo Famulari
1 sibling, 0 replies; 23+ messages in thread
From: Leo Famulari @ 2020-05-25 17:33 UTC (permalink / raw)
To: zimoun; +Cc: Julien Lepiller, Ludovic Courtès, 38108
On Mon, May 25, 2020 at 11:43:57AM +0200, zimoun wrote:
> However, some English teachers in France say that the rule is:
>
> This is an example (and here some words.)
It looks really weird to me!
^ permalink raw reply [flat|nested] 23+ messages in thread
* [bug#38108] [PATCH] doc: Fix typos.
2019-11-07 18:50 [bug#38108] [PATCH] doc: Fix typos zimoun
2019-11-08 14:10 ` Giovanni Biscuolo
2019-11-08 22:41 ` Ludovic Courtès
@ 2019-11-11 20:11 ` zimoun
2020-05-21 23:55 ` [bug#38108] [PATCH v2] " zimoun
2020-05-22 0:03 ` [bug#38108] [PATCH v3] " zimoun
4 siblings, 0 replies; 23+ messages in thread
From: zimoun @ 2019-11-11 20:11 UTC (permalink / raw)
To: 38108; +Cc: zimoun
From: zimoun <zimon.toutoune@gmail.com>
* doc/guix.texi: Fix typos.
---
doc/guix.texi | 79 ++++++++++++++++++++++++++-------------------------
1 file changed, 40 insertions(+), 39 deletions(-)
diff --git a/doc/guix.texi b/doc/guix.texi
index 27cb31dde5..48a6f550e5 100644
--- a/doc/guix.texi
+++ b/doc/guix.texi
@@ -67,6 +67,7 @@ Copyright @copyright{} 2019 Diego Nicola Barbato@*
Copyright @copyright{} 2019 Ivan Petkov@*
Copyright @copyright{} 2019 Jakob L. Kreuze@*
Copyright @copyright{} 2019 Kyle Andrews@*
+Copyright @copyright{} 2019 Simon Tournier@*
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.3 or
@@ -585,7 +586,7 @@ you may have to run @code{su -} or @code{sudo -i}. As @code{root}, run:
This creates @file{/gnu/store} (@pxref{The Store}) and @file{/var/guix}.
The latter contains a ready-to-use profile for @code{root} (see next
-step.)
+step).
Do @emph{not} unpack the tarball on a working Guix system since that
would overwrite its own essential files.
@@ -593,10 +594,10 @@ would overwrite its own essential files.
The @code{--warning=no-timestamp} option makes sure GNU@tie{}tar does
not emit warnings about ``implausibly old time stamps'' (such
warnings were triggered by GNU@tie{}tar 1.26 and older; recent
-versions are fine.)
+versions are fine).
They stem from the fact that all the
files in the archive have their modification time set to zero (which
-means January 1st, 1970.) This is done on purpose to make sure the
+means January 1st, 1970). This is done on purpose to make sure the
archive content is independent of its creation time, thus making it
reproducible.
@@ -680,7 +681,7 @@ there:
That way, assuming @file{/usr/local/share/info} is in the search path,
running @command{info guix} will open this manual (@pxref{Other Info
Directories,,, texinfo, GNU Texinfo}, for more details on changing the
-Info search path.)
+Info search path).
@item
@cindex substitutes, authorization thereof
@@ -1334,7 +1335,7 @@ build failed and the client specified @option{--keep-failed}
(@pxref{Invoking guix build, @option{--keep-failed}}).
The daemon listens for connections and spawns one sub-process for each session
-started by a client (one of the @command{guix} sub-commands.) The
+started by a client (one of the @command{guix} sub-commands). The
@command{guix processes} command allows you to get an overview of the activity
on your system by viewing each of the active sessions and clients.
@xref{Invoking guix processes}, for more information.
@@ -2266,7 +2267,7 @@ mkfs.ext4 -L my-root /dev/sda2
If you are instead planning to encrypt the root partition, you can use
the Cryptsetup/LUKS utilities to do that (see @inlinefmtifelse{html,
@uref{https://linux.die.net/man/8/cryptsetup, @code{man cryptsetup}},
-@code{man cryptsetup}} for more information.) Assuming you want to
+@code{man cryptsetup}} for more information). Assuming you want to
store the root partition on @file{/dev/sda2}, the command sequence would
be along these lines:
@@ -2732,7 +2733,7 @@ Install the specified @var{package}s.
Each @var{package} may specify either a simple package name, such as
@code{guile}, or a package name followed by an at-sign and version number,
such as @code{guile@@1.8.8} or simply @code{guile@@1.8} (in the latter
-case, the newest version prefixed by @code{1.8} is selected.)
+case, the newest version prefixed by @code{1.8} is selected).
If no version number is specified, the
newest available version will be selected. In addition, @var{package}
@@ -3323,7 +3324,7 @@ When using HTTPS, the server's X.509 certificate is @emph{not} validated
HTTPS clients such as Web browsers usually do. This is because Guix
authenticates substitute information itself, as explained above, which
is what we care about (whereas X.509 certificates are about
-authenticating bindings between domain names and public keys.)
+authenticating bindings between domain names and public keys).
@node Proxy Settings
@subsection Proxy Settings
@@ -4457,7 +4458,7 @@ The main options are:
@table @code
@item --export
-Export the specified store files or packages (see below.) Write the
+Export the specified store files or packages (see below). Write the
resulting archive to the standard output.
Dependencies are @emph{not} included in the output, unless
@@ -4474,7 +4475,7 @@ of the exported store items.
Read an archive from the standard input, and import the files listed
therein into the store. Abort if the archive has an invalid digital
signature, or if it is signed by a public key not among the authorized
-keys (see @code{--authorize} below.)
+keys (see @code{--authorize} below).
@item --missing
Read a list of store file names from the standard input, one per line,
@@ -4490,7 +4491,7 @@ generate the key pair.
The generated key pair is typically stored under @file{/etc/guix}, in
@file{signing-key.pub} (public key) and @file{signing-key.sec} (private
-key, which must be kept secret.) When @var{parameters} is omitted,
+key, which must be kept secret). When @var{parameters} is omitted,
an ECDSA key using the Ed25519 curve is generated, or, for Libgcrypt
versions before 1.6.0, it is a 4096-bit RSA key.
Alternatively, @var{parameters} can specify
@@ -4774,7 +4775,7 @@ that will be added to the environment directly.
@item --pure
Unset existing environment variables when building the new environment, except
-those specified with @option{--preserve} (see below.) This has the effect of
+those specified with @option{--preserve} (see below). This has the effect of
creating an environment in which search paths only contain package inputs.
@item --preserve=@var{regexp}
@@ -4813,7 +4814,7 @@ directory is created that matches the current user's home directory, and
The spawned process runs as the current user outside the container. Inside
the container, it has the same UID and GID as the current user, unless
-@option{--user} is passed (see below.)
+@option{--user} is passed (see below).
@item --network
@itemx -N
@@ -5641,7 +5642,7 @@ Lastly, @code{propagated-inputs} is similar to @code{inputs}, but the
specified packages will be automatically installed alongside the package
they belong to (@pxref{package-cmd-propagated-inputs, @command{guix
package}}, for information on how @command{guix package} deals with
-propagated inputs.)
+propagated inputs).
For example this is necessary when a C/C++ library needs headers of
another library to compile, or when a pkg-config file refers to another
@@ -6714,7 +6715,7 @@ argument.
Return @code{#t} when @var{path} designates a valid store item and
@code{#f} otherwise (an invalid item may exist on disk but still be
invalid, for instance because it is the result of an aborted or failed
-build.)
+build).
A @code{&store-protocol-error} condition is raised if @var{path} is not
prefixed by the store directory (@file{/gnu/store}).
@@ -7181,7 +7182,7 @@ The store monad---an alias for @var{%state-monad}.
Values in the store monad encapsulate accesses to the store. When its
effect is needed, a value of the store monad must be ``evaluated'' by
-passing it to the @code{run-with-store} procedure (see below.)
+passing it to the @code{run-with-store} procedure (see below).
@end defvr
@deffn {Scheme Procedure} run-with-store @var{store} @var{mval} [#:guile-for-build] [#:system (%current-system)]
@@ -7315,7 +7316,7 @@ into gexps. For example, a useful type of high-level objects that can be
inserted in a gexp is ``file-like objects'', which make it easy to
add files to the store and to refer to them in
derivations and such (see @code{local-file} and @code{plain-file}
-below.)
+below).
To illustrate the idea, here is an example of a gexp:
@@ -7485,7 +7486,7 @@ Like the above, but refers to native builds of the objects listed in
@end table
G-expressions created by @code{gexp} or @code{#~} are run-time objects
-of the @code{gexp?} type (see below.)
+of the @code{gexp?} type (see below).
@end deffn
@deffn {Scheme Syntax} with-imported-modules @var{modules} @var{body}@dots{}
@@ -7531,7 +7532,7 @@ Return @code{#t} if @var{obj} is a G-expression.
G-expressions are meant to be written to disk, either as code building
some derivation, or as plain files in the store. The monadic procedures
below allow you to do that (@pxref{The Store Monad}, for more
-information about monads.)
+information about monads).
@deffn {Monadic Procedure} gexp->derivation @var{name} @var{exp} @
[#:system (%current-system)] [#:target #f] [#:graft? #t] @
@@ -8467,7 +8468,7 @@ guix build --log-file -e '(@@ (gnu packages guile) guile-2.0)'
If a log is unavailable locally, and unless @code{--no-substitutes} is
passed, the command looks for a corresponding log on one of the
-substitute servers (as specified with @code{--substitute-urls}.)
+substitute servers (as specified with @code{--substitute-urls}).
So for instance, imagine you want to see the build log of GDB on MIPS,
but you are actually on an @code{x86_64} machine:
@@ -9222,7 +9223,7 @@ guix refresh -l -e '(@@@@ (gnu packages commencement) glibc-final)'
@end example
This command lists the dependents of the ``final'' libc (essentially all
-the packages.)
+the packages).
@item --update
@itemx -u
@@ -9329,7 +9330,7 @@ be used when passing @command{guix refresh} one or more package names:
@item --list-updaters
@itemx -L
-List available updaters and exit (see @option{--type} above.)
+List available updaters and exit (see @option{--type} above).
For each updater, display the fraction of packages it covers; at the
end, display the fraction of packages covered by all these updaters.
@@ -9393,7 +9394,7 @@ When this option is omitted, @command{guix refresh} uses
@file{~/.config/guix/upstream/trustedkeys.kbx} as the keyring for upstream
signing keys. OpenPGP signatures are checked against keys from this keyring;
missing keys are downloaded to this keyring as well (see
-@option{--key-download} below.)
+@option{--key-download} below).
You can export keys from your default GPG keyring into a keybox file using
commands like this one:
@@ -9769,7 +9770,7 @@ guix graph --type=reverse-package ocaml
...@: yields the graph of packages that @emph{explicitly} depend on OCaml (if
you are also interested in cases where OCaml is an implicit dependency, see
-@code{reverse-bag} below.)
+@code{reverse-bag} below).
Note that for core packages this can yield huge graphs. If all you want
is to know the number of packages that depend on a given package, use
@@ -10277,7 +10278,7 @@ When a difference is found between the hash of a locally-built item and
that of a server-provided substitute, or among substitutes provided by
different servers, the command displays it as in the example above and
its exit code is 2 (other non-zero exit codes denote other kinds of
-errors.)
+errors).
The one option that matters is:
@@ -10571,7 +10572,7 @@ integration tool; their process identifier (PID) is given by the
The @code{LockHeld} fields show which store items are currently locked by this
session, which corresponds to store items being built or substituted (the
@code{LockHeld} field is not displayed when @command{guix processes} is not
-running as root.) Last, by looking at the @code{ChildProcess} field, we
+running as root). Last, by looking at the @code{ChildProcess} field, we
understand that these three builds are being offloaded (@pxref{Daemon Offload
Setup}).
@@ -11203,7 +11204,7 @@ variables.
@defvr {Scheme Variable} %base-file-systems
These are essential file systems that are required on normal systems,
such as @var{%pseudo-terminal-file-system} and @var{%immutable-store} (see
-below.) Operating system declarations should always contain at least
+below). Operating system declarations should always contain at least
these.
@end defvr
@@ -11923,7 +11924,7 @@ Since this is part of @code{%base-services}, you can use
@code{modify-services} to customize the set of special files
(@pxref{Service Reference, @code{modify-services}}). But the simple way
to add a special file is @i{via} the @code{extra-special-file} procedure
-(see below.)
+(see below).
@end defvr
@deffn {Scheme Procedure} extra-special-file @var{file} @var{target}
@@ -14004,7 +14005,7 @@ definition (@pxref{operating-system Reference, system-wide packages}).
This is the type for the @uref{https://wiki.gnome.org/Projects/GDM/, GNOME
Desktop Manager} (GDM), a program that manages graphical display servers and
handles graphical user logins. Its value must be a @code{gdm-configuration}
-(see below.)
+(see below).
@cindex session types (X11)
@cindex X11 session types
@@ -15274,7 +15275,7 @@ gnome-session``. Currently only GNOME has support for Wayland.
@defvr {Scheme Variable} gnome-desktop-service-type
This is the type of the service that adds the @uref{https://www.gnome.org,
GNOME} desktop environment. Its value is a @code{gnome-desktop-configuration}
-object (see below.)
+object (see below).
This service adds the @code{gnome} package to the system profile, and extends
polkit with the actions from @code{gnome-settings-daemon}.
@@ -15292,7 +15293,7 @@ The GNOME package to use.
@defvr {Scheme Variable} xfce-desktop-service-type
This is the type of a service to run the @uref{Xfce, https://xfce.org/}
desktop environment. Its value is an @code{xfce-desktop-configuration} object
-(see below.)
+(see below).
This service adds the @code{xfce} package to the system profile, and
extends polkit with the ability for @code{thunar} to manipulate the file
@@ -15312,7 +15313,7 @@ The Xfce package to use.
@deffn {Scheme Variable} mate-desktop-service-type
This is the type of the service that runs the @uref{https://mate-desktop.org/,
MATE desktop environment}. Its value is a @code{mate-desktop-configuration}
-object (see below.)
+object (see below).
This service adds the @code{mate} package to the system
profile, and extends polkit with the actions from
@@ -21155,10 +21156,10 @@ configuration:
Note that ddclient needs to access credentials that are stored in a
@dfn{secret file}, by default @file{/etc/ddclient/secrets} (see
-@code{secret-file} below.) You are expected to create this file manually, in
+@code{secret-file} below). You are expected to create this file manually, in
an ``out-of-band'' fashion (you @emph{could} make this file part of the
service configuration, for instance by using @code{plain-file}, but it will be
-world-readable @i{via} @file{/gnu/store}.) See the examples in the
+world-readable @i{via} @file{/gnu/store}). See the examples in the
@file{share/ddclient} directory of the @code{ddclient} package.
@c %start of fragment
@@ -24935,7 +24936,7 @@ password, and which needs to access the @file{/etc/passwd} and
obvious security reasons. To address that, these executables are
@dfn{setuid-root}, meaning that they always run with root privileges
(@pxref{How Change Persona,,, libc, The GNU C Library Reference Manual},
-for more info about the setuid mechanism.)
+for more info about the setuid mechanism).
The store itself @emph{cannot} contain setuid programs: that would be a
security issue since any user on the system can write derivations that
@@ -25988,7 +25989,7 @@ each other:
Emit in Dot/Graphviz format to standard output the @dfn{service
extension graph} of the operating system defined in @var{file}
(@pxref{Service Composition}, for more information on service
-extensions.)
+extensions).
The command:
@@ -26517,7 +26518,7 @@ services and service types. This interface is provided by the
@deffn {Scheme Procedure} service @var{type} [@var{value}]
Return a new service of @var{type}, a @code{<service-type>} object (see
-below.) @var{value} can be any object; it represents the parameters of
+below). @var{value} can be any object; it represents the parameters of
this particular service instance.
When @var{value} is omitted, the default value specified by @var{type}
@@ -27025,7 +27026,7 @@ Occasionally, important security vulnerabilities are discovered in software
packages and must be patched. Guix developers try hard to keep track of
known vulnerabilities and to apply fixes as soon as possible in the
@code{master} branch of Guix (we do not yet provide a ``stable'' branch
-containing only security updates.) The @command{guix lint} tool helps
+containing only security updates). The @command{guix lint} tool helps
developers find out about vulnerable versions of software packages in the
distribution:
@@ -27463,7 +27464,7 @@ reason.
Guix is based on the @uref{https://nixos.org/nix/, Nix package manager},
which was designed and
implemented by Eelco Dolstra, with contributions from other people (see
-the @file{nix/AUTHORS} file in Guix.) Nix pioneered functional package
+the @file{nix/AUTHORS} file in Guix). Nix pioneered functional package
management, and promoted unprecedented features, such as transactional
package upgrades and rollbacks, per-user profiles, and referentially
transparent build processes. Without this work, Guix would not exist.
--
2.24.0.rc1
^ permalink raw reply related [flat|nested] 23+ messages in thread* [bug#38108] [PATCH v2] doc: Fix typos.
2019-11-07 18:50 [bug#38108] [PATCH] doc: Fix typos zimoun
` (2 preceding siblings ...)
2019-11-11 20:11 ` [bug#38108] [PATCH] doc: Fix typos zimoun
@ 2020-05-21 23:55 ` zimoun
2020-05-22 0:03 ` [bug#38108] [PATCH v3] " zimoun
4 siblings, 0 replies; 23+ messages in thread
From: zimoun @ 2020-05-21 23:55 UTC (permalink / raw)
To: 38108; +Cc: zimoun
* doc/guix.texi: Fix typos.
---
doc/contributing.texi | 2 +-
doc/guix.texi | 86 +++++++++++++++++++++----------------------
2 files changed, 44 insertions(+), 44 deletions(-)
diff --git a/doc/contributing.texi b/doc/contributing.texi
index 44bec00236..0ef5e2cc0a 100644
--- a/doc/contributing.texi
+++ b/doc/contributing.texi
@@ -501,7 +501,7 @@ It is a good idea to strip commit identifiers in the @code{version}
field to, say, 7 digits. It avoids an aesthetic annoyance (assuming
aesthetics have a role to play here) as well as problems related to OS
limits such as the maximum shebang length (127 bytes for the Linux
-kernel.) It is best to use the full commit identifiers in
+kernel). It is best to use the full commit identifiers in
@code{origin}s, though, to avoid ambiguities. A typical package
definition may look like this:
diff --git a/doc/guix.texi b/doc/guix.texi
index 216422fe31..18bf554c1e 100644
--- a/doc/guix.texi
+++ b/doc/guix.texi
@@ -609,7 +609,7 @@ you may have to run @code{su -} or @code{sudo -i}. As @code{root}, run:
This creates @file{/gnu/store} (@pxref{The Store}) and @file{/var/guix}.
The latter contains a ready-to-use profile for @code{root} (see next
-step.)
+step).
Do @emph{not} unpack the tarball on a working Guix system since that
would overwrite its own essential files.
@@ -617,10 +617,10 @@ would overwrite its own essential files.
The @option{--warning=no-timestamp} option makes sure GNU@tie{}tar does
not emit warnings about ``implausibly old time stamps'' (such
warnings were triggered by GNU@tie{}tar 1.26 and older; recent
-versions are fine.)
+versions are fine).
They stem from the fact that all the
files in the archive have their modification time set to zero (which
-means January 1st, 1970.) This is done on purpose to make sure the
+means January 1st, 1970). This is done on purpose to make sure the
archive content is independent of its creation time, thus making it
reproducible.
@@ -705,7 +705,7 @@ there:
That way, assuming @file{/usr/local/share/info} is in the search path,
running @command{info guix} will open this manual (@pxref{Other Info
Directories,,, texinfo, GNU Texinfo}, for more details on changing the
-Info search path.)
+Info search path).
@item
@cindex substitutes, authorization thereof
@@ -1363,7 +1363,7 @@ build failed and the client specified @option{--keep-failed}
(@pxref{Invoking guix build, @option{--keep-failed}}).
The daemon listens for connections and spawns one sub-process for each session
-started by a client (one of the @command{guix} sub-commands.) The
+started by a client (one of the @command{guix} sub-commands). The
@command{guix processes} command allows you to get an overview of the activity
on your system by viewing each of the active sessions and clients.
@xref{Invoking guix processes}, for more information.
@@ -2292,7 +2292,7 @@ mkfs.ext4 -L my-root /dev/sda2
If you are instead planning to encrypt the root partition, you can use
the Cryptsetup/LUKS utilities to do that (see @inlinefmtifelse{html,
@uref{https://linux.die.net/man/8/cryptsetup, @code{man cryptsetup}},
-@code{man cryptsetup}} for more information.) Assuming you want to
+@code{man cryptsetup}} for more information). Assuming you want to
store the root partition on @file{/dev/sda2}, the command sequence would
be along these lines:
@@ -2764,7 +2764,7 @@ Install the specified @var{package}s.
Each @var{package} may specify either a simple package name, such as
@code{guile}, or a package name followed by an at-sign and version number,
such as @code{guile@@1.8.8} or simply @code{guile@@1.8} (in the latter
-case, the newest version prefixed by @code{1.8} is selected.)
+case, the newest version prefixed by @code{1.8} is selected).
If no version number is specified, the
newest available version will be selected. In addition, @var{package}
@@ -3368,7 +3368,7 @@ When using HTTPS, the server's X.509 certificate is @emph{not} validated
HTTPS clients such as Web browsers usually do. This is because Guix
authenticates substitute information itself, as explained above, which
is what we care about (whereas X.509 certificates are about
-authenticating bindings between domain names and public keys.)
+authenticating bindings between domain names and public keys).
@node Proxy Settings
@subsection Proxy Settings
@@ -4563,7 +4563,7 @@ The main options are:
@table @code
@item --export
-Export the specified store files or packages (see below.) Write the
+Export the specified store files or packages (see below). Write the
resulting archive to the standard output.
Dependencies are @emph{not} included in the output, unless
@@ -4580,7 +4580,7 @@ exported store items.
Read an archive from the standard input, and import the files listed
therein into the store. Abort if the archive has an invalid digital
signature, or if it is signed by a public key not among the authorized
-keys (see @option{--authorize} below.)
+keys (see @option{--authorize} below).
@item --missing
Read a list of store file names from the standard input, one per line,
@@ -4596,7 +4596,7 @@ to generate the key pair.
The generated key pair is typically stored under @file{/etc/guix}, in
@file{signing-key.pub} (public key) and @file{signing-key.sec} (private
-key, which must be kept secret.) When @var{parameters} is omitted,
+key, which must be kept secret). When @var{parameters} is omitted,
an ECDSA key using the Ed25519 curve is generated, or, for Libgcrypt
versions before 1.6.0, it is a 4096-bit RSA key.
Alternatively, @var{parameters} can specify
@@ -4912,7 +4912,7 @@ interpreted as packages that will be added to the environment directly.
@item --pure
Unset existing environment variables when building the new environment, except
-those specified with @option{--preserve} (see below.) This has the effect of
+those specified with @option{--preserve} (see below). This has the effect of
creating an environment in which search paths only contain package inputs.
@item --preserve=@var{regexp}
@@ -4930,7 +4930,7 @@ guix environment --pure --preserve=^SLURM --ad-hoc openmpi @dots{} \
This example runs @command{mpirun} in a context where the only environment
variables defined are @env{PATH}, environment variables whose name starts
with @samp{SLURM}, as well as the usual ``precious'' variables (@env{HOME},
-@env{USER}, etc.)
+@env{USER}, etc.).
@item --search-paths
Display the environment variable definitions that make up the
@@ -4951,7 +4951,7 @@ directory is created that matches the current user's home directory, and
The spawned process runs as the current user outside the container. Inside
the container, it has the same UID and GID as the current user, unless
-@option{--user} is passed (see below.)
+@option{--user} is passed (see below).
@item --network
@itemx -N
@@ -5852,7 +5852,7 @@ Lastly, @code{propagated-inputs} is similar to @code{inputs}, but the
specified packages will be automatically installed alongside the package
they belong to (@pxref{package-cmd-propagated-inputs, @command{guix
package}}, for information on how @command{guix package} deals with
-propagated inputs.)
+propagated inputs).
For example this is necessary when a C/C++ library needs headers of
another library to compile, or when a pkg-config file refers to another
@@ -7027,7 +7027,7 @@ argument.
Return @code{#t} when @var{path} designates a valid store item and
@code{#f} otherwise (an invalid item may exist on disk but still be
invalid, for instance because it is the result of an aborted or failed
-build.)
+build).
A @code{&store-protocol-error} condition is raised if @var{path} is not
prefixed by the store directory (@file{/gnu/store}).
@@ -7072,7 +7072,7 @@ directory in the store, but may produce more.
@cindex dependencies, build-time
The inputs of the derivations---i.e., its build-time dependencies---which may
be other derivations or plain files in the store (patches, build scripts,
-etc.)
+etc.).
@item
The system type targeted by the derivation---e.g., @code{x86_64-linux}.
@@ -7494,7 +7494,7 @@ The store monad---an alias for @code{%state-monad}.
Values in the store monad encapsulate accesses to the store. When its
effect is needed, a value of the store monad must be ``evaluated'' by
-passing it to the @code{run-with-store} procedure (see below.)
+passing it to the @code{run-with-store} procedure (see below).
@end defvr
@deffn {Scheme Procedure} run-with-store @var{store} @var{mval} [#:guile-for-build] [#:system (%current-system)]
@@ -7632,7 +7632,7 @@ into gexps. For example, a useful type of high-level objects that can be
inserted in a gexp is ``file-like objects'', which make it easy to
add files to the store and to refer to them in
derivations and such (see @code{local-file} and @code{plain-file}
-below.)
+below).
To illustrate the idea, here is an example of a gexp:
@@ -7803,7 +7803,7 @@ Like the above, but refers to native builds of the objects listed in
@end table
G-expressions created by @code{gexp} or @code{#~} are run-time objects
-of the @code{gexp?} type (see below.)
+of the @code{gexp?} type (see below).
@end deffn
@deffn {Scheme Syntax} with-imported-modules @var{modules} @var{body}@dots{}
@@ -7849,7 +7849,7 @@ Return @code{#t} if @var{obj} is a G-expression.
G-expressions are meant to be written to disk, either as code building
some derivation, or as plain files in the store. The monadic procedures
below allow you to do that (@pxref{The Store Monad}, for more
-information about monads.)
+information about monads).
@deffn {Monadic Procedure} gexp->derivation @var{name} @var{exp} @
[#:system (%current-system)] [#:target #f] [#:graft? #t] @
@@ -8860,7 +8860,7 @@ guix build --log-file -e '(@@ (gnu packages guile) guile-2.0)'
If a log is unavailable locally, and unless @option{--no-substitutes} is
passed, the command looks for a corresponding log on one of the
-substitute servers (as specified with @option{--substitute-urls}.)
+substitute servers (as specified with @option{--substitute-urls}).
So for instance, imagine you want to see the build log of GDB on MIPS,
but you are actually on an @code{x86_64} machine:
@@ -9084,7 +9084,7 @@ hash (@pxref{Invoking guix archive}).
@item --exclude-vcs
@itemx -x
When combined with @option{--recursive}, exclude version control system
-directories (@file{.bzr}, @file{.git}, @file{.hg}, etc.)
+directories (@file{.bzr}, @file{.git}, @file{.hg}, etc.).
@vindex git-fetch
As an example, here is how you would compute the hash of a Git checkout,
@@ -9617,7 +9617,7 @@ guix refresh -l -e '(@@@@ (gnu packages commencement) glibc-final)'
@end example
This command lists the dependents of the ``final'' libc (essentially all
-the packages.)
+the packages).
@item --update
@itemx -u
@@ -9724,7 +9724,7 @@ be used when passing @command{guix refresh} one or more package names:
@item --list-updaters
@itemx -L
-List available updaters and exit (see @option{--type} above.)
+List available updaters and exit (see @option{--type} above).
For each updater, display the fraction of packages it covers; at the
end, display the fraction of packages covered by all these updaters.
@@ -9788,7 +9788,7 @@ When this option is omitted, @command{guix refresh} uses
@file{~/.config/guix/upstream/trustedkeys.kbx} as the keyring for upstream
signing keys. OpenPGP signatures are checked against keys from this keyring;
missing keys are downloaded to this keyring as well (see
-@option{--key-download} below.)
+@option{--key-download} below).
You can export keys from your default GPG keyring into a keybox file using
commands like this one:
@@ -10200,7 +10200,7 @@ guix graph --type=reverse-package ocaml
...@: yields the graph of packages that @emph{explicitly} depend on OCaml (if
you are also interested in cases where OCaml is an implicit dependency, see
-@code{reverse-bag} below.)
+@code{reverse-bag} below).
Note that for core packages this can yield huge graphs. If all you want
is to know the number of packages that depend on a given package, use
@@ -10774,7 +10774,7 @@ When a difference is found between the hash of a locally-built item and
that of a server-provided substitute, or among substitutes provided by
different servers, the command displays it as in the example above and
its exit code is 2 (other non-zero exit codes denote other kinds of
-errors.)
+errors).
The one option that matters is:
@@ -11100,7 +11100,7 @@ integration tool; their process identifier (PID) is given by the
The @code{LockHeld} fields show which store items are currently locked by this
session, which corresponds to store items being built or substituted (the
@code{LockHeld} field is not displayed when @command{guix processes} is not
-running as root.) Last, by looking at the @code{ChildProcess} field, we
+running as root). Last, by looking at the @code{ChildProcess} field, we
understand that these three builds are being offloaded (@pxref{Daemon Offload
Setup}).
@@ -11742,7 +11742,7 @@ variables.
@defvr {Scheme Variable} %base-file-systems
These are essential file systems that are required on normal systems,
such as @code{%pseudo-terminal-file-system} and @code{%immutable-store} (see
-below.) Operating system declarations should always contain at least
+below). Operating system declarations should always contain at least
these.
@end defvr
@@ -12571,7 +12571,7 @@ Since this is part of @code{%base-services}, you can use
@code{modify-services} to customize the set of special files
(@pxref{Service Reference, @code{modify-services}}). But the simple way
to add a special file is @i{via} the @code{extra-special-file} procedure
-(see below.)
+(see below).
@end defvr
@deffn {Scheme Procedure} extra-special-file @var{file} @var{target}
@@ -14882,7 +14882,7 @@ definition (@pxref{operating-system Reference, system-wide packages}).
This is the type for the @uref{https://wiki.gnome.org/Projects/GDM/, GNOME
Desktop Manager} (GDM), a program that manages graphical display servers and
handles graphical user logins. Its value must be a @code{gdm-configuration}
-(see below.)
+(see below).
@cindex session types (X11)
@cindex X11 session types
@@ -16153,7 +16153,7 @@ gnome-session``. Currently only GNOME has support for Wayland.
@defvr {Scheme Variable} gnome-desktop-service-type
This is the type of the service that adds the @uref{https://www.gnome.org,
GNOME} desktop environment. Its value is a @code{gnome-desktop-configuration}
-object (see below.)
+object (see below).
This service adds the @code{gnome} package to the system profile, and extends
polkit with the actions from @code{gnome-settings-daemon}.
@@ -16171,7 +16171,7 @@ The GNOME package to use.
@defvr {Scheme Variable} xfce-desktop-service-type
This is the type of a service to run the @uref{Xfce, https://xfce.org/}
desktop environment. Its value is an @code{xfce-desktop-configuration} object
-(see below.)
+(see below).
This service adds the @code{xfce} package to the system profile, and
extends polkit with the ability for @code{thunar} to manipulate the file
@@ -16191,7 +16191,7 @@ The Xfce package to use.
@deffn {Scheme Variable} mate-desktop-service-type
This is the type of the service that runs the @uref{https://mate-desktop.org/,
MATE desktop environment}. Its value is a @code{mate-desktop-configuration}
-object (see below.)
+object (see below).
This service adds the @code{mate} package to the system
profile, and extends polkit with the actions from
@@ -16505,7 +16505,7 @@ Users need to be in the @code{lp} group to access the D-Bus service.
@defvr {Scheme Variable} gnome-keyring-service-type
This is the type of the service that adds the
@uref{https://wiki.gnome.org/Projects/GnomeKeyring, GNOME Keyring}. Its
-value is a @code{gnome-keyring-configuration} object (see below.)
+value is a @code{gnome-keyring-configuration} object (see below).
This service adds the @code{gnome-keyring} package to the system profile
and extends PAM with entries using @code{pam_gnome_keyring.so}, unlocking
@@ -22252,10 +22252,10 @@ configuration:
Note that ddclient needs to access credentials that are stored in a
@dfn{secret file}, by default @file{/etc/ddclient/secrets} (see
-@code{secret-file} below.) You are expected to create this file manually, in
+@code{secret-file} below). You are expected to create this file manually, in
an ``out-of-band'' fashion (you @emph{could} make this file part of the
service configuration, for instance by using @code{plain-file}, but it will be
-world-readable @i{via} @file{/gnu/store}.) See the examples in the
+world-readable @i{via} @file{/gnu/store}). See the examples in the
@file{share/ddclient} directory of the @code{ddclient} package.
@c %start of fragment
@@ -26330,7 +26330,7 @@ password, and which needs to access the @file{/etc/passwd} and
obvious security reasons. To address that, these executables are
@dfn{setuid-root}, meaning that they always run with root privileges
(@pxref{How Change Persona,,, libc, The GNU C Library Reference Manual},
-for more info about the setuid mechanism.)
+for more info about the setuid mechanism).
The store itself @emph{cannot} contain setuid programs: that would be a
security issue since any user on the system can write derivations that
@@ -27467,7 +27467,7 @@ each other:
Emit in Dot/Graphviz format to standard output the @dfn{service
extension graph} of the operating system defined in @var{file}
(@pxref{Service Composition}, for more information on service
-extensions.)
+extensions).
The command:
@@ -28028,7 +28028,7 @@ services and service types. This interface is provided by the
@deffn {Scheme Procedure} service @var{type} [@var{value}]
Return a new service of @var{type}, a @code{<service-type>} object (see
-below.) @var{value} can be any object; it represents the parameters of
+below). @var{value} can be any object; it represents the parameters of
this particular service instance.
When @var{value} is omitted, the default value specified by @var{type}
@@ -28584,7 +28584,7 @@ Occasionally, important security vulnerabilities are discovered in software
packages and must be patched. Guix developers try hard to keep track of
known vulnerabilities and to apply fixes as soon as possible in the
@code{master} branch of Guix (we do not yet provide a ``stable'' branch
-containing only security updates.) The @command{guix lint} tool helps
+containing only security updates). The @command{guix lint} tool helps
developers find out about vulnerable versions of software packages in the
distribution:
@@ -29022,7 +29022,7 @@ reason.
Guix is based on the @uref{https://nixos.org/nix/, Nix package manager},
which was designed and
implemented by Eelco Dolstra, with contributions from other people (see
-the @file{nix/AUTHORS} file in Guix.) Nix pioneered functional package
+the @file{nix/AUTHORS} file in Guix). Nix pioneered functional package
management, and promoted unprecedented features, such as transactional
package upgrades and rollbacks, per-user profiles, and referentially
transparent build processes. Without this work, Guix would not exist.
--
2.26.2
^ permalink raw reply related [flat|nested] 23+ messages in thread* [bug#38108] [PATCH v3] doc: Fix typos.
2019-11-07 18:50 [bug#38108] [PATCH] doc: Fix typos zimoun
` (3 preceding siblings ...)
2020-05-21 23:55 ` [bug#38108] [PATCH v2] " zimoun
@ 2020-05-22 0:03 ` zimoun
4 siblings, 0 replies; 23+ messages in thread
From: zimoun @ 2020-05-22 0:03 UTC (permalink / raw)
To: 38108; +Cc: zimoun
* doc/guix.texi: Fix typos.
* doc/contributing.texi: Fix typos.
---
doc/contributing.texi | 2 +-
doc/guix.texi | 86 +++++++++++++++++++++----------------------
2 files changed, 44 insertions(+), 44 deletions(-)
diff --git a/doc/contributing.texi b/doc/contributing.texi
index 44bec00236..0ef5e2cc0a 100644
--- a/doc/contributing.texi
+++ b/doc/contributing.texi
@@ -501,7 +501,7 @@ It is a good idea to strip commit identifiers in the @code{version}
field to, say, 7 digits. It avoids an aesthetic annoyance (assuming
aesthetics have a role to play here) as well as problems related to OS
limits such as the maximum shebang length (127 bytes for the Linux
-kernel.) It is best to use the full commit identifiers in
+kernel). It is best to use the full commit identifiers in
@code{origin}s, though, to avoid ambiguities. A typical package
definition may look like this:
diff --git a/doc/guix.texi b/doc/guix.texi
index 216422fe31..18bf554c1e 100644
--- a/doc/guix.texi
+++ b/doc/guix.texi
@@ -609,7 +609,7 @@ you may have to run @code{su -} or @code{sudo -i}. As @code{root}, run:
This creates @file{/gnu/store} (@pxref{The Store}) and @file{/var/guix}.
The latter contains a ready-to-use profile for @code{root} (see next
-step.)
+step).
Do @emph{not} unpack the tarball on a working Guix system since that
would overwrite its own essential files.
@@ -617,10 +617,10 @@ would overwrite its own essential files.
The @option{--warning=no-timestamp} option makes sure GNU@tie{}tar does
not emit warnings about ``implausibly old time stamps'' (such
warnings were triggered by GNU@tie{}tar 1.26 and older; recent
-versions are fine.)
+versions are fine).
They stem from the fact that all the
files in the archive have their modification time set to zero (which
-means January 1st, 1970.) This is done on purpose to make sure the
+means January 1st, 1970). This is done on purpose to make sure the
archive content is independent of its creation time, thus making it
reproducible.
@@ -705,7 +705,7 @@ there:
That way, assuming @file{/usr/local/share/info} is in the search path,
running @command{info guix} will open this manual (@pxref{Other Info
Directories,,, texinfo, GNU Texinfo}, for more details on changing the
-Info search path.)
+Info search path).
@item
@cindex substitutes, authorization thereof
@@ -1363,7 +1363,7 @@ build failed and the client specified @option{--keep-failed}
(@pxref{Invoking guix build, @option{--keep-failed}}).
The daemon listens for connections and spawns one sub-process for each session
-started by a client (one of the @command{guix} sub-commands.) The
+started by a client (one of the @command{guix} sub-commands). The
@command{guix processes} command allows you to get an overview of the activity
on your system by viewing each of the active sessions and clients.
@xref{Invoking guix processes}, for more information.
@@ -2292,7 +2292,7 @@ mkfs.ext4 -L my-root /dev/sda2
If you are instead planning to encrypt the root partition, you can use
the Cryptsetup/LUKS utilities to do that (see @inlinefmtifelse{html,
@uref{https://linux.die.net/man/8/cryptsetup, @code{man cryptsetup}},
-@code{man cryptsetup}} for more information.) Assuming you want to
+@code{man cryptsetup}} for more information). Assuming you want to
store the root partition on @file{/dev/sda2}, the command sequence would
be along these lines:
@@ -2764,7 +2764,7 @@ Install the specified @var{package}s.
Each @var{package} may specify either a simple package name, such as
@code{guile}, or a package name followed by an at-sign and version number,
such as @code{guile@@1.8.8} or simply @code{guile@@1.8} (in the latter
-case, the newest version prefixed by @code{1.8} is selected.)
+case, the newest version prefixed by @code{1.8} is selected).
If no version number is specified, the
newest available version will be selected. In addition, @var{package}
@@ -3368,7 +3368,7 @@ When using HTTPS, the server's X.509 certificate is @emph{not} validated
HTTPS clients such as Web browsers usually do. This is because Guix
authenticates substitute information itself, as explained above, which
is what we care about (whereas X.509 certificates are about
-authenticating bindings between domain names and public keys.)
+authenticating bindings between domain names and public keys).
@node Proxy Settings
@subsection Proxy Settings
@@ -4563,7 +4563,7 @@ The main options are:
@table @code
@item --export
-Export the specified store files or packages (see below.) Write the
+Export the specified store files or packages (see below). Write the
resulting archive to the standard output.
Dependencies are @emph{not} included in the output, unless
@@ -4580,7 +4580,7 @@ exported store items.
Read an archive from the standard input, and import the files listed
therein into the store. Abort if the archive has an invalid digital
signature, or if it is signed by a public key not among the authorized
-keys (see @option{--authorize} below.)
+keys (see @option{--authorize} below).
@item --missing
Read a list of store file names from the standard input, one per line,
@@ -4596,7 +4596,7 @@ to generate the key pair.
The generated key pair is typically stored under @file{/etc/guix}, in
@file{signing-key.pub} (public key) and @file{signing-key.sec} (private
-key, which must be kept secret.) When @var{parameters} is omitted,
+key, which must be kept secret). When @var{parameters} is omitted,
an ECDSA key using the Ed25519 curve is generated, or, for Libgcrypt
versions before 1.6.0, it is a 4096-bit RSA key.
Alternatively, @var{parameters} can specify
@@ -4912,7 +4912,7 @@ interpreted as packages that will be added to the environment directly.
@item --pure
Unset existing environment variables when building the new environment, except
-those specified with @option{--preserve} (see below.) This has the effect of
+those specified with @option{--preserve} (see below). This has the effect of
creating an environment in which search paths only contain package inputs.
@item --preserve=@var{regexp}
@@ -4930,7 +4930,7 @@ guix environment --pure --preserve=^SLURM --ad-hoc openmpi @dots{} \
This example runs @command{mpirun} in a context where the only environment
variables defined are @env{PATH}, environment variables whose name starts
with @samp{SLURM}, as well as the usual ``precious'' variables (@env{HOME},
-@env{USER}, etc.)
+@env{USER}, etc.).
@item --search-paths
Display the environment variable definitions that make up the
@@ -4951,7 +4951,7 @@ directory is created that matches the current user's home directory, and
The spawned process runs as the current user outside the container. Inside
the container, it has the same UID and GID as the current user, unless
-@option{--user} is passed (see below.)
+@option{--user} is passed (see below).
@item --network
@itemx -N
@@ -5852,7 +5852,7 @@ Lastly, @code{propagated-inputs} is similar to @code{inputs}, but the
specified packages will be automatically installed alongside the package
they belong to (@pxref{package-cmd-propagated-inputs, @command{guix
package}}, for information on how @command{guix package} deals with
-propagated inputs.)
+propagated inputs).
For example this is necessary when a C/C++ library needs headers of
another library to compile, or when a pkg-config file refers to another
@@ -7027,7 +7027,7 @@ argument.
Return @code{#t} when @var{path} designates a valid store item and
@code{#f} otherwise (an invalid item may exist on disk but still be
invalid, for instance because it is the result of an aborted or failed
-build.)
+build).
A @code{&store-protocol-error} condition is raised if @var{path} is not
prefixed by the store directory (@file{/gnu/store}).
@@ -7072,7 +7072,7 @@ directory in the store, but may produce more.
@cindex dependencies, build-time
The inputs of the derivations---i.e., its build-time dependencies---which may
be other derivations or plain files in the store (patches, build scripts,
-etc.)
+etc.).
@item
The system type targeted by the derivation---e.g., @code{x86_64-linux}.
@@ -7494,7 +7494,7 @@ The store monad---an alias for @code{%state-monad}.
Values in the store monad encapsulate accesses to the store. When its
effect is needed, a value of the store monad must be ``evaluated'' by
-passing it to the @code{run-with-store} procedure (see below.)
+passing it to the @code{run-with-store} procedure (see below).
@end defvr
@deffn {Scheme Procedure} run-with-store @var{store} @var{mval} [#:guile-for-build] [#:system (%current-system)]
@@ -7632,7 +7632,7 @@ into gexps. For example, a useful type of high-level objects that can be
inserted in a gexp is ``file-like objects'', which make it easy to
add files to the store and to refer to them in
derivations and such (see @code{local-file} and @code{plain-file}
-below.)
+below).
To illustrate the idea, here is an example of a gexp:
@@ -7803,7 +7803,7 @@ Like the above, but refers to native builds of the objects listed in
@end table
G-expressions created by @code{gexp} or @code{#~} are run-time objects
-of the @code{gexp?} type (see below.)
+of the @code{gexp?} type (see below).
@end deffn
@deffn {Scheme Syntax} with-imported-modules @var{modules} @var{body}@dots{}
@@ -7849,7 +7849,7 @@ Return @code{#t} if @var{obj} is a G-expression.
G-expressions are meant to be written to disk, either as code building
some derivation, or as plain files in the store. The monadic procedures
below allow you to do that (@pxref{The Store Monad}, for more
-information about monads.)
+information about monads).
@deffn {Monadic Procedure} gexp->derivation @var{name} @var{exp} @
[#:system (%current-system)] [#:target #f] [#:graft? #t] @
@@ -8860,7 +8860,7 @@ guix build --log-file -e '(@@ (gnu packages guile) guile-2.0)'
If a log is unavailable locally, and unless @option{--no-substitutes} is
passed, the command looks for a corresponding log on one of the
-substitute servers (as specified with @option{--substitute-urls}.)
+substitute servers (as specified with @option{--substitute-urls}).
So for instance, imagine you want to see the build log of GDB on MIPS,
but you are actually on an @code{x86_64} machine:
@@ -9084,7 +9084,7 @@ hash (@pxref{Invoking guix archive}).
@item --exclude-vcs
@itemx -x
When combined with @option{--recursive}, exclude version control system
-directories (@file{.bzr}, @file{.git}, @file{.hg}, etc.)
+directories (@file{.bzr}, @file{.git}, @file{.hg}, etc.).
@vindex git-fetch
As an example, here is how you would compute the hash of a Git checkout,
@@ -9617,7 +9617,7 @@ guix refresh -l -e '(@@@@ (gnu packages commencement) glibc-final)'
@end example
This command lists the dependents of the ``final'' libc (essentially all
-the packages.)
+the packages).
@item --update
@itemx -u
@@ -9724,7 +9724,7 @@ be used when passing @command{guix refresh} one or more package names:
@item --list-updaters
@itemx -L
-List available updaters and exit (see @option{--type} above.)
+List available updaters and exit (see @option{--type} above).
For each updater, display the fraction of packages it covers; at the
end, display the fraction of packages covered by all these updaters.
@@ -9788,7 +9788,7 @@ When this option is omitted, @command{guix refresh} uses
@file{~/.config/guix/upstream/trustedkeys.kbx} as the keyring for upstream
signing keys. OpenPGP signatures are checked against keys from this keyring;
missing keys are downloaded to this keyring as well (see
-@option{--key-download} below.)
+@option{--key-download} below).
You can export keys from your default GPG keyring into a keybox file using
commands like this one:
@@ -10200,7 +10200,7 @@ guix graph --type=reverse-package ocaml
...@: yields the graph of packages that @emph{explicitly} depend on OCaml (if
you are also interested in cases where OCaml is an implicit dependency, see
-@code{reverse-bag} below.)
+@code{reverse-bag} below).
Note that for core packages this can yield huge graphs. If all you want
is to know the number of packages that depend on a given package, use
@@ -10774,7 +10774,7 @@ When a difference is found between the hash of a locally-built item and
that of a server-provided substitute, or among substitutes provided by
different servers, the command displays it as in the example above and
its exit code is 2 (other non-zero exit codes denote other kinds of
-errors.)
+errors).
The one option that matters is:
@@ -11100,7 +11100,7 @@ integration tool; their process identifier (PID) is given by the
The @code{LockHeld} fields show which store items are currently locked by this
session, which corresponds to store items being built or substituted (the
@code{LockHeld} field is not displayed when @command{guix processes} is not
-running as root.) Last, by looking at the @code{ChildProcess} field, we
+running as root). Last, by looking at the @code{ChildProcess} field, we
understand that these three builds are being offloaded (@pxref{Daemon Offload
Setup}).
@@ -11742,7 +11742,7 @@ variables.
@defvr {Scheme Variable} %base-file-systems
These are essential file systems that are required on normal systems,
such as @code{%pseudo-terminal-file-system} and @code{%immutable-store} (see
-below.) Operating system declarations should always contain at least
+below). Operating system declarations should always contain at least
these.
@end defvr
@@ -12571,7 +12571,7 @@ Since this is part of @code{%base-services}, you can use
@code{modify-services} to customize the set of special files
(@pxref{Service Reference, @code{modify-services}}). But the simple way
to add a special file is @i{via} the @code{extra-special-file} procedure
-(see below.)
+(see below).
@end defvr
@deffn {Scheme Procedure} extra-special-file @var{file} @var{target}
@@ -14882,7 +14882,7 @@ definition (@pxref{operating-system Reference, system-wide packages}).
This is the type for the @uref{https://wiki.gnome.org/Projects/GDM/, GNOME
Desktop Manager} (GDM), a program that manages graphical display servers and
handles graphical user logins. Its value must be a @code{gdm-configuration}
-(see below.)
+(see below).
@cindex session types (X11)
@cindex X11 session types
@@ -16153,7 +16153,7 @@ gnome-session``. Currently only GNOME has support for Wayland.
@defvr {Scheme Variable} gnome-desktop-service-type
This is the type of the service that adds the @uref{https://www.gnome.org,
GNOME} desktop environment. Its value is a @code{gnome-desktop-configuration}
-object (see below.)
+object (see below).
This service adds the @code{gnome} package to the system profile, and extends
polkit with the actions from @code{gnome-settings-daemon}.
@@ -16171,7 +16171,7 @@ The GNOME package to use.
@defvr {Scheme Variable} xfce-desktop-service-type
This is the type of a service to run the @uref{Xfce, https://xfce.org/}
desktop environment. Its value is an @code{xfce-desktop-configuration} object
-(see below.)
+(see below).
This service adds the @code{xfce} package to the system profile, and
extends polkit with the ability for @code{thunar} to manipulate the file
@@ -16191,7 +16191,7 @@ The Xfce package to use.
@deffn {Scheme Variable} mate-desktop-service-type
This is the type of the service that runs the @uref{https://mate-desktop.org/,
MATE desktop environment}. Its value is a @code{mate-desktop-configuration}
-object (see below.)
+object (see below).
This service adds the @code{mate} package to the system
profile, and extends polkit with the actions from
@@ -16505,7 +16505,7 @@ Users need to be in the @code{lp} group to access the D-Bus service.
@defvr {Scheme Variable} gnome-keyring-service-type
This is the type of the service that adds the
@uref{https://wiki.gnome.org/Projects/GnomeKeyring, GNOME Keyring}. Its
-value is a @code{gnome-keyring-configuration} object (see below.)
+value is a @code{gnome-keyring-configuration} object (see below).
This service adds the @code{gnome-keyring} package to the system profile
and extends PAM with entries using @code{pam_gnome_keyring.so}, unlocking
@@ -22252,10 +22252,10 @@ configuration:
Note that ddclient needs to access credentials that are stored in a
@dfn{secret file}, by default @file{/etc/ddclient/secrets} (see
-@code{secret-file} below.) You are expected to create this file manually, in
+@code{secret-file} below). You are expected to create this file manually, in
an ``out-of-band'' fashion (you @emph{could} make this file part of the
service configuration, for instance by using @code{plain-file}, but it will be
-world-readable @i{via} @file{/gnu/store}.) See the examples in the
+world-readable @i{via} @file{/gnu/store}). See the examples in the
@file{share/ddclient} directory of the @code{ddclient} package.
@c %start of fragment
@@ -26330,7 +26330,7 @@ password, and which needs to access the @file{/etc/passwd} and
obvious security reasons. To address that, these executables are
@dfn{setuid-root}, meaning that they always run with root privileges
(@pxref{How Change Persona,,, libc, The GNU C Library Reference Manual},
-for more info about the setuid mechanism.)
+for more info about the setuid mechanism).
The store itself @emph{cannot} contain setuid programs: that would be a
security issue since any user on the system can write derivations that
@@ -27467,7 +27467,7 @@ each other:
Emit in Dot/Graphviz format to standard output the @dfn{service
extension graph} of the operating system defined in @var{file}
(@pxref{Service Composition}, for more information on service
-extensions.)
+extensions).
The command:
@@ -28028,7 +28028,7 @@ services and service types. This interface is provided by the
@deffn {Scheme Procedure} service @var{type} [@var{value}]
Return a new service of @var{type}, a @code{<service-type>} object (see
-below.) @var{value} can be any object; it represents the parameters of
+below). @var{value} can be any object; it represents the parameters of
this particular service instance.
When @var{value} is omitted, the default value specified by @var{type}
@@ -28584,7 +28584,7 @@ Occasionally, important security vulnerabilities are discovered in software
packages and must be patched. Guix developers try hard to keep track of
known vulnerabilities and to apply fixes as soon as possible in the
@code{master} branch of Guix (we do not yet provide a ``stable'' branch
-containing only security updates.) The @command{guix lint} tool helps
+containing only security updates). The @command{guix lint} tool helps
developers find out about vulnerable versions of software packages in the
distribution:
@@ -29022,7 +29022,7 @@ reason.
Guix is based on the @uref{https://nixos.org/nix/, Nix package manager},
which was designed and
implemented by Eelco Dolstra, with contributions from other people (see
-the @file{nix/AUTHORS} file in Guix.) Nix pioneered functional package
+the @file{nix/AUTHORS} file in Guix). Nix pioneered functional package
management, and promoted unprecedented features, such as transactional
package upgrades and rollbacks, per-user profiles, and referentially
transparent build processes. Without this work, Guix would not exist.
--
2.26.2
^ permalink raw reply related [flat|nested] 23+ messages in thread