Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #31029
| Date | 2012-10-09 09:26 -0500 |
|---|---|
| From | Tim Chase <python.list@tim.thechases.com> |
| Subject | Re: mangled messages |
| References | (2 earlier) <adht95F2luqU1@mid.individual.net> <mailman.1982.1349764176.27098.python-list@python.org> <qotr4p8cdot.fsf@ruuvi.it.helsinki.fi> <mailman.1987.1349780698.27098.python-list@python.org> <qotpq4r7svd.fsf@ruuvi.it.helsinki.fi> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.2000.1349792713.27098.python-list@python.org> (permalink) |
On 10/09/12 07:05, Jussi Piitulainen wrote: > Tim Chase writes: >> However, it might be that there is no CR+LF on the last line, >> or that one line is missing the CR, so your viewer heuristic >> (vim does this) thinks it has Unix NL-only line-endings and >> shows the ^M on all the lines that have the CR. All for one >> stray line without. > > That doesn't sound robust. The problem is still quite rare for > me. Vim's heuristic is that, if *all* the lines end in CR+LF, it's a DOS-formatted file; otherwise it's a Unix-style (LF) file with spurious CRs in it (they just happen to come at the end of most-but-not-all lines). It works quite robustly, since writing the file back out will reliably put the CRs back where they were and leave the non-CR'ed lines as they were with only LF. Vim makes it pretty easy to remove the spurious CRs and then change the file-format from Unix to DOS line-endings and write it out if that's what you want[1]. -tkc [1] :%s/\r$ :set ff=dos :w which (1) removes the spurious/inconsistent CRs, (2) tells vim that newlines should be written as CR+LF when writing and (3) writes the file back out to disk.
Back to comp.lang.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Unpaking Tuple sajuptpm <sajuptpm@gmail.com> - 2012-10-06 03:09 -0700
Re: Unpaking Tuple Chris Rebert <clp2@rebertia.com> - 2012-10-06 03:27 -0700
Re: Unpaking Tuple Roy Smith <roy@panix.com> - 2012-10-06 08:46 -0400
Re: Unpaking Tuple Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2012-10-06 15:08 +0000
Re: Unpaking Tuple Thomas Bach <thbach@students.uni-mainz.de> - 2012-10-08 23:45 +0200
RE: Unpaking Tuple "Prasad, Ramit" <ramit.prasad@jpmorgan.com> - 2012-10-08 22:21 +0000
Re: RE: Unpaking Tuple Bob Martin <bob.martin@excite.com> - 2012-10-09 07:07 +0100
Re: Unpaking Tuple Dave Angel <d@davea.name> - 2012-10-09 02:29 -0400
Re: Unpaking Tuple Jussi Piitulainen <jpiitula@ling.helsinki.fi> - 2012-10-09 10:22 +0300
Re: mangled messages (was: Unpaking Tuple) Tim Chase <python.list@tim.thechases.com> - 2012-10-09 05:48 -0500
Re: mangled messages (was: Unpaking Tuple) Jussi Piitulainen <jpiitula@ling.helsinki.fi> - 2012-10-09 15:05 +0300
Re: mangled messages Tim Chase <python.list@tim.thechases.com> - 2012-10-09 09:26 -0500
Re: Unpaking Tuple Grant Edwards <invalid@invalid.invalid> - 2012-10-09 14:11 +0000
RE: RE: Unpaking Tuple "Prasad, Ramit" <ramit.prasad@jpmorgan.com> - 2012-10-09 16:40 +0000
Re: Unpaking Tuple Robert Miles <robertmiles@teranews.com> - 2012-11-18 19:14 -0600
Re: Unpaking Tuple Hans Mulder <hansmu@xs4all.nl> - 2012-11-19 02:56 +0100
Re: Unpaking Tuple woooee <woooee@gmail.com> - 2012-10-07 10:58 -0700
Re: Unpaking Tuple Terry Reedy <tjreedy@udel.edu> - 2012-10-07 16:03 -0400
csiph-web