11/30/2022 0 Comments Jedit setup line endings![]() So that tells you that: yup, "0." must be the odd man out. You might try dos2unix with the -info switch like this: $ dos2unix -info - *Ġ 35 0 no_bom text Some network appliances are really, really picky about how their certificate files are encoded. And I already knew that those were cert files. (By the way: this is what one of my typical "certificate work" directories looks like.) And one of these files has different line endings. Let's try a little quiz: I've got some files. The trouble with regular file is this: Sometimes it's trying to be too smart/too specific. I sometimes have to check this for PEM certificate files. (So if it does not explicitly mention any kind of line endings then this means: "LF line endings".) It will just output text for Linux/Unix "LF" line endings. #Jedit setup line endings for mac#It will output with CR line endings for MAC line endings.It will output with CRLF line endings for DOS/Windows line endings.Short version: file -k somefile.txt will tell you. But for tough cases try file -k or dosunix -ih. Try file, then file -k, then dos2unix -ihįile will usually be enough. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |