Brian wrote:
> Regarding efficiency, I am strictly talking about the code path.
> Having Cygwin add a \r when the file is written the first time should
> be more efficient than reprocessing the whole thing after it's been
> processed the first time, or at the least reparsing the lines in an
> outpu
Hannu E K Nevalainen wrote:
> james pentland also wrote:
> > this makes sed unusable or undesirable for a large
> > number of files i might want to edit.
>
> I don't take this as an implication of 'bulk' edits. So your "many files"
> falls on this. Also; using sed implies automatic changes.
My r
Brian Dessent wrote:
> Hannu E K Nevalainen wrote:
>
>> You wrote:
>>> james pentland wrote:
>>>
sed has the unfortunate property that it reduces dos
format line endings to unix format line endings.
>>>
>>> Use a text mode mount.
>>
>> Using a sledgahammer for a nail?
>> Better to use un
Hannu E K Nevalainen wrote:
> You wrote:
> > james pentland wrote:
> >
> >> sed has the unfortunate property that it reduces dos
> >> format line endings to unix format line endings.
> >
> > Use a text mode mount.
>
> Using a sledgahammer for a nail?
> Better to use unix2dos A.K.A. u2d.
I disag
You wrote:
> james pentland wrote:
>
>> sed has the unfortunate property that it reduces dos
>> format line endings to unix format line endings.
>
> Use a text mode mount.
>
> Brian
Using a sledgahammer for a nail?
Better to use unix2dos A.K.A. u2d.
/Hannu E K Nevalainen, B.Sc. EE Microcomput
james pentland wrote:
> sed has the unfortunate property that it reduces dos
> format line endings to unix format line endings.
Use a text mode mount.
Brian
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation:
6 matches
Mail list logo