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.

Sign up for GitHub

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

Jump to bottom

Smarter line endings #5

Closed
inikulin opened this issue Oct 24, 2014 · 1 comment
Closed

Smarter line endings #5

inikulin opened this issue Oct 24, 2014 · 1 comment

Comments

@inikulin
Copy link
Owner

Line endings are huge PITA for people who use different OS's for development (like I do). \n is not recognized by Windows in some editors, meanwhille \r\n ends up with extra ^M character in *nix systems. Currently dmn enforces \r\n in generated files (see: inikulin/ineed#3). We need to take smarter approach. Use the following strategy: If we already have .npmignore use it's line endings, otherwise use line endings of the OS in which dmn was invoked.
@inikulin inikulin mentioned this issue Oct 24, 2014
Closed
@inikulin
Copy link
Owner Author

Updated version is in npm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@inikulin