On 3/23/21 4:46 AM, Andreas Schwab wrote:
> On Mär 22 2021, Dale R. Worley wrote:
>
>> Greg Wooledge writes:
>>> Partly true. seq(1) is a Linux thing, and was never part of any
>>> tradition, until Linux people started doing it.
>>
>> Huh. I started with Ultrix, and then SunOS, but don't
Andreas Schwab writes:
>> I've never tracked down why, but the Perl executable is a lot smaller
>> than the Bash executable.
>
> Is it?
>
> $ size /usr/bin/perl /bin/bash
>textdata bss dec hex filename
> 2068661 27364 648 2096673 1ffe21 /usr/bin/perl
> 1056850 22188
Eduardo Bustamante writes:
> The summary is that SSH is reading from the same file descriptor as
> "read". Use '-n' (or redirect SSH's stdin from /dev/null) to prevent
> this.
Oh, yeah, I've been bitten by that one many times.
Another solution, though more awkward, is feeding the data for read
L A Walsh writes:
> It would be nice to have a expansion that preserves arg boundaries
> but that expands to nothing when there are 0 parameters
> (because whatever gets called still sees "" as a parameter)
Fiddling a bit, I found this is a nice way to show how "$@" (or any
other construction)
On 3/24/21 3:49 PM, Ilkka Virta wrote:
> On Wed, Mar 24, 2021 at 9:38 PM L A Walsh wrote:
>
>> Hmmm...Now that I try to show an example, I'm not getting
>> the same results. Grrr. Darn Heizenbugs.
>>
>
> Just remember that if you test with printf, it always prints at least once,
> which
On Wed, Mar 24, 2021 at 2:22 PM gregrwm wrote:
>
> Configuration Information [Automatically generated, do not change]:
> Machine: x86_64
> OS: linux-gnu
> Compiler: gcc
> Compilation CFLAGS: -g -O2 -Wno-parentheses -Wno-format-security
> uname output: Linux ginger 4.18.0-240.15.1.el8_3.x86_64 #1
> On Mar 24, 2021, at 5:21 PM, gregrwm wrote:
>
> Oddly, somehow, invoking ssh in a loop causes the loop to preterminate.
> Why?
https://mywiki.wooledge.org/BashFAQ/089
vq
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -g -O2 -Wno-parentheses -Wno-format-security
uname output: Linux ginger 4.18.0-240.15.1.el8_3.x86_64 #1 SMP Mon Mar 1
17:16:16 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
On Wed, Mar 24, 2021 at 9:38 PM L A Walsh wrote:
> Hmmm...Now that I try to show an example, I'm not getting
> the same results. Grrr. Darn Heizenbugs.
>
Just remember that if you test with printf, it always prints at least once,
which makes it look exactly as if it got an empty string
On 2021/03/23 21:41, Lawrence Velázquez wrote:
On Mar 23, 2021, at 11:43 PM, Eli Schwartz wrote:
It's not clear to me, how you expect this to differ from the existing
behavior of "$@" or "${arr[@]}" which already expands to
rather than an actual "" parameter.
The original message
Date:Wed, 24 Mar 2021 11:15:11 +0300
From:=?UTF-8?B?T8SfdXo=?=
Message-ID:
| I think I got the general idea of aliases now
I'm not sure why you want or need that, aliases
are dumb (bizarre) and shoukd be deleted...
I keep trying to get tge POSIX people to
24 Mart 2021 Çarşamba tarihinde Robert Elz yazdı:
>
> At least in the NetBSD sh, as soon as the \n that comes from the
> expanded P2B is seen, the shell switches to heredoc input reading,
> which doesn't read tokens at all, just lines until the end delimiter
> is seen. There's absolutely no
12 matches
Mail list logo
