« first day (1788 days earlier)   

6:04 AM
@FaheemMitha I didn't get you
 
 
3 hours later…
8:59 AM
@Kanth I'm sorry, I don't know what comment you are replying to. Please use the reply function of chat (click left mouse button at the left end).
 
 
3 hours later…
11:30 AM
Do not get how accepted answer resolves the issue here: unix.stackexchange.com/q/226090/28489 , Am I missing something?
Thought that: If a sub process, here ffmpeg, receive SIGINT, it should be ignored by bash unless one handle it specifically by trap.
Are there versions that operates differently?
 
@Sukminder source command run all line in a file, it is the same as if you run cmd1 ; cmd2 ; cmd3 (+Ctrl-C) ; cmd4 ; cmd5
all cmd's are run, even thon cmd3 is interrupted
s/thon/thou/
 
11:47 AM
@Archemar: Yes, source file or . file runs the script in current shell. bash file or ./file creates a new sub shell, but how does that solve issue with SIGINT sent to a sub-command in that script?
 
most likely subcomment get kill, and kill signal propagate to enclosing shell.
 
 
1 hour later…
1:19 PM
@mods - sorry for two flags, still learning.
 

« first day (1788 days earlier)