home-manager/tests/modules/programs/git/git-with-email-expected.conf

[sendemail "hm-account"]
	from = hm@example.org
	smtpEncryption = tls
	smtpServer = smtp.example.org
	smtpUser = home.manager.jr

[sendemail "hm@example.com"]
	from = hm@example.com
	smtpEncryption = tls
	smtpServer = smtp.example.com
	smtpUser = home.manager

[user]
	email = hm@example.com
	name = H. M. Test
git: quote sendemail section header This will allow, e.g., the character `@` in the email identity. Also adds a test case. Fixes #557 2019-01-29 18:17:24 +01:00			`[sendemail "hm-account"]`
git: fix the config output formatting When setting values using the `git config --set` command, git formats the file a bit differently. This changes the output so it maps to that format. Differences: * each `key = value` in a section is prefixed by a tab character * the `=` between the key and the value is surrounded by spaces PR #1069 2020-03-05 15:57:19 +01:00			`from = hm@example.org`
			`smtpEncryption = tls`
			`smtpServer = smtp.example.org`
			`smtpUser = home.manager.jr`
git: quote sendemail section header This will allow, e.g., the character `@` in the email identity. Also adds a test case. Fixes #557 2019-01-29 18:17:24 +01:00
			`[sendemail "hm@example.com"]`
git: fix the config output formatting When setting values using the `git config --set` command, git formats the file a bit differently. This changes the output so it maps to that format. Differences: * each `key = value` in a section is prefixed by a tab character * the `=` between the key and the value is surrounded by spaces PR #1069 2020-03-05 15:57:19 +01:00			`from = hm@example.com`
			`smtpEncryption = tls`
			`smtpServer = smtp.example.com`
			`smtpUser = home.manager`
git: quote sendemail section header This will allow, e.g., the character `@` in the email identity. Also adds a test case. Fixes #557 2019-01-29 18:17:24 +01:00
			`[user]`
git: fix the config output formatting When setting values using the `git config --set` command, git formats the file a bit differently. This changes the output so it maps to that format. Differences: * each `key = value` in a section is prefixed by a tab character * the `=` between the key and the value is surrounded by spaces PR #1069 2020-03-05 15:57:19 +01:00			`email = hm@example.com`
			`name = H. M. Test`