donovanglover-nix-config/editorconfig/README.md

# editorconfig

[editorconfig][editorconfig] is the standard tool for editing consistency between editors.

## Use Cases

editorconfig can be used to:

- Finally forget about whether spaces or tabs are being used; editorconfig will handle this automatically for you
- Share the same indentation settings in all the editors you and your colleagues use

You should not use editorconfig if:

- You should use editorconfig.

## Usage

If you use my [`.vimrc`](/vim) or [code](/code) config, editorconfig is already applied.

[editorconfig]: https://github.com/editorconfig/editorconfig
docs: Add READMEs for wal, term, and editorconfig Also, after some testing, it turns out that my previous assumption about systemd was wrong. Placing a service in default.target.wants directly will cause the service to instead not be recognized by systemd. 2018-10-24 03:18:56 +02:00			`# editorconfig`

docs: Update READMEs for code, editorconfig, and gpg 2018-11-20 04:50:09 +01:00			`[editorconfig][editorconfig] is the standard tool for editing consistency between editors.`
docs: Add READMEs for wal, term, and editorconfig Also, after some testing, it turns out that my previous assumption about systemd was wrong. Placing a service in default.target.wants directly will cause the service to instead not be recognized by systemd. 2018-10-24 03:18:56 +02:00
docs: Update READMEs for code, editorconfig, and gpg 2018-11-20 04:50:09 +01:00			`## Use Cases`
docs: Add READMEs for wal, term, and editorconfig Also, after some testing, it turns out that my previous assumption about systemd was wrong. Placing a service in default.target.wants directly will cause the service to instead not be recognized by systemd. 2018-10-24 03:18:56 +02:00
docs: Update READMEs for code, editorconfig, and gpg 2018-11-20 04:50:09 +01:00			`editorconfig can be used to:`
docs: Add READMEs for wal, term, and editorconfig Also, after some testing, it turns out that my previous assumption about systemd was wrong. Placing a service in default.target.wants directly will cause the service to instead not be recognized by systemd. 2018-10-24 03:18:56 +02:00
docs: Update READMEs for code, editorconfig, and gpg 2018-11-20 04:50:09 +01:00			`- Finally forget about whether spaces or tabs are being used; editorconfig will handle this automatically for you`
			`- Share the same indentation settings in all the editors you and your colleagues use`
docs: Add READMEs for wal, term, and editorconfig Also, after some testing, it turns out that my previous assumption about systemd was wrong. Placing a service in default.target.wants directly will cause the service to instead not be recognized by systemd. 2018-10-24 03:18:56 +02:00
docs: Update READMEs for code, editorconfig, and gpg 2018-11-20 04:50:09 +01:00			`You should not use editorconfig if:`

			`- You should use editorconfig.`
docs: Add READMEs for wal, term, and editorconfig Also, after some testing, it turns out that my previous assumption about systemd was wrong. Placing a service in default.target.wants directly will cause the service to instead not be recognized by systemd. 2018-10-24 03:18:56 +02:00
			`## Usage`

docs: Update READMEs for code, editorconfig, and gpg 2018-11-20 04:50:09 +01:00			If you use my [`.vimrc`](/vim) or [code](/code) config, editorconfig is already applied.
docs: Add READMEs for wal, term, and editorconfig Also, after some testing, it turns out that my previous assumption about systemd was wrong. Placing a service in default.target.wants directly will cause the service to instead not be recognized by systemd. 2018-10-24 03:18:56 +02:00
docs: Update READMEs for code, editorconfig, and gpg 2018-11-20 04:50:09 +01:00			`[editorconfig]: https://github.com/editorconfig/editorconfig`