On 12/3/16 10:26 PM, Laur Aliste wrote:
> Hi,
> upgraded bash from
> GNU bash, version *4.3.30(1)-release* (x86_64-pc-linux-gnu)
> to *4.4.5(1)-release* and noticed the *readonly* array variables fail to be
> defined with init values.
This was changed as the result of a bug report from December, 2
Chet Ramey wrote:
The short answer is that colon is special to readline: it breaks words for
the readline completion code. If you want to complete filenames beginning
with a colon, either quote the colon or remove colon from
$COMP_WORDBREAKS.
If you're using bash-completion, it may have its own
Studio compiler may use things like '-xregs=no%frameptr' for example.
Thank you
--
Vlad
# Our compiler flags contain percent sign which get mixed up with percent sign
# seprators used by sed.
# Submitted to bug-bash@gnu.org
--- Makefile.in 2014-01-25 13:27:30.0 -0800
+++ Makefil
> > And second patch we use because of xpg-echo. Would it have sense to have
> > it included, or maybe stop the tests completely instead?
>
> You could just have turned off the xpg_echo option instead of going through
> a convoluted test (which just emulates `shopt -q') to determine whether or
> n
