Quote:
Originally Posted by knc1
... "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.
...
@Ehhh This is an example on HowTo not top post. GM has shown you other examples.
|
I used a hex editor built into a windows "programmer's editor". That programmer's editor offers to convert "Unix" to DOS line-endings if CRs are missing (when loading from a local hard drive). It did not give that warning when loading these scripts from a network share (CIFs on linux). And worse, its built-in hex edit shows CRs. It is not normal for that program to convert unless you say "Yes" to is warning about missing CRs. There was no warning. It does not have a history of auto-converting, so I suspect that the problem is with the CIFS share. Who knows?
P.S. The top-post EXAMPLES were provided by ixtab. I posted links to the RFC and the "why" pages.