View Single Post
Old 08-12-2019, 11:47 AM   #150
NiLuJe
BLAM!
NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.
 
NiLuJe's Avatar
 
Posts: 13,506
Karma: 26047202
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
@frostschutz: Hopefully made that slightly clearer in the help message, and added a -k, --cls flag that *will* always abort early .

Obviously, in your example, unless there's a significant delay between the two calls during a single iteration, what'll happen is that the controller will bundle the two refreshes together, and you'll probably almost never see the line on screen .

Without knowing more context about your use-cases, what would make more sense to me would be a single fbink -c "$line" (i.e., clear the screen, then print $line) .

Last edited by NiLuJe; 08-12-2019 at 11:51 AM.
NiLuJe is offline   Reply With Quote