Neil Shepperd <[email protected]> writes: > You can have rules without any outputs in tup. eg: > > foreach *.pdf |> dosomething %f |> > > `dosomething` will be re-run whenever its input changes.
That would open the pdf viewer for all changed pdf files. But the idea of a no-output rule might be useful in other ways, and I'll keep it in my toolkit. > I'm not sure how well this would work with an interactive program > like a pdf viewer though, since it will be started in tup's > "special" environment (chroot or whatever). I found that it worked once I put 'export DISPLAY' before the rule. -Sanjoy -- -- tup-users mailing list email: [email protected] unsubscribe: [email protected] options: http://groups.google.com/group/tup-users?hl=en --- You received this message because you are subscribed to the Google Groups "tup-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
