Open GoogleCodeExporter opened 8 years ago
you are wrong, reading stdin is always important. progress bar indicates that
process is running or not. and only way to check this is a read data from
stdin. no data - no progress
but in your case you may try to use some third-party tools for generating
output for your process. for example - pv
(http://www.ivarch.com/programs/pv.shtml)
Original comment by ananasik
on 17 Apr 2011 at 5:19
Can you check if a process is running by its pid? Thanks for the pv
recommendation.
Original comment by tri...@gmail.com
on 17 Apr 2011 at 5:34
check running process is a task for glue script, not for yad.
like follow
lxsplit -j file.avi.001 &
while pkill -0 lxsplit; do
echo running
sleep 0.5
done | yad --progress --pulsate --auto-close --auto-kill --button gtk-cancel:1
Original comment by ananasik
on 17 Apr 2011 at 5:41
I am really liking yad, it is much more powerful than zenity. However I am
having trouble getting the log function to work. Try this example and maybe
someone can help me understand what I am doing wrong
lxsplit -j file.avi.001 &
while pkill -0 lxsplit; do
echo running
sleep 0.5
done | yad --progress --pulsate --auto-close --auto-kill --button gtk-cancel:1
--enable-log --log-expanded
Thanks
Original comment by coopercr...@gmail.com
on 5 Dec 2013 at 3:19
only stings, started with '#' appends to log
lxsplit -j file.avi.001 &
while pkill -0 lxsplit; do
echo '#running'
sleep 0.5
done | yad --progress --pulsate --auto-close --auto-kill --button gtk-cancel:1
--enable-log --log-expanded
Original comment by ananasik
on 5 Dec 2013 at 5:24
Thanks for the reply.
Is there any way to tail -f a log file for example to the yad progress log?
Original comment by coopercr...@gmail.com
on 10 Dec 2013 at 2:00
One more thing, it seems the log command only works from an interactive shell,
not when run from a shell script.
Original comment by coopercr...@gmail.com
on 10 Dec 2013 at 2:43
try to disable buffering with stdbuf command in your script
Original comment by ananasik
on 10 Dec 2013 at 5:53
Original issue reported on code.google.com by
tri...@gmail.com
on 17 Apr 2011 at 2:02