bash expanding relative paths in auto-complete

2015-08-13 Thread Linda Walsh
in bash 4.3.39, if I type a command, (like "."(source)) and a relative path like : ../conf, it expands the relative pathname to absolute pathnames. This is bad .. since I reuse relative commands in different absolute places. It didn't used to do this, and it's a potential security problem, since

Re: declare -f produces non eval'able output

2015-08-13 Thread Chet Ramey
On 8/13/15 12:06 PM, isabella parakiss wrote: > declare -f doesn't know that most keywords are valid function names: > > $ function time () { :; } > $ declare -f time > time () > { > : > } > > It should probably check if the name is if/for/time... before printing it. Thanks for the report.

Re: Bash ignores case when globbing with character ranges

2015-08-13 Thread Chet Ramey
On 8/13/15 1:36 PM, Greg Wooledge wrote: > However, bash does define a shopt called "globasciiranges" which > changes the behavior of [a-z] from locale-based to traditional US-ASCII. > You might want to try that, if you aren't willing to use the portable > syntax, or to dumb down your LC_* variabl

Re: Bash ignores case when globbing with character ranges

2015-08-13 Thread Greg Wooledge
On Thu, Aug 13, 2015 at 10:15:18AM -0400, g...@callahans.site wrote: > Description: > bash includes characters of wrong case when globbing with ranges > (i.e., [a-z]), after the first instance. The result of [a-z] in locales other than C or POSIX is implementation- defined. If you wan

Bash ignores case when globbing with character ranges

2015-08-13 Thread gwb
Configuration Information [Automatically generated, do not change]: Machine: x86_64 OS: linux-gnu Compiler: gcc -I/home/abuild/rpmbuild/BUILD/bash-4.2 -L/home/abuild/rpmbuild/BUILD/bash-4.2/../readline-6.2 Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64' -DCONF_OSTYPE='linux-gnu' -D

Re: Bash ignores case when globbing with character ranges

2015-08-13 Thread George Baltz
Never mind. Further investigation shows it's working as designed, and the (ir)rationale behind it. Sigh. Just when I thought EBCDIC was nothing but a distant, painful memory, it gets institutionalized. gwb

Bash ignores case when globbing with character ranges

2015-08-13 Thread George Baltz
Configuration Information [Automatically generated, do not change]: Machine: x86_64 OS: linux-gnu Compiler: gcc -I/home/abuild/rpmbuild/BUILD/bash-4.2 - L/home/abuild/rpmbuild/BUILD/bash-4.2/../readline-6.2 Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64' - DCONF_OSTYPE='linux-gnu' -D

declare -f produces non eval'able output

2015-08-13 Thread isabella parakiss
declare -f doesn't know that most keywords are valid function names: $ function time () { :; } $ declare -f time time () { : } It should probably check if the name is if/for/time... before printing it. --- xoxo iza

Re: problems with traps

2015-08-13 Thread Chet Ramey
On 8/12/15 9:55 PM, isabella parakiss wrote: > This segfaults when it receives a SIGUSR1: > > #!/bin/bash > trap ': $(:) < <(:)' USR1 > while :; do sleep 1; done Thanks for the report. The problem is the process substitution in the trap. I will fix it for the next version of bash. Chet -- ``

Re: -e does not take effects in subshell

2015-08-13 Thread Chet Ramey
On 8/13/15 1:35 AM, isabella parakiss wrote: > On 8/13/15, Eric Blake wrote: >> Like it or not, it is the historical behavior standardized by POSIX. It >> is NOT intuitive, and our advice is "DON'T USE set -e - IT WON'T DO WHAT >> YOU WANT". We can't change the behavior, because it would break sc