clemens fischer wrote:
> [...]
If you received several emails/posts, I apologize. This was a problem
with "news.eternal-september.org". My article was sent only once from
my box.
clemens
Greg Wooledge wrote:
> In this particular case, I would use a glob rather than an ERE,
> because "h?" is much simpler than "^h.$".
Besides, bash's extended globs provide everything ERE's provide. I use
the idiom:
shopt -s extglob
# for example, to check for numbers
case "-${somethin
Matthew Woehlke wrote:
>>> clemens fischer writes:
>>>
>>>> I have the following construct in a script:
>>>>
>>>> ... a number of commands
>>>> {
>>>> ... a number of commands
>>>> } 2>&1
Andreas Schwab wrote:
> clemens fischer writes:
>
>> I have the following construct in a script:
>>
>> ... a number of commands
>> {
>> ... a number of commands
>> } 2>&1 | ${prog_log} "${logfile}"
>>
>> It seems
'uname -rims'
Linux 2.6.31.1-spott i686 AuthenticAMD
'bash --version'
GNU bash, version 4.0.24(1)-release (i686-pc-linux-gnu)
I have the following construct in a script:
... a number of commands
{
... a number of commands
} 2>&1 | ${prog_log} "${logfile}"
It seems anything inside th
I have a script going through ELF files and finding which of them refer
to non-existing shared libraries. After finding the files, it proceeds
by checking which package they belong to, which is an expensive
operation, so it is done in a "coproc" co-process.
The main loop knows when all the files
