Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add .editorconfig file #9

Merged
merged 2 commits into from
May 26, 2014
Merged

Add .editorconfig file #9

merged 2 commits into from
May 26, 2014

Conversation

TomOne
Copy link
Contributor

@TomOne TomOne commented May 25, 2014

This adds an .editorconfig file as I already wrote in chocolatey-archive/chocolatey#294 (comment)

@TomOne
Copy link
Contributor Author

TomOne commented May 25, 2014

BTW, there are two workarounds to at least advise folks to not use crappy editors like M$ notepad.exe which doesn’t even support UTF-8 correctly, or older Notepad++ versions:

  1. Set end-of-line character of *.nuspec files to LF instead of CRLF. notepad.exe is probably the only editor out there which doesn’t support that. If a package creator sees everything in a single line, he would probably stop using notepad.exe. 😆
  2. Add a comment with at least one non-ASCII unicode character to *.nuspec files. This forces editors that do support UTF-8, but don’t use it by default, to use UTF-8. This affects even the latest version of Notepad++ if there’s the configuration from older versions. The comment could look like this:
<!-- Do not remove this test for UTF-8: if “Ω” doesn’t appear as greek uppercase omega letter enclosed in quotation marks, you should use an editor that supports UTF-8, not this one. -->

If you give me an OK for this, I’ll integrate these two workarounds into the templates.

@ferventcoder
Copy link
Contributor

Love it. Make the changes!

On Sunday, May 25, 2014, TomOne notifications@github.com wrote:

BTW, there are two workarounds to at least advise folks to not use crappy
editors like M$ notepad.exe which doesn’t even support UTF-8 correctly,
or older Notepad++ versions:

  1. Set end-of-line character of *.nuspec files to LF instead of CRLF.
    notepad.exe is probably the only editor out there which doesn’t support
    that. If a package creator sees everything in a single line, he would
    probably stop using notepad.exe. [image: 😆]
  2. Add a comment with at least one non-ASCII unicode character to *.nuspecfiles. This forces editors that do support UTF-8, but don’t use it by
    default, to use UTF-8. This affects even the latest version of Notepad++ if
    there’s the configuration from older versions. The comment could look like
    this:

If you give me an OK for this, I’ll integrate these two workarounds into
the templates.


Reply to this email directly or view it on GitHubhttps://github.com//pull/9#issuecomment-44139481
.

Rob
"Be passionate in all you do"

http://devlicio.us/blogs/rob_reynolds
http://ferventcoder.com
http://twitter.com/ferventcoder

@TomOne
Copy link
Contributor Author

TomOne commented May 25, 2014

All right, I’ll do it. The comment for the nuspecs looks a bit weird but it does what we want. 😄

@TomOne
Copy link
Contributor Author

TomOne commented May 25, 2014

Done. Just merge this and the other PR #10

ferventcoder added a commit that referenced this pull request May 26, 2014
@ferventcoder ferventcoder merged commit b9f18e7 into chocolatey-archive:master May 26, 2014
@TomOne TomOne deleted the editorconfig branch May 27, 2014 14:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants