When I go for auto complete now, the filenames no longer line up:
Ishtar:/suse132 ls e17-
e17-0.17.6-2.1.10.x86_64.rpm
e17-branding-openSUSE-0.1-10.1.
2.x86_64.rpm e17-branding-upstream-0.17.6-2.1.10.x86_64.rpm
e17-devel-0.1
7.6-2.1.10.x86_64.rpm
Configuration Information:
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/local/share/locale' -DPACKAGE='bash'
-DSHELL
Chet Ramey wrote:
On 7/12/15 11:58 PM, Linda Walsh wrote:
set -A hash
This is an error
---
a brain-o -- at least I got the capitalized-A ;-)
(original code probably had a
hash hash
or
map hash
)
declare -A hash...
(I rarely type out the full command due to my aliases
and
On 14/07/15 06:49, Dmitry Bogatov wrote:
Guile is for situations, when script is mainly calls other programs,
but still needs moderately complex logic of text manipulation,
compraison and mapping. Recently I wrote script, that had to emulate
map(data structure). Well, I would prefer that is
On Tue, Jul 14, 2015 at 11:13 AM, Charles Daffern seejay...@gmail.com
wrote:
On 14/07/15 06:49, Dmitry Bogatov wrote:
Guile is for situations, when script is mainly calls other programs,
but still needs moderately complex logic of text manipulation,
compraison and mapping. Recently I wrote
On 14 Jul 2015 11:35, Pierre Gaston wrote:
I think adoption would be difficult considering even a useful loadable
builtin like finfo has not found its way into default installations, but
for instance I can imagine bash programmable completion could go another
level with an embedded interpreter
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 7/13/15 4:46 PM, Dmitry Bogatov wrote:
Hello, bug-bash and personally maintainer Chet Ramsey.
Would you be interested in following patches?
* GNU Guile integration (built-in that outputs value of Guile procedure
call, similar to what
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 7/14/15 8:22 AM, Chet Ramey wrote:
On 7/14/15 2:33 AM, Mike Frysinger wrote:
running it with set -x shows that it runs the xgcc rm steps, but
that's
it.
using strace shows xgcc and rm both exit(0), but for some reason
bash doe
s
not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 7/14/15 2:33 AM, Mike Frysinger wrote:
running it with set -x shows that it runs the xgcc rm steps, but that's
it.
using strace shows xgcc and rm both exit(0), but for some reason bash doe
s
not continue to the following commands like it
On 7/14/15 3:25 AM, Linda Walsh wrote:
When I go for auto complete now, the filenames no longer line up:
Ishtar:/suse132 ls e17-
e17-0.17.6-2.1.10.x86_64.rpm
e17-branding-openSUSE-0.1-10.1.
2.x86_64.rpm e17-branding-upstream-0.17.6-2.1.10.x86_64.rpm
e17-devel-0.1
Chet Ramey wrote:
Am still on 4.2, but in the bashdir, I get:
reset ... ^L
Erase is control-H (^H).
Kill is control-X (^X).
Ishtar:law hhsfshsdfhl^C
Ishtar:law bind
Ishtar:law cd ../tools/bash/bash-4.3
Ishtar:tools/bash/bash-4.3 ls bcomplete
bash*bashintl.h bashversion*
11 matches
Mail list logo
