Zitat von Chet Ramey <[EMAIL PROTECTED]>:
> Actually, I am discouraged that applications were not written to use the
> portable `printf'. Use of `echo' in portable applications has been
> deprecated for years.
>
> It's hindsight, of course, but had mc been written (or modified later)
> to use pri
Jochen Roderburg wrote:
> Indeed there it is. Actually, I did not suspect a changelog in a directory
> named
> CWRU and had not looked there ;-)
Sorry. It's always been there.
> Let's see, if I understood it correct now: To adhere to the above mentioned
> standards you no longer allow octal d
Eric Blake <[EMAIL PROTECTED]> wrote:
> According to Chet Ramey on 10/21/2006 11:52 AM:
>> Jochen Roderburg wrote:
>>>
>>> I finally tracked this down to a changed behaviour of the builtin echo
>>> command.
>>>
>>> Namely, the formecho -e '\nnn' with a 3-digit octal number does not
>>> work
Zitat von Chet Ramey <[EMAIL PROTECTED]>:
> Jochen Roderburg wrote:
> > Namely, the formecho -e '\nnn' with a 3-digit octal number does not
> work
> > any longer, only the variant echo -e '\0nnn' with a leading zero.
> >
> > Don't know it this is a bug or feature ;-)
>
> It's intentional.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[Adding bug-coreutils to CC]
According to Chet Ramey on 10/21/2006 11:52 AM:
> Jochen Roderburg wrote:
>>
>> I finally tracked this down to a changed behaviour of the builtin echo
>> command.
>>
>> Namely, the formecho -e '\nnn' with a 3-digit
Jochen Roderburg wrote:
> I found a problem under Linux with the 'Midnight Commander' (v 4.5.55) and the
> new bash 3.2.
> Chdirs in subshells do not work with the effects:
> 1) On every directory change in mc you get a warning 'Could not change
> directory
> ...'
>mostly corrupting the mc pro
I found a problem under Linux with the 'Midnight Commander' (v 4.5.55) and the
new bash 3.2.
Chdirs in subshells do not work with the effects:
1) On every directory change in mc you get a warning 'Could not change directory
...'
mostly corrupting the mc program window.
2) It is not possible to
