unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: 宋文武 <iyzsong@outlook.com>
To: Maxime Devos <maximedevos@telenet.be>
Cc: 54293@debbugs.gnu.org
Subject: [bug#54293] [WIP] home: Add home-git-service-type
Date: Wed, 09 Mar 2022 20:18:32 +0800	[thread overview]
Message-ID: <TYCP286MB189784F08409D048990E3FBBA30A9@TYCP286MB1897.JPNP286.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <a7fdfcfb23c47227f7d0e19eda6688783980f58e.camel@telenet.be> (Maxime Devos's message of "Mon, 07 Mar 2022 18:58:26 +0100")

Maxime Devos <maximedevos@telenet.be> writes:

> 宋文武 schreef op ma 07-03-2022 om 22:51 [+0800]:
>> +           (for-each
>> +            (match-lambda
>> +              ((key value)
>> +               (simple-format #t "\t~a = ~s~%" key value)))
>
> What if I want to set the key 'bar' to the value 'foo bar ' (without
> teh quotes, but with the trailing space)?  If I do ‘git config
> 'foo.bar' "foo bar "’, then the following is added to .git/config:
>
> [foo]
>         bar = "foo bar "
>
> so it seems that some escaping may be necessary.

Yes, '~s' in the format string will use 'write' which will print strings
in double quotes with some escapes.  I think it's compatible with
gitconfig's requirement.

>
> Also, what character encoding does git expect .git/config expect it to
> be in?  UTF-8, whatever the current locale's encoding is, ...?

I guess it expect UTF-8, will do some tests later, thanks!




  reply	other threads:[~2022-03-09 12:19 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-07 14:51 [bug#54293] [WIP] home: Add home-git-service-type 宋文武
2022-03-07 17:58 ` Maxime Devos
2022-03-09 12:18   ` 宋文武 [this message]
2022-03-07 18:01 ` Maxime Devos
2022-03-07 18:12   ` Maxime Devos
2022-03-07 18:02 ` Maxime Devos
2022-03-07 18:04 ` Maxime Devos
2022-03-07 18:11 ` Maxime Devos
2022-03-09 12:50   ` 宋文武
2022-03-12 22:27     ` Maxime Devos
2022-03-12  2:22 ` [bug#54293] [PATCH v2] " iyzsong
2022-03-12  9:51   ` Maxime Devos
2022-03-12  9:54   ` Maxime Devos
2022-03-29 13:56     ` [bug#54293] [WIP] " Ludovic Courtès
2022-03-12  9:58   ` [bug#54293] [PATCH v2] " Maxime Devos
2022-03-12 10:02   ` Maxime Devos
2022-03-12 10:03   ` Maxime Devos
2022-03-12 10:11   ` Maxime Devos
2022-03-12 10:12   ` Maxime Devos
2022-03-12 10:21   ` Maxime Devos
2022-03-12 10:24   ` Maxime Devos
2022-03-12 10:26   ` Maxime Devos
2022-03-12 10:31   ` Maxime Devos
2022-03-12 10:39   ` Maxime Devos
2022-05-21 13:47   ` [bug#54293] [WIP] " Ludovic Courtès

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=TYCP286MB189784F08409D048990E3FBBA30A9@TYCP286MB1897.JPNP286.PROD.OUTLOOK.COM \
    --to=iyzsong@outlook.com \
    --cc=54293@debbugs.gnu.org \
    --cc=maximedevos@telenet.be \
    /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).