On 09/28/2015 08:56 AM, Eric Blake wrote:
> On 09/28/2015 08:30 AM, Mikhail Usenko wrote:
>
>> But catching that bug (in upstream?) hasn't changed anything
>> at least on my installation:
>
> Okay, I can see the disappearing \r even on a binary mount, so it
> appears to be unrelated to the fix f
On 09/28/2015 10:48 AM, Mikhail Usenko wrote:
> On Mon, 28 Sep 2015 08:56:14 -0600
> Eric Blake <...> wrote:
>>
>> 'echo -n' and 'echo -e' are non-portable (even in bash; because I can
>> use 'shopt -s xpgecho' to get POSIX-mandated behavior). Use 'printf'
>> instead.
>>
>
> xpg_echo doesn't chan
On Mon, 28 Sep 2015 08:56:14 -0600
Eric Blake <...> wrote:
>
> 'echo -n' and 'echo -e' are non-portable (even in bash; because I can
> use 'shopt -s xpgecho' to get POSIX-mandated behavior). Use 'printf'
> instead.
>
xpg_echo doesn't change 'echo -ne' behavior
('echo -e' force backslash-escape
On 09/28/2015 09:04 AM, Tim Higgins wrote:
> Team
> When I run startx I get the following error.
> higginst@HigginsT-LT-W7 ~
> $ startx
>
And this is related to bash, how?
Please don't top-post or commandeer unrelated threads. If you have an
unrelated question, start a new thread.
>
>
> CON
On 09/28/2015 08:30 AM, Mikhail Usenko wrote:
> But catching that bug (in upstream?) hasn't changed anything
> at least on my installation:
Okay, so it sounds like your issue is separate.
>
> ---%<--%<---
> #! /bin/bash
> bash -version | head -n1
> echo
>
> sender()
> {
> echo -n '\r\n'
On Thu, 24 Sep 2015 15:10:25 -0600
Eric Blake <...> wrote:
> On 06/04/2015 03:51 AM, Mikhail Usenko wrote:
> > Eric Blake (cygwin) <...> wrote:
> >> 4.3.39-2
> >
> > Hello, Eric.
> > It has the same issue as in the previous version:
> > eating one \r from the odd numbered chains of the \r.
> >
>
On 06/04/2015 03:51 AM, Mikhail Usenko wrote:
> Eric Blake (cygwin) <...> wrote:
>> 4.3.39-2
>
> Hello, Eric.
> It has the same issue as in the previous version:
> eating one \r from the odd numbered chains of the \r.
>
Please try the (currently-experimental) 4.3.42-4, which should fix the
issue
On 06/04/2015 03:51 AM, Mikhail Usenko wrote:
> Eric Blake (cygwin) <...> wrote:
>> 4.3.39-2
>
> Hello, Eric.
> It has the same issue as in the previous version:
> eating one \r from the odd numbered chains of the \r.
Yes, I know there are still \r issues, although I appreciate the test
case as I
Eric Blake (cygwin) <...> wrote:
> 4.3.39-2
Hello, Eric.
It has the same issue as in the previous version:
eating one \r from the odd numbered chains of the \r.
bash-4.3.39-2
-
$ echo -ne "\r\n" | { read t; echo "$t"; } | od -tx1
000 0a
001
$ echo -ne "\r\r\n" | { read t; echo
A new release of bash, 4.3.39-2, has been uploaded and will soon reach a
mirror near you; leaving 4.3.33-1 as the previous version.
NEWS:
=
This is my second build of bash 4.3 for cygwin, incorporating several
new upstream official patches and working around a change in make 4.1
VPATH behavior
10 matches
Mail list logo
