Re: backward-kill-word is not refreshing correctly
m...@ice.filescope.com wrote: > Configuration Information [Automatically generated, do not change]: > Machine: i686 > OS: linux-gnu > Compiler: i686-pc-linux-gnu-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='bash' -DSHELL > -DHAVE_CONFIG_H -I. -I. -I./include -I./lib > -DDEFAULT_PATH_VALUE='/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin' > -DSTANDARD_UTILS_PATH='/bin:/usr/bin:/sbin:/usr/sbin' > -DSYS_BASHRC='/etc/bash/bashrc' -DSYS_BASH_LOGOUT='/etc/bash/bash_logout' > -DNON_INTERACTIVE_LOGIN_SHELLS -DSSH_SOURCE_BASHRC -march=pentium4 -O2 -pipe > uname output: Linux ice.filescope.com 2.6.25.10 #5 PREEMPT Thu Nov 27 > 16:10:07 EST 2008 i686 Intel(R) Pentium(R) 4 CPU 1400MHz GenuineIntel > GNU/Linux > Machine Type: i686-pc-linux-gnu > > Bash Version: 4.0 > Patch Level: 10 > Release Status: release > > Description: > When I type a long string of text and start pressing ctrl-W to > backwards-kill words, bash deletes the words but doesn't visually refresh > (the words still appear on the command line). This was not occurring for me > in the 3.x series of Bash. I can't reproduce this. I wonder if it's just latency on the machine. -- ``The lyf so short, the craft so long to lerne.'' - Chaucer Chet Ramey, ITS, CWRUc...@case.eduhttp://cnswww.cns.cwru.edu/~chet/
"declare -c" not documented
The -c option for declare (new in bash 4.0) is not mentioned in either the man page or the "help declare" text.
Re: "declare -c" not documented
Greg Wooledge wrote: > The -c option for declare (new in bash 4.0) is not mentioned in either > the man page or the "help declare" text. Correct. I'm not sure the capitalization feature will survive. If it makes it into the next version, I will add the documentation. -- ``The lyf so short, the craft so long to lerne.'' - Chaucer Chet Ramey, ITS, CWRUc...@case.eduhttp://cnswww.cns.cwru.edu/~chet/
I really mean to go to EOF
You know those pesky error messages, nurdsome: line 17: warning: here-document at line 1 delimited by end-of-file (wanted `EOF') Well there should be a new 'trick': <<$EOF, <<\$EOF, or something, the meaning of which is 'I really mean to go all the way to the end of the file'. This is in addition to the usual ways to disable seeing such warnings. Ah, missing since the birth of /bin/sh. OK, never mind.
tab completion of an invalid start spring causes memory fault in bash 3.2pl39
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? From: dgets...@mywork.net To: bug-bash@gnu.org,b...@packages.debian.org Subject: Bash 3.2 dies upon flood of tab-completion requests for invalid start string 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' -DPACKAGE='bash' - DSHELL -DHAVE_CONFIG_H -I. -I../bash -I../bash/include -I../bash/ lib -g -O2 -Wall uname output: Linux dgetsmanlinux 2.6.27-14-generic #1 SMP Fri Mar 13 18:00:20 UTC 2009 i686 GNU/Linux Machine Type: i486-pc-linux-gnu Bash Version: 3.2 Patch Level: 39 Release Status: release Description: Bash has a memory fault when overrun with tab-completion requests for a starting string that does not exist in the particular tree referenced. Repeat-By: I originally duplicated this problem on the host machine that I first saw it on by laying on the tab key for a null string after the root directory // was typed where was an NFS mounted fs. After I noted this behavior was reproducible my cow orker duplicated it on his workstation; both of these machines are Ubuntu 8 machines, one being 8.04 and one 8.10. Here is a cut 'n paste of the actual output of the bug in the wild: ---BEGIN PASTE--- Linux yyy 2.6.24-23-server #1 SMP Thu Nov 27 18:45:02 UTC 2008 x86_64 The programs included with the Ubuntu system are free software; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright. Ubuntu comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. To access official Ubuntu documentation, please visit: http://help.ubuntu.com/ Last login: Thu Mar 19 11:14:15 2009 from 192.168.1.30 dgets...@yyy:~$ ls /backup/zzz malloc: ../bash/subst.c:4198: assertion botched realloc: start and end chunk sizes differ last command: jobs Aborting...Connection to vmware-bismarck-alpha closed. 11:11:02 Thu Mar 19 - Jobs: 0 - Cmd: 4 dgets...@xxx:~$ Display all 2707 possibilities? (y or n) ---END PASTE--- Note: I forgot to mention that this bug seems to transcend the differences between x86_64 and i386 as the original notation was found on Ubuntu 8.04 x86_64 server. Fix: No idea.
bash-4.0 filename completion
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 a After pressing TAB completion seems to stop working, pressing Ctrl-i (another bind for `complete') also doesn't work, using Alt+/ (bind for complete-filename) works. It happens with bash-4.0* but works ok in bash-3.2*. Completing file names with open single quotation (cat 'a) also does not work. (please keep my e-mail in To: or Cc:) -- Krzysiek Pawlik key id: 0xBC51 desktop-misc, java, apache, ppc, vim, kernel, python... signature.asc Description: OpenPGP digital signature
TIMEFORMAT bug
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' -DPACKAGE='bash' -DSHELL -DHAVE_CONFIG_H -I. -I../bash -I../bash/include -I../bash/lib -g -O2 -Wall uname output: Linux mmarkk-desktop 2.6.27-11-generic #1 SMP Thu Jan 29 19:24:39 UTC 2009 i686 GNU/Linux Machine Type: i486-pc-linux-gnu Bash Version: 3.2 Patch Level: 39 Release Status: release Description: TIMEFORMAT variable improperly handled Repeat-By: $ TIMEFORMAT='test'; time echo aaa aaa test (works OK, but:) $ TIMEFORMAT='test' time echo aaa outputs something like this: aaa 0.00user 0.00system 0:00.00elapsed 200%CPU (0avgtext+0avgdata 0maxresident)k 0inputs+0outputs (0major+198minor)pagefaults 0swaps ( it seems memory leak or undocumented features of the bash...) BASH 2.05 said: $ TIMEFORMAT=1 time echo q -bash: time: command not found
