On 9/18/24 1:10 PM, Greg Wooledge wrote:
Thanks for the proposal. I think the [base#]n syntax is reasonable
here without adding a new shell option.
Do recall, however, that negative numbers break the workaround suggested
by Andreas.
$((10#${line:12:2}))
Not part of the original problem
On Wed, Sep 18, 2024 at 10:51:51 -0400, Chet Ramey wrote:
> On 9/17/24 7:50 PM, BRUCE FOWLER via Bug reports for the GNU Bourne Again
> SHell wrote:
> > An interesting problem I ran into recently:
> > I have a shell script that I run about once a month that
> > "screen-scrapes" from the output of a
On 9/17/24 7:50 PM, BRUCE FOWLER via Bug reports for the GNU Bourne Again
SHell wrote:
An interesting problem I ran into recently:
I have a shell script that I run about once a month that
"screen-scrapes" from the output of another program using the
substring capability, e.g. ${data_line:12:2
On Sep 17 2024, BRUCE FOWLER via Bug reports for the GNU Bourne Again SHell
wrote:
> of C-language compatibility. I could use the [base#]n form
> but that gets awkward.
Why is that awkward? It's a general solution to a general problem, and
does not require any new features.
> Even the venerabl
another is ${var##0}
On Wednesday, September 18, 2024, BRUCE FOWLER via Bug reports for the GNU
Bourne Again SHell wrote:
> An interesting problem I ran into recently:
>
> I have a shell script that I run about once a month that
> "screen-scrapes" from the output of another program using the
> s
An interesting problem I ran into recently:
I have a shell script that I run about once a month that
"screen-scrapes" from the output of another program using the
substring capability, e.g. ${data_line:12:2}. This is pulling
out the two-digit month ranging from "01" to "12".
This worked fine, e
