Date: Wed, 18 Nov 2015 20:32:53 +0100 From: Lars Engels <lars.engels@0x20.net> To: Allan Jude <allanjude@freebsd.org> Cc: Garrett Cooper <yaneurabeya@gmail.com>, freebsd-current@freebsd.org Subject: Re: libXO-ification - Why - and is it a symptom of deeper issues? Message-ID: <20151118193252.GE27296@e-new.0x20.net> In-Reply-To: <5648CBA1.9010300@freebsd.org> References: <0650CA79-5711-44BF-AC3F-0C5C5B6E5BD9@rdsor.ro> <5648C964.2020405@freebsd.org> <2DF061E9-2541-4B10-9744-C49C515FF672@gmail.com> <5648CBA1.9010300@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--588wvpgrYaEESfyK Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Nov 15, 2015 at 01:14:57PM -0500, Allan Jude wrote: > You can setup an atexit() call to call xo_finish automatically when the > program exits. The original changes to uptime had a few other issues, > which I fixed. >=20 Is there a list of tools that can already output via libxo? Neither "uptime -h", nor its manpage or "apropros libxo" doesn't reveal anything. --588wvpgrYaEESfyK Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQF8BAEBCgBmBQJWTNJkXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ4RjQwMDE3RTRERjUzMTI1N0FGRTUxNDlF NTRDQjM3RDNBMDg5RDZEAAoJEOVMs306CJ1tUncH/RdKmJSpzyyw05tS1In5jiyN TwJ7HaVcCqXvdKPYIp/c4qDWmsn16rwSgwvb6CxVsFzqc8iBBOSKwNTb2fm27CTy PuKiDBL7WNPCvdxbNBTQMRJLHqbgjqQGvmrFsrcnpwntMHrJeFHL0fdfXa/EovTk 92uOMC2dxg5ynGPXp5+xD5woCVJ27TblC/ec87CS2eTeZsnyxWmMT3UV7ULSMVNI /gv0yzHC6FaIVmI3uyKWD2PtuLNO6VSWJo9jjBQS6/pNRjzzz8zaDBGupCe5banp 87ciOJKV7y6+HFsyi4nTiDCpXtYOtMA9b8Cs0TWHUaeV86anM4U3czECDJvB2tk= =kf+q -----END PGP SIGNATURE----- --588wvpgrYaEESfyK--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20151118193252.GE27296>