On 18/07/2019 14:12, Greg Wooledge wrote:
On Thu, Jul 18, 2019 at 10:58:52AM +0200, Henning wrote:
eval 'foo=(["key"]="'"${foo["key"]}"' value2")'
If you just want to work around the bug, why not do it in the simplest
way
On 18/07/2019 11:19, Andreas Schwab wrote:
On Jul 18 2019, Henning wrote:
eval 'foo=(["key"]="'"${foo["key"]}"' value2")'
This will break if ${foo["key"]} contains any of $ ` " \ .
Correct. I'd only taken blanks into account.
Henning
On 18/07/2019 03:16, Darren 'Tadgy' Austin wrote:
foo=(["key"]="${foo["key"]} value2")
using eval shoud also succeed, even for older bash:
eval 'foo=(["key"]="'"${foo["key"]}"' value2")'
Henning
On 25/05/2019 11:14, Henning wrote:
On 24/05/2019 17:16, Chet Ramey wrote:
That's not in the distributed version of bash-5.0. If you're applying an
older cygwin patch, have you tried just building the distributed version?
Let's make sure that works.
Bang! It does. So sorr
elf. Especially
as I have never used the 'igncr' stuff anyway. I hope there won't
appear ther Windows related issues.
I'm going to explore things now. And I have been waiting for
{previous,next}-screen-line and several other things.
Thanks a lot.
Henning
if (STREQ (option_name, o_options[i].name))
{
+#ifdef __CYGWIN__
+ if (o_options[i].interactive_only && avoid_interactive)
+ return EXECUTION_SUCCESS;
+#endif
if (o_options[i].letter == 0)
{
previous_option_value = GET_BINARY_O_OPTION_VALUE (i,
o_options[i].name);
@@ -588,7 +621,11 @@ parse_shellopts (value)
vptr = 0;
while (vname = extract_colon_unit (value, &vptr))
{
+#ifdef __CYGWIN__
+ set_minus_o_option_maybe (FLAG_ON, vname, !interactive_shell);
+#else
set_minus_o_option (FLAG_ON, vname);
+#endif
free (vname);
}
}
--
Several hunks applied, others could be applied manually. But the lines
where INTERACTIVE_ONLY was added, produced an error message like
expected } before INTERACTIVE_ONLY
All this is of course far beyond my knowledge and I wouldn't mind you
asking me to be patient and wait for cygwin ...
Thanks for your efforts
Henning
on Cygwin
Henning
On 22/05/2019 14:58, Koichi Murase wrote:
What still remains is the not working assignment of ^X.
Henning
Hi, I guess you are using Bash 4.4 because, according to my records,
bind -x '"\C-x": ...' after unbinding all the keyseqs causes segfaults
in Bash-3.0, 3.1 and 4.0-
rminal does not
produce like \eO[ABCDFH]
That seems to be wrong. Currently, the script works perfectly and the
time is acceptable.
What still remains is the not working assignment of ^X.
This inquiry would have been better suited for help-bash rather than
bug-bash.
Hmm. Yes (except for ^X)
Henning
essage: "... cannot find keymap for
command". What does that mean? Could you give an example that would
produce this error message?
Thank you.
Henning
On 20/05/2019 15:38, Chet Ramey wrote:
On 5/19/19 10:43 AM, Henning wrote:
I don't like to have dozens of key bindings I never use. Currently I
am issuing lots of lots of bind -r/-u commands to get rid of the
default bindings. This slows down console startup unnecessarily.
I would really
ntly explaining my intentions in my original
mail, and thanks for your prompt reply.
Henning
u all.
Or is there something undocumented for this purpose?
And yes, I know, it's soo dangerous.
Henning
I've noticed that this problem does no longer occur if bash 4.2.8 is
configured --with-bash-malloc. On my distribution (arch) bash is
configured --without-bash-malloc by default.
This is the configuration i use now (derived from the archlinux
pkgbuild):
./configure --prefix=/usr --with-curses --e
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-unknown-linux-gnu'
-DCONF_VENDOR='unknown' -DLOCALEDIR='/usr/share/local
t;POT-Creation-Date: 2009-12-30 08:25-0500\n"
-"PO-Revision-Date: 2009-09-14 20:37+0200\n"
-"Last-Translator: Nils Naumann \n"
+"PO-Revision-Date: 2010-09-07 12:03+0100\n"
+"Last-Translator: Henning Eggers \n"
"Language-Team: German \n"
"MIM
Configuration Information [Automatically generated, do not change]:
Machine: i686
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i686' -
DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i686-pc-linux-gnu' -
DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='ba
On Tue, 02.03.2010 um 15:41 +0530, Kalidas Yeturu wrote:
> Logically equivalent statements output different results. Suspect
> problem with 'pipe'.
>
This is not a bug, quoting man bash:
> Each command in a pipeline is executed as a separate process (i.e.,
> in a subshell).
http://mywiki.wooled
On Sun, Nov 15, 2009 at 08:31:38PM -0600, Peng Yu wrote:
> If I have the following in the command line,
>
> ~/.bash
>
> when I type , it will become /home/my_user_name/.bash
>
> I'm wondering if it is possible to configure bash command completion,
> so that it will still be '~/.bash'
>
Add
se
Configuration Information [Automatically generated, do not change]:
Machine: i686
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i686'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i686-pc-linux-gnu'
-DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='ba
this keyseq, it never 'gets through' to
bash unless you'd disable/change it for your terminal via stty.
So these keys aren't documented in man bash since they aren't part
of bash (or readline for that matter).
Regards,
Henning
Configuration Information [Automatically generated, do not change]:
Machine: i686
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i686'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i686-pc-linux-gnu'
-DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='ba
Chet Ramey wrote:
> Henning Bekel wrote:
>> Hello,
>> If I try to change READLINE_LINE and READLINE_POINT from a
>> function bound via bind -x, then setting READLINE_POINT is not
>> applied every second time I invoke the function. Instead, the
>> cursor
e this work
like readline's own editing functions (e.g. upcase-word) or macros
that edit the line without printing it again on a new line. But
maybe I just misinterpreted the purpose of this new feature. If
so, could you explain it's intended purpose?
Regards,
Henning
24 matches
Mail list logo