Configuration Information [Automatically generated, do not change]:
Machine: i486
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i486'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i486-pc-linux-gnu'
-DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale'
On Fri, Mar 20, 2009 at 8:36 AM, Марк Коренберг socketp...@gmail.com wrote:
Configuration Information [Automatically generated, do not change]:
Machine: i486
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i486'
-DCONF_OSTYPE='linux-gnu'
Damon Getsman wrote:
I think I just found a bug in the version of bash that ships with
Ubuntu 8.04 and 8.10; I've tested and reproduced it across x86_64 and
i386/i586 distributions as well as the server/desktop distributions.
Anybody else seen this in the wild?
This was previously reported
Krzysiek Pawlik wrote:
Hello,
With bash-4.0-10 I get following behavior:
$ touch 'a file with spaces'
$ touch 'a File with spaces'
$ touch 'a File With spaces'
$ cat aTAB
After pressing TAB completion seems to stop working, pressing Ctrl-i (another
bind for `complete') also doesn't
I'm trying to write a stack trace function and BASH_LINENO doesn't
make sense sometimes and doesn't appear too accurate at others.
Here's my test script:
shopt -s extdebug
trap 'backtrace' ERR
set -E
backtrace() {
echo FUNCNAME: ${funcna...@]}
echo BASH_SOURCE: ${bash_sour...@]}
http://sources.gentoo.org/viewcvs.py/*checkout*/portage/main/trunk/bin/isolated-
functions.sh?content-type=text%2Fplain
checkout the dump_trace() func at the top ... that might help. or it might
confuse. g'luck!
-mike
signature.asc
Description: This is a digitally signed message part.
Chet Ramey wrote:
I can't reproduce this. I get a\ (escaped space), and then listing of
possible completions with subsequent TABs. This is the correct behavior.
Could it have something to do with any completion functions you have
defined?
Yes, it does. When I tested without any completion
Krzysiek Pawlik wrote:
Chet Ramey wrote:
I can't reproduce this. I get a\ (escaped space), and then listing of
possible completions with subsequent TABs. This is the correct behavior.
Could it have something to do with any completion functions you have
defined?
Yes, it does. When I
Марк Коренберг wrote:
Configuration Information [Automatically generated, do not change]:
Machine: i486
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i486'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i486-pc-linux-gnu'
-DCONF_VENDOR='pc'
Chet Ramey wrote:
This might be the result of changes to the bash readline support function
that dequotes filenames. That function was changed as the result of bug
reports against bash-3.2 to better implement shell quoting. That means:
1. Backslashes should not be stripped within single
$ echo $BASH_VERSION
3.2.48(1)-release
$ echo $(fc -nl -1)
echo $BASH_VERSION
$ echo $BASH_VERSION
4.0.10(2)-release
$ echo $(fc -nl -1)
echo $(fc -nl -1)
I see there were a lot of changes to fc, is this intended or a bug?
It seems there is another way to get the last history entry that works
11 matches
Mail list logo