On 6/22/20 9:26 PM, Godmar Back wrote:
> In any event, this was very illuminating - though I have one last
> question: why did you not implement it?
It's not a requirement. The text you quoted is from the rationale, and
there is no corresponding text in the normative portion of the standard.
It's
I do:
set output
echo ">$1<"
>output<
output=""printf ${1:+-v $1} "%s:%s" 23 myproc
-Bash: printf: ` output': not a valid identifier
for some reason it is regarding the space before $1 in
the printf as part of the variable name.
It doesn't seem to do this on linux (lnx 4.4.12(3), cyg-4.4.12
On Tue, Jun 23, 2020 at 12:21:24PM -0700, L A Walsh wrote:
> set output
> output=""printf ${1:+-v $1} "%s:%s" 23 myproc
> -Bash: printf: ` output': not a valid identifier
Your command is simply wrong. You've got two double-quotes in a row,
which simply cancel each other out, as they contain only
The 'stat(2)' system call returns an optimal i/o size for files since some
files in addition to being on disks with a 4k sector size (making 128bytes
a slow choice for reads, and a real slow choice for writes), also can be on
a RAID with it's own optimal i/o size.
I think the 'stat(1)' prog shows
there was a linefeed in my source between output="" and the printf.
It's a gmail feature to mangle your input.
On Tue, Jun 23, 2020 at 12:30 PM Greg Wooledge wrote:
> On Tue, Jun 23, 2020 at 12:21:24PM -0700, L A Walsh wrote:
> > set output
> > output=""printf ${1:+-v $1} "%s:%s" 23 myproc
> >
It's a gmail feature to mangle your input in weird ways when you cut/paste.
the line with 'output=""' is separate from the "printf" line. Sorry.
On Tue, Jun 23, 2020 at 12:30 PM Greg Wooledge wrote:
> On Tue, Jun 23, 2020 at 12:21:24PM -0700, L A Walsh wrote:
> > set output
> > output=""print
On Tue, Jun 23, 2020 at 12:33:23PM -0700, L A Walsh wrote:
> It's a gmail feature to mangle your input in weird ways when you cut/paste.
> the line with 'output=""' is separate from the "printf" line. Sorry.
First, stop top-quoting.
Second, if you know that gmail is horrible and is going to mang
On 6/23/20 3:33 PM, L A Walsh wrote:
> On Tue, Jun 23, 2020 at 12:30 PM Greg Wooledge wrote:
>
>> On Tue, Jun 23, 2020 at 12:21:24PM -0700, L A Walsh wrote:
>>> set output
>>> output=""printf ${1:+-v $1} "%s:%s" 23 myproc
>>> -Bash: printf: ` output': not a valid identifier
>>
>> Your command is
On 6/23/20 3:21 PM, L A Walsh wrote:
> I do:
>
> set output
> echo ">$1<"
>> output<
> output=""printf ${1:+-v $1} "%s:%s" 23 myproc
>
>
>
> -Bash: printf: ` output': not a valid identifier
It looks like word splitting on the result of ${1:+-v $1} isn't taking
place. That might be due to IFS;
re: IFS... yup. that was it, not sure how it got cleared, but it did.
Thanks for the clue.
As for gmailnecessity creates unfortunate circumstances...having your
main file system (RAID 0) fail, along with your backups (in a separate disk
enclosure, also RAID 0), isn't something that happens ev
10 matches
Mail list logo
