Sorry for splitting a message into two.
On Wed, Nov 30, 2016 at 07:34:25AM +0500, Mihail Konev wrote:
> On Tue, Nov 29, 2016 at 10:02:08AM -0500, Greg Wooledge wrote:
> > On Tue, Nov 29, 2016 at 02:14:11PM +0500, Mihail Konev wrote:
> > > > Buggy (replace the ^-sequences in the second line):
> >
On Tue, Nov 29, 2016 at 10:02:08AM -0500, Greg Wooledge wrote:
> On Tue, Nov 29, 2016 at 02:14:11PM +0500, Mihail Konev wrote:
> > > Buggy (replace the ^-sequences in the second line):
> > > PS1="[\${PWD##*/}]\$ " # set the prompt
> > > PS1="^[]0;\$PWD^G^M$PS1"# set the window title
> > >
Bash Version: 4.4
Release Status: release
Description:
I attempted a comprehensive review of Readline command documentation,
similar to what I did for Readline variables earlier this year. Thank
you for incorporating so many fixes into Bash 4.4.
* emacs-editing-mode: is documented in
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: cygwin
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash.exe' -DCONF_HOSTTYPE='x86_64'
-DCONF_OSTYPE='cygwin' -DCONF_MACHTYPE='x86_64-unknown-cygwin'
-DCONF_VENDOR='unknown' -DLOCALEDIR='/usr/share/locale'
On 11/26/16 1:01 PM, L A Walsh wrote:
> But this didn't (misspelling of hash name):
>
>> if [[ ${requirs[xxx]:-} ]]; then echo ok; else echo not; fi
> bash: xxx: unbound variable
>
> Shouldn't it have said:
>
> bash: requirs: unbound variable?
No. Bash performs array referencing `inside
On 11/29/16 1:32 AM, Pas wrote:
> Hello,
>
> Thank you for the very fast reply, though I'd like to shamelessly ask
> for more bits of your time.
>
> I've strace'd all the involved processes (as far as I know), and all
> were just getting the SIGTTINs, no one was sending SIGCONTs (
>
On 11/27/16 5:07 AM, Otenba wrote:
> Bash Version: 4.4
> Patch Level: 5
> Release Status: release
>
> Description:
> Performing variable indirection using an empty value causes an error. It
> didn't in Bash 4.3.
It's pretty clear that indirect expansion that attempts to reference
through an
On Tue, Nov 29, 2016 at 02:14:11PM +0500, Mihail Konev wrote:
> > Buggy (replace the ^-sequences in the second line):
> > PS1="[\${PWD##*/}]\$ " # set the prompt
> > PS1="^[]0;\$PWD^G^M$PS1"# set the window title
> >
>
> Turns out this was the only one buggy.
> So it was all the (mis-)
Hello,
Thank you for the very fast reply, though I'd like to shamelessly ask
for more bits of your time.
I've strace'd all the involved processes (as far as I know), and all
were just getting the SIGTTINs, no one was sending SIGCONTs (
http://i.imgur.com/n5bUQVM.png - 25799 a bash process, and
On Tue, Nov 29, 2016 at 01:27:26PM +0500, Mihail Konev wrote:
> Buggy:
> PS1='\[\e]0;\w\a\]\n\[\e[32m\]\u@\h \[\e[35m\]$MSYSTEM\[\e[0m\]
> \[\e[33m\]\w\[\e[0m\]\n\$ '
>
Not a buggy one.
It does not trigger the bug.
> Buggy (replace the ^-sequences in the second line):
> PS1="[\${PWD##*/}]\$ "
On Tue, Nov 29, 2016 at 08:27:00AM +0500, Mihail Konev wrote:
> Msys2 on windows, at least, should do it without a problem.
Tried both it (bash 4.3.46) and arch linux in qemu (bash 4.3.46).
Neither reproduced.
Nevertheless, MSYS2 was exhibiting the bug all the time, most likely,
with bash
On Tue, Nov 29, 2016 at 12:47:26PM +0500, Mihail Konev wrote:
> On Tue, Nov 29, 2016 at 08:27:00AM +0500, Mihail Konev wrote:
> > Msys2 on windows, at least, should do it without a problem.
>
> Tried both it (bash 4.3.46) and arch linux in qemu (bash 4.3.46).
> Neither reproduced.
>
>
On 29/11/16 05:41, Robert Durkacz wrote:
> make has survived all this time but it is not very well accepted today
> with a lot of competing build systems trying to do better. bash is
> very secure and moreover the Bourne shell was there first. make is
> falling out of favour as far as I can see
13 matches
Mail list logo
