A challenge I can imagine with the "screen" workflow is detecting when a command has been executed (and capturing stderr/stdout). Do you have a solution for that in mind?
On Wed, Apr 17, 2013 at 5:21 PM, Terry Brown <[email protected]>wrote: > On Wed, 17 Apr 2013 14:48:59 +0300 > "Ville M. Vainio" <[email protected]> wrote: > > > Often, I find myself wanting to execute system commands in serial fashion > > (first in, first out), capture their output, and allow browsing it, BUT > not > > blocking Leo or ipython terminal. > > > > I'd like to show stderr and stdout in g.es, or separate log page, and > > provide callback after task has been completed. > > There's the leoscreen stuff for integration with the GNU `screen` > terminal switcher / manager. Push lines from the body to the terminal, > pull lines back the other way. But more for interactive interaction > with terminal programs than batch oriented work. Leo doesn't block. > > Cheers -Terry > > > Unless anyone has something like this already, I plan to create it > "later" > > with QProcess. > > > > -- > You received this message because you are subscribed to the Google Groups > "leo-editor" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/leo-editor?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/leo-editor?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
