On Saturday 13 April 2013 10:44:20 Michał Górny wrote:
> The edos2unix is quite useful when handling DOS-sourced packages.
> But since it's a bash function, you can't reasonably use it from within
> find invocation. And often you hit packages which are all flooded with
> CRLFs that you need to conv
On Sunday 14 April 2013 07:26:26 Peter Stuge wrote:
> Michał Górny wrote:
> > > > Any thoughts?
> > >
> > > If doing this at all I think it should take an -r option to enable
> > > the new recursion, for symmetry with the do* functions and for
> > > backwards compatibility.
> >
> > Backwards comp
Michał Górny wrote:
> > > Any thoughts?
> >
> > If doing this at all I think it should take an -r option to enable
> > the new recursion, for symmetry with the do* functions and for
> > backwards compatibility.
>
> Backwards compatibility with what?
With the old non-recursive behavior of edos2un
On Sun, 14 Apr 2013 12:37:05 +0200
Peter Stuge wrote:
> Michał Górny wrote:
> > Any thoughts?
>
> If doing this at all I think it should take an -r option to enable
> the new recursion, for symmetry with the do* functions and for
> backwards compatibility.
Backwards compatibility with what?
--
Michał Górny wrote:
> Any thoughts?
If doing this at all I think it should take an -r option to enable
the new recursion, for symmetry with the do* functions and for
backwards compatibility.
//Peter
On Sat, Apr 13, 2013 at 10:44 AM, Michał Górny wrote:
> The edos2unix is quite useful when handling DOS-sourced packages.
> But since it's a bash function, you can't reasonably use it from within
> find invocation. And often you hit packages which are all flooded with
> CRLFs that you need to conv
The edos2unix is quite useful when handling DOS-sourced packages.
But since it's a bash function, you can't reasonably use it from within
find invocation. And often you hit packages which are all flooded with
CRLFs that you need to convert.
That's why I'm suggesting to make edos2unix recursive. Th
