Comment # 2 on bug 1175929 from macias -

> If you get solutions offered to a problem you need to properly investigate the 
> solutions and not just always go with keep obsoletes and hope for the best.

I didn't say that.

> So we cannot simply say , number 2 is always for keeping obsoletes. 

Ok, let' make it (k). And you can, here is how.

> Those are different for every problem we might encounter, also a solution might 
> not only have a keep obsolete but also it needs to install a new package or 
> update another one, remove a lock etc. 

In short there are multiple scenarios, I agree. Yet, among them there are very
"special" cases, when the action for all packages involved is the same. Like
keep, or deinstall.

So user would see (just an example):

Problem: problem foo
 Solution 1: Following actions will be done:
  keep obsolete xxx
  install new package boo
  update kernel
 Solution d: deinstallation of yyy
   deinstallation of zzz
   deinstallation of aaa
  Solution k: keep m
    keep n

I hope it is clear the same way you can in advance predict action "cancel", we
can predict action "keep all packages mentioned", "delete all packages
mentioned", and thus assign them fixed shortcuts. For those actions, that are
ad-hoc solutions, the bindings would be dynamic, 1, 2, 3, and so on.