Philip wrote:
> Hi! Short question this time..
>
> $ echo '-e'
> does not print -e
>
> $ echo '-e '
> does print -e .
By the way, neither -e nor -E are explained in the option section of
„help echo“. Only -n is mentioned there.
GNU bash, Version 4.2.10(1)-release (x86_64-suse-linux-gnu)
On Mon, Jan 23, 2012 at 11:47 AM, Ralf Goertz
wrote:
> Philip wrote:
>
>> Hi! Short question this time..
>>
>> $ echo '-e'
>> does not print -e
>>
>> $ echo '-e '
>> does print -e .
>
> By the way, neither -e nor -E are explained in the option section of
> „help echo“. Only -n is mentioned there.
Pierre Gaston writes:
> On Mon, Jan 23, 2012 at 11:47 AM, Ralf Goertz
> wrote:
>> Philip wrote:
>>
>>> Hi! Short question this time..
>>>
>>> $ echo '-e'
>>> does not print -e
>>>
>>> $ echo '-e '
>>> does print -e .
>>
>> By the way, neither -e nor -E are explained in the option section of
>> „
> On Sun, Jan 22, 2012 at 04:52:06PM -0500, Chet Ramey wrote:
>On 1/22/12 7:35 AM, Roger wrote:
>>> On Sat, Jan 21, 2012 at 09:17:32PM -0500, Chet Ramey wrote:
>>>
>>> I could look at putting in some sort of inter-character timeout, but I
>>> don't know yet how well the code structure lends itself
On Mon, Jan 23, 2012 at 08:52:17AM EST, Roger wrote:
[..]
> Matter of fact, I'm starting to find VIM's long wait time length
> a little annoying. ;-)
:h tm
:h ttm
CJ
Hi,
after the following fragment of code named variable gets empty:
ls | while read file ; do
v=1
break
done
echo $v
Is it a bug or a feature?
GNU bash, version 4.1.2(1)-release
Denis
On Mon, Jan 23, 2012 at 2:58 PM, Denis Melnikov wrote:
> Hi,
> after the following fragment of code named variable gets empty:
>
> ls | while read file ; do
> v=1
> break
> done
> echo $v
>
> Is it a bug or a feature?
> GNU bash, version 4.1.2(1)-release
>
> Denis
>
Pipelines create subshells.
On 1/23/12 8:52 AM, Roger wrote:
> A little more indepth examination, and I can see VIM's wait is approximately
> double of what the readline patch's wait time is. However, I think the
> shorter
> wait time is more functional as when typing a double char, it in no way takes
> as long as VIM's
On 1/23/12 2:58 PM, Denis Melnikov wrote:
> Hi,
> after the following fragment of code named variable gets empty:
>
> ls | while read file ; do
> v=1
> break
> done
> echo $v
>
> Is it a bug or a feature?
> GNU bash, version 4.1.2(1)-release
All components of a pipeline generally run in sepa
> On Mon, Jan 23, 2012 at 04:52:17AM -0900, Roger wrote:
>> On Sun, Jan 22, 2012 at 04:52:06PM -0500, Chet Ramey wrote:
>>On 1/22/12 7:35 AM, Roger wrote:
On Sat, Jan 21, 2012 at 09:17:32PM -0500, Chet Ramey wrote:
I could look at putting in some sort of inter-character timeout, but
On 1/23/12 1:12 AM, Jonathan Andrews wrote:
> I needed a statically linked bash for testing an arm board. I did not
> expect it to be nearly 3MB though ! It surprises me that a statically
> linked bash is bigger than the entire busybox binary i've compiled, or
> my kernel image for that matter. Is
On Mon, 2012-01-23 at 20:30 -0500, Chet Ramey wrote:
> On 1/23/12 1:12 AM, Jonathan Andrews wrote:
>
> > I needed a statically linked bash for testing an arm board. I did not
> > expect it to be nearly 3MB though ! It surprises me that a statically
> > linked bash is bigger than the entire busybox
12 matches
Mail list logo