Date: prev next · Thread: first prev next last


Hi,

Christian Lohmaier wrote on 2011-03-17 19.44:

Then please replace your ugly hack with this:

hehe, thanks, this looks much better. My script was really, well... don't tell anyone. :-) Yours works nearly like a charm, except one issue - it doesn't seem to limit the depth of scanning. I've forwarded you one example mail, where one subscription ID is added to the output... I don't know why, however. /*/* looks good to me, similar to the -mindepth 2 -maxdepth 2 I've added... maybe you have an idea what's wrong?

Apart from that: Thanks a bunch, your output is much nicer!

(in case you're curious: 2>/dev/null just because there is some
spurious "discus" file in /var/spool/mlmmj/sv.libreoffice.org - it
contains a number only, probably created by a bad script? - the output
doesn't hurt when piping stdout to the mail only, but it "pollutes"
console output otherwise :-)

Ooops... indeed, a bug. Removed it. Thanks for noticing!

Florian

--
Florian Effenberger <floeff@documentfoundation.org>
Steering Committee and Founding Member of The Document Foundation
Tel: +49 8341 99660880 | Mobile: +49 151 14424108
Skype: floeff | Twitter/Identi.ca: @floeff

--
E-mail to moderators+help@documentfoundation.org for instructions on how to unsubscribe
List archives are available at http://listarchives.documentfoundation.org/www/moderators/
All messages you send to this list will be publicly archived and cannot be deleted

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.