On 02/06/2018 11:04 AM, enh wrote:
>> So when I say "a proper bash replacement" I'm _mostly_ targeting bash
>> 2.x with proper utf8 and the occasional new feature like ~= (regex
>> matches) that are easy to do. Stuff like <(command) and file{1,2}.txt
>> are over 20 years old.
>
> <(command) isn't
On Tue, Feb 6, 2018 at 8:45 AM, Rob Landley wrote:
> On 02/05/2018 09:41 PM, Robert Thompson wrote:
>> Yeah, I ran into some similar issues years ago... In my case, I got
>> burned into learning not to assume that bash (or any other shell) is
>> correct, or even necessarily *self* consistent(eve
On 02/05/2018 09:41 PM, Robert Thompson wrote:
> Yeah, I ran into some similar issues years ago... In my case, I got
> burned into learning not to assume that bash (or any other shell) is
> correct, or even necessarily *self* consistent(even on linux), so I
> tend to reflexively do differential c