williampuk / line-ending-converter Goto Github PK

Behavior like the encoding and syntax selection indicator.

Test cases related to the status view are not passing. Need some help to fix them

Just like the 'UTF-8' that is on the status bar the line-ending of the current file could be displayed for information purposes.

I use windows but other colleagues use Mac. So I have to revert the line-ending. But after I change the line-ending to LF, every time I open a file and instantly save it, the atom change yellow to warn me . So I use git bash , and find there is a unexpected new line in the end of the page.
If there is wrong usage ,please tell me .Thanks!

Hi, how about to convert line endings automatically on save? Ideally we could create project settings for that. What do you think?

This plugin is great, except on my windows machine its not working at all :(

As with most feature requests in Atom, my issue will start...

In Sublime, I can open a bunch of files in the editor and use the command palette to convert them all to Unix/Windows/whatever (and then save all). It'd be cool if this package could do the same. I have a feeling it's not too difficult, just iterate through all editors for the current window and apply the EOL change to each.

What would be better (but harder), and what Sublime does not do, would be to be able to do it for a bunch of files without having to open them. Maybe right click in tree view on a file to immediately convert and save the file, and on a directory to immediately convert and save all files within the directory (recursively). And maybe an extra command to just convert all files in project.

In an ideal world you could use a mini editor to accept a kind of glob patter for files to be converted, a bit like the "file/directory pattern" in the file in project dialog. That way I can make sure I only target certain files (e.g. *.php) rather than possibly erroneously converting files I need to keep a \r\n or binary files (though I'd suggest that this plugin somehow detect between a binary and a text file and make sure it doesn't convert binary files).

What do you think? Maybe take it one step at a time and start with the "all open editors" one?

Have and option in setting to hide line-ending-converter commands from the context menu.

Reason: I don't use this package that often, but when I do, I access it from command palette so for me it just pollutes context menu.