Eric Blake wrote:
On 06/07/2012 03:22 PM, Linda Walsh wrote:
This isn't a matter of preference... its a real bug.
Ex:
$ ls $HOME/bin
"ls: cannot access $HOME/bin: No such file or directory"
Yes, we know. Ergo patch 29:
According to the the referred to discussion on this
issu
On 06/07/2012 03:22 PM, Linda Walsh wrote:
> This isn't a matter of preference... its a real bug.
>
> Ex:
> $ ls $HOME/bin
> "ls: cannot access $HOME/bin: No such file or directory"
Yes, we know. Ergo patch 29:
https://lists.gnu.org/archive/html/bug-bash/2012-05/msg00148.html
--
Eric Blake
Clark WANG wrote:
On Mon, May 28, 2012 at 11:32 PM, John E. Malmberg wrote:
Actual results:
ls \$HOME/
Already discussed for quite a few times. :) For example:
http://lists.gnu.org/archive/html/bug-bash/2011-12/msg00079.html
(patched attached)
http://lists.gnu.org/archive/html/bug-bash/201
On Thu, Jun 7, 2012 at 1:01 AM, Pierre Gaston wrote:
> Fwiw here is a robust and simple solution for in_:
>
> _in () {
> local e t
> t="${2:?}[@]";
> for e in "${!t}"; do [[ $1 = "$e" ]] && return 0;done
> return 1;
> }
>
>
The following won't have a name space collision with the 'e' variable
On 6/6/12 8:22 AM, John E. Malmberg wrote:
> The existing port of Bash for VMS claims to be 1.4.8, which as near as I
> can tell must be based on 1.4.7, as I do not see a 1.4.8 in the download
> section.
>
> What they did to work around that VMS does not have a fork() call, is to:
>
> Make a
On 6/4/12 12:42 PM, Davide Brini wrote:
> Bash Version: 4.2
> Patch Level: 29
> Release Status: release
>
> Description:
> To insert them in the history, bash converts multiline commands into a
> single line, normally replacing newlines with semicolons. However, if the
> multiline command
On Thu, Jun 7, 2012 at 12:27 PM, Dan Douglas wrote:
> On Thursday, June 07, 2012 10:01:51 AM Pierre Gaston wrote:
>> On Thu, Jun 7, 2012 at 6:07 AM, Linda Walsh wrote:
>> >(no I haven't made it space/bracket...whatever proof...just a bit
>> > more work)
>>
>> It's not just "a bit more work", ther
On Thursday, June 07, 2012 10:01:51 AM Pierre Gaston wrote:
> On Thu, Jun 7, 2012 at 6:07 AM, Linda Walsh wrote:
> >(no I haven't made it space/bracket...whatever proof...just a bit
> > more work)
>
> It's not just "a bit more work", there are many workarounds but it's not
> really possible to ma
On Thu, Jun 7, 2012 at 6:07 AM, Linda Walsh wrote:
>(no I haven't made it space/bracket...whatever proof...just a bit
> more work)
It's not just "a bit more work", there are many workarounds but it's not
really possible to make a really robust generic solution for assignment,
and in the end it ju
