Re: `test -R' not working

Le 01/03/2014 03:26, Chet Ramey a écrit : Thanks for the report. A line got dropped from a merge back during development. I've attached a patch that fixes this and one other problem with -R. Chet it works now. thank you.

Errors in commands containing UTF8 characters are printed with UTF8 byte expansion

When I accidentally type some nonexistent command containing UTF8 characters, an error has UTF8 characters expanded: $ ЫZZZ bash: $'\320\253ZZZ': command not found I think bash shouldn't discriminate against UTF8 characters in error messages, and shouldn't expand them. If some international use

Commands containing UTF8 characters mess up bash history

I manipulate with some files containing UTF8 characters. The only commands I run are these: ./some-cmd < ../some-dir/utf8-containing-file-name.txt vim ../some-dir/utf8-containing-file-name.txt After a while of running of such commands, and going back and forth in history and rerunning them, the

Re: Commands containing UTF8 characters mess up bash history

You could use the command "history -c" to clear the history in case this becomes a real issue. I don't have a real fix. Sent from my iPad > On Mar 1, 2014, at 1:23 PM, Yuri wrote: > > I manipulate with some files containing UTF8 characters. The only commands I > run are these: > ./some-cmd <

Re: Commands containing UTF8 characters mess up bash history

On 03/01/2014 14:07, Ryan Cunningham wrote: You could use the command "history -c" to clear the history in case this becomes a real issue. I don't have a real fix. The problem is that it comes back over and over again. Yuri

Re: Commands containing UTF8 characters mess up bash history

Then you might want to file a formal bug report using 'bashbug'. Reply with the bug report. In the meanwhile, reinstall Bash using these commands, to find out if the problem occurs upstream (if it doesn't, don't report it here): wget ftp://ftp.gnu.org/gnu/bash/bash-4.3.tar.gz tar -xzvf bash-4.3.

RFE: a way to echo the arguments with quoting

I have an ugly function I wrote for zsh that does this: Sat 14:17:25 ip2 yost /Users/yost 1 634 Z% echo-quoted xyz \$foo 'a b c ' '\n' xyz '$foo' 'a b c ' '\n' Sat 14:17:53 ip2 yost /Users/yost 0 635 Z% It would be nice if there were an easy way to do this in bash. Here is my use case: echo-c

Re: RFE: a way to echo the arguments with quoting

On Sat, Mar 01, 2014 at 02:34:56PM -0800, Dave Yost wrote: > I have an ugly function I wrote for zsh that does this: > > Sat 14:17:25 ip2 yost /Users/yost > 1 634 Z% echo-quoted xyz \$foo 'a b c ' '\n' > xyz '$foo' 'a b c ' '\n' > Sat 14:17:53 ip2 yost /Users/yost > 0 635 Z% > > It would be nic

typo in bash manual

In http://www.gnu.org/software/bash/manual/bashref.html#GNU-Parallel Where you say ls *.gz | parallel -j+0 "zcat {} | bzip2 >{.}.bz2 && rm {}" This will recompress all files in the current directory with names ending in .gz using bzip2, running one job per CPU (-j+0) in parallel. it should be ls

Re: typo in bash manual

Hmmm. That doesn't seem right. Actually, the original statement is correct. Sent from my iPad > On Mar 1, 2014, at 11:29 AM, Dave Yost wrote: > > In http://www.gnu.org/software/bash/manual/bashref.html#GNU-Parallel > > Where you say > ls *.gz | parallel -j+0 "zcat {} | bzip2 >{.}.bz2 && rm {}"

Re: typo in bash manual

On 2014-03-01 11:29:03 -0800, Dave Yost wrote: > In http://www.gnu.org/software/bash/manual/bashref.html#GNU-Parallel > > Where you say > ls *.gz | parallel -j+0 "zcat {} | bzip2 >{.}.bz2 && rm {}" > This will recompress all files in the current directory with names ending in > .gz using bzip2, r

Re: Commands containing UTF8 characters mess up bash history

To: bug-bash@gnu.org Subject: Commands containing UTF8 characters mess up bash history Configuration Information: Machine: amd64 OS: freebsd9.2 Compiler: clang Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='amd64' -DCONF_OSTYPE='freebsd9.2' -DCONF_MACHTYPE='amd64-portbld-freebsd9.2' -DC