Quote:
Originally Posted by geekmaster
Anyway, perhaps this auto-conversion thing has to do with the smb/cifs shares I am using for all my kindle stuff, because I do not remember this problem before.
|
SMB/CIFS (Windows or *nix) considers all payload as binary, although I seem to recall that at least some implementations have an "auto EL feature".
I rarely use CIFS here, so the exact option(s) are buried in my memory from easy recall.
Quote:
Originally Posted by geekmaster
Again, Ehhh, sorry about getting angry because you could not get your uploaded files correct, when they were probably correct all along.
|
Windows I/O defaults to "cooked" (same as MS-DOS) for any file that it does not recognize as binary.
All applications follow that general rule, except those that try to be "user helpful" by making gratuitous changes.
I.E: "text editors"
know they are dealing with "text" and use cooked;
"hex editors"
know they are dealing with "binary" and don't use cooked.
Both flavors of gratuitous "user helpers" get it wrong (tm) at times.
*nix (and Linux) systems only support "cooked" in the tty drivers (it is an option, you can view/change with stty).
And it is rare to find an application that is gratuitously "user helpful", but they do occur at times (usually as applications "ported" from a non-*nix system).
Quote:
Originally Posted by geekmaster
knc1: You reported seeing CRs too... What tools did you use to determine that? Any windows stuff?
|
I do not admit, even among close friends, that I might own a Windows license or two.
knc1 reported that Geany offered to convert the line endings to unix endings.
At which point,
knc1 jumped to the conclusion that the file needed conversion.
My Bad;
I did not actually test that offer by exectuting the choice to see if it would have made any changes.
So I now realize that the Geany offer may not have been conclusive that non-unix line endings where present.
@Ehhh This is an example on HowTo
not top post. GM has shown you other examples.