-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday 14 June 2003 13:17, [EMAIL PROTECTED] wrote: > Some one please chim in if I am wrong here, but it is my understanding > that control-s only stops output being displayed to the terminal. It won't > actually stop things from happening. It is ment if things are scrolling to > fast and you to stop to read it. Control-Q is its counter-part to continue > output. > > Now it may be possible that these are signals that can be trapped by > python, but I think they are received in the tty layer and never get > passed to python. > > The only thing that I can think of that can answer this question is > actually killing the emerge [like w/ control-c], then starting it up again > w/ emerge --resume. I know the --resume feature is new since 2.47 and was > ment incase you emerge -e world, although it may have more uses. I can > also tell you that --resume will have to start from the start of the last > package it was working on, however it will not redo any that it has > already finished. > > Cheers, > Mike
I second that. The --resume option seems to be the only answer, and I've used it numerous times. Very effective for putting long-winded stuff on screen. Callan - -- "I disapprove of what you say, but I will defend to the death your right to say it." - Beatrice Hall Registered Linux User #311796 ICQ UIN: 1926211 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE+6rMinyMhcbScbQYRApo5AJ4gBKLftpL8HUlBjQLHMXVYfWyJDwCggs7C ZHy8R3zoWWPz9DXaiefGI08= =XeHE -----END PGP SIGNATURE----- -- [EMAIL PROTECTED] mailing list
