null output?

null output?

[William Lupton]

[-- Attachment #1: Type: text/plain, Size: 807 bytes --]

Hello,

When testing I find that I quite often don't care about the output (because
I care about filter output), so I often redirect stdout to /dev/null.

This is fine, but I wondered whether there could / should be (or indeed is)
a way of indicating that no output is desired. This might, for example, be
indicated via --to "" or --to null?

Worth it? Not worth it?

Thanks,
William

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/CAEe_xxii0b_gJSxY9ruh1pW_gXcNUp9wXn1_QPJjkupYnfzj8A%40mail.gmail.com.

[-- Attachment #2: Type: text/html, Size: 1247 bytes --]

Re: null output?

[Albert Krewinkel]

William Lupton <wlupton-QSt+ys/nuMyEUIsrzH9SikB+6BGkLq7r@public.gmane.org> writes:

> When testing I find that I quite often don't care about the output
> (because I care about filter output), so I often redirect stdout to
> /dev/null.
> This is fine, but I wondered whether there could / should be (or indeed
> is) a way of indicating that no output is desired. This might, for
> example, be indicated via --to "" or --to null?

I usually use `-o /dev/null` when developing Lua scripts: that will
discard the document, but preserves any `print` messages and warnings
that my scripts may produce.


-- 
Albert Krewinkel
GPG: 8eed e3e2 e8c5 6f18 81fe  e836 388d c0b2 1f63 1124