Re: eval a=b\ c

2015-05-27 Thread Eduardo A . Bustamante López
On Wed, May 27, 2015 at 12:59:53AM -0700, Dave Yost wrote: > OK, I can make it to work in bash if I say > echodo a=b\\ c > but then zsh tries to execute c. Can’t win. > > The problem is: how do I write this function so that it can be invoked > identically in zsh and bash with identical results

Re: eval a=b\ c

2015-05-27 Thread Dave Yost
OK, I can make it to work in bash if I say echodo a=b\\ c but then zsh tries to execute c. Can’t win. The problem is: how do I write this function so that it can be invoked identically in zsh and bash with identical results of setting a variable to a value with a space in it? > On 2015-05-26,

AW: Feature request

2015-05-27 Thread Alexander.Elgert
Maybe you want to read my posting with the title: """bash functions with [\.-] function/method name parser""" It works pretty well, as long as you do not use dots or dashes in your function names. Unluckily, there was no response so far on the doxygen list. ;( Regards, Alexander On 5/14/

Re: [PATCH] Add EXECIGNORE

2015-05-27 Thread Chet Ramey
On 4/17/15 5:53 PM, Eric Blake wrote: > Based on an idea from Dan Colascione: > https://sourceware.org/ml/cygwin/2010-11/msg00022.html > > Usage: add this to your shell startup: > EXECIGNORE='*.so:*.so.*' > to cause TAB completion to ignore shared library files when crawling > the file system to

Re: unset does not act as expected on namerefs

2015-05-27 Thread Chet Ramey
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 5/26/15 5:02 PM, Shawn Wilson wrote: > On +2015/05/26 18:05:18, Geir Hauge wrote: >> On Tue, May 26, 2015 at 11:00:45AM -0500, Eduardo A. Bustamante López wr ote: >>> # Here we 'unset ref', which actually unsets 'var'. Then, we assign 'va r' to >>>

Re: unset does not act as expected on namerefs

2015-05-27 Thread Chet Ramey
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 5/26/15 10:31 AM, Shawn Wilson wrote: > swilson@swlap1:~/temp$ bash --version > GNU bash, version 4.3.11(1)-release (x86_64-pc-linux-gnu) > swilson@swlap1:~/temp$ cat t.txt > $ome text !n a file| > swilson@swlap1:~/temp$ unset t > swilson@swlap1:~/

Re: unset does not act as expected on namerefs

2015-05-27 Thread Greg Wooledge
On Tue, May 26, 2015 at 05:02:43PM -0400, Shawn Wilson wrote: > If there's no good reason to keep this as is (some use case where > this might be wanted and breaking backward compatibility - I can't > see anyone actually *wanting* it this way) shouldn't it be changed? > A behavior can be documented