On Mittwoch, 5. September 2007 Aaron Stone wrote: > dbmail-sievecmd -u <username> -i [scriptname [filename]] > > I could write a line to stderr like "Please enter data for > <scriptname> on stdin" which would clue you in to what's happening > and give confirmation of the file name, in case it turns out to be > something unexpected.
Yes, that could help resolve the confusion. I guess others will run into the same sometimes, so it's better to write that info. Maybe only write that info if the script was called from command line, not from within another script? I don't know how to do that, though. Possibly only write that message if stdin has no input available? mfg zmi -- // Michael Monnerie, Ing.BSc ----- http://it-management.at // Tel: 0676/846 914 666 .network.your.ideas. // PGP Key: "curl -s http://zmi.at/zmi.asc | gpg --import" // Fingerprint: EA39 8918 EDFF 0A68 ACFB 11B7 BA2D 060F 1C6F E6B0 // Keyserver: www.keyserver.net Key-ID: 1C6FE6B0
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ DBmail mailing list [email protected] https://mailman.fastxs.nl/mailman/listinfo/dbmail
