On Wed, Mar 28, 2012 at 10:39 AM, Patrick Woolsey <pwool...@barebones.com> wrote: > At 10:20 -0600 03/28/2012, LuKreme wrote: >>On 28 Mar 2012, at 09:57 , Patrick Woolsey wrote: >>> [1. Please note that whatever options you set for 'tidy', you'll need to >>> redirect error output away from stderr, otherwise the combined output will >>> be directed to BBEdit's Unix Script Output window instead of replacing the >>> current document's contents.] >> >>Do you mean >> >>/usr/bin/tidy -f /dev/null -config /path/to/your/tidyconfig.txt 2> /dev/null >> >>or do you mean something else? > > > Sorry, I should've made that clearer. > > The command in my post does that redirection via '-f /dev/null' but if you > substitute your own options, you'll want to keep doing likewise. >
Is there a way to specify the Unix Script Output window for errors instead of /dev/null? I don't actually want to ignore the errors. -- David Eves -- You received this message because you are subscribed to the "BBEdit Talk" discussion group on Google Groups. To post to this group, send email to bbedit@googlegroups.com To unsubscribe from this group, send email to bbedit+unsubscr...@googlegroups.com For more options, visit this group at <http://groups.google.com/group/bbedit?hl=en> If you have a feature request or would like to report a problem, please email "supp...@barebones.com" rather than posting to the group. Follow @bbedit on Twitter: <http://www.twitter.com/bbedit>
