It's real fun when you have thousands of text scripts that have to be ported across OSes and have to figure out what program can best be used to batch convert them all. This is probably all confusing to non-UNIX geeks, but this is something I've had to deal with for the entire 20+ years I've been dealing with text between DOS and UNIX. The vi command line way I deal with this is:Īnd they will be be converted to 'cr' (carriage return, not carriage return-linefeed) and when you save the file it'll be all well in the UNIX world. twdiff (TextWrangler Diff Helper)Bare Bones Software, Inc.No. Over on the Mac side, TextEdit generally seems to handle text files properly regardless of where they are created, but vi will show those 'crlf' characters as a ^M, which is not a big deal, but annoying. and it has a command-line diff, twdiff i use the BBEdit/TW diff often (i own a BBEdit 6.5 list at home, but at work have to use whatever's free), but it isn't always right for what i want it's good for analysis, but harder to just get a list of what is different, as i can with plain diff (which i might then pipe into TW for a few quick regexp. BMW 188mm Diff Rebuild Kit (1983-1998 E30 E34 E36). Oddly enough, if you edit a text file created by Mac OS X with the "DOS" command line 'edit' command under Windows and just save it, it'll convert the newlines to what Windows expects with the rest of the Windows text editors. You'll note that if you use vi on a text file created by a Windows notepad, for example, will show ^M characters at each newline, while text files created by Mac OS X will look all goofy using windows notepad. This is also why I use command line utilities for both OS's, and this is something that goes back to the early days of all the UNIX's and the DOS world.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |