From: Alain BROSSARD <abross...@reyl.com> | I did think about the case to parse the output, but this means that you | already know that the problem is triggered by calling an external program.
I think there is some miscommunication going on here. The message I sent had nothing to do with the original problem reported (which as I said, seemed to already be understood, with solutions available), but just to this statement from you in an earlier message: | it is extremely difficult to check whether -a is set | or not without using an external command. which is simply incorrect. In fact, I cannot imagine a case where one would use an external command to determine if -a is set or not, assuming one had a need to do that. The method I gave using case (there are other ways, but they're uglier) was purely for that purpose, to determine whether or not -a is set. The code to be filled in was for whatever you wanted to do (maybe just set a variable to true or false or something, but it could be anything) once you have discovered the state of the -a option. kre
