Hi Thomas et al, I think I was mistaken about the problem I stated earlier. I can recreate the top issue even without your patch - so it must be my environment. I tried your latest patch, and it works fine.
One basic question I have about the code is, when the timer pops, how does the code pop out of parsecmd() to test for timed_out? Lastly, can we allow this patch into the official busybox release train? It has been asked for numerous times on this alias, and it makes ash, just a little bit more like bash. tia, rouble On Thu, Feb 3, 2011 at 5:50 AM, Thomas Geulig <[email protected]> wrote: > Am Mittwoch 02 Februar 2011, 17:37:48 schrieb rouble: >> I see an issue when running ash with this patch. When you run top, >> with this patch installed, it does not run cleanly. It just dumps >> data, and the screen does not stay in one place. I am testing with >> 1.17.3. > > I've never seen such issues. I used many versions between 1.0.0 and > 1.18.2 on arm and 386 platforms. > > But you could try the updated patch ... > > Thomas > > _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
