Re^6: Convert file to unix

This is quite the waste of time and space, but still if you insist, this comment made the assertion (that simply resaving 'dos-mode' files in vi would fix them), and when I referred to the parent in my reply to you that is the comment I was referring to, i.e. the parent of the comment you were replying to, not the parent of your reply.

Also thanks for the information on removing ^Ms with vi, but my reply to Re: Convert file to unix was intended to clarify the comment re: fixing 'dos mode' text files, not to solicit a solution to the problem in vi.

Comment on Re^6: Convert file to unix

Replies are listed 'Best First'.
Re^7: Convert file to unix by Marshall (Canon) on Aug 19, 2009 at 13:05 UTC
Sorry if I appeared to complicate things. That wasn't my intent. I replied in a different thread context. I don't know of a way to have a both "seamless" (meaning everybody uses their current favorite editor, eg, NotePad, vi or whatever in exactly the same that they use it now) and high performance (meaning sub-second update) editing of a file visible from both a Unix box and a Windows box. However, a check-it-out, modify-it, check-it-in model would for sure work. I guess the issue is how to make something like that work as easily as possible... The "get the data into memory and open that data in an editor" is not hard - lots of these things can "read the other guys format". The hard part is "SAVE"..maybe I want to save the data in HIS format, not my native format. That means resolving conflicts with others who might be trying to do the same thing (ie updating the same file) which is the most difficult part and oh, by the way, some format changes along the way. I guess I just stuck my head into a mess. But these problems have solutions.	[reply]

Replies are listed 'Best First'.

Re^7: Convert file to unix
by Marshall (Canon) on Aug 19, 2009 at 13:05 UTC

However, a check-it-out, modify-it, check-it-in model would for sure work. I guess the issue is how to make something like that work as easily as possible... The "get the data into memory and open that data in an editor" is not hard - lots of these things can "read the other guys format". The hard part is "SAVE"..maybe I want to save the data in HIS format, not my native format. That means resolving conflicts with others who might be trying to do the same thing (ie updating the same file) which is the most difficult part and oh, by the way, some format changes along the way.

I guess I just stuck my head into a mess. But these problems have solutions.

[reply]