[Aptitude-devel] Bug#246672: aptitude: quit directly instead of pressing a key to continue

Manuel A. Fernandez Montecelo manuel.montezelo at gmail.com
Thu Mar 10 23:22:57 UTC 2016


2016-03-10 18:54 martin f krafft:
>also sprach Manuel A. Fernandez Montecelo <manuel.montezelo at gmail.com> [2016-03-10 18:04 +0100]:
>> I don't know if your complaint is more the speed side of reloading
>> the cache, or that you just don't see the need and don't want
>> curses to be restored just for quitting.  In the latter case,
>> maybe it would not be very difficult to implement what you ask,
>> but the reloading of the cache would continue to be there.
>
>Shouldn't the reloading of the cache happen in the background right
>away? Why do I need to hit a key for it to start. Instead, start it
>right away, and let the user hit a key to continue or 'q' to quit.
>If s/he continues, then the UI can pick up the background process.
>If 'q' is pressed instead, say that "aptitude is shutting down"
>until the background process returns.

Would be a nice idea, but aptitude is absolutely not ready to do this in
the short or medium term.  That is, not going to happen anytime soon for
this particular case.

So having that into account, what's the reply to the question above?


Cheers.
-- 
Manuel A. Fernandez Montecelo <manuel.montezelo at gmail.com>



More information about the Aptitude-devel mailing list