On Thu, 2013-01-24 at 15:18 +0100, Stefan Assmann wrote: > On 23.01.2013 17:55, James Antill wrote: > > Are you aware of the alwaysprompt config? > > I've read the documentation about alwaysprompt, but I'm not sure how > this would be of help.
Because tends to solve the problem of being annoyed with confirmations. In the case of things like "yum install foo", it won't prompt you for the trivial cases ... thus. when it does prompt you, you'll want to do more than just glance and hit return. > > What result are you trying to achieve? > > Trying to provide a way for users to have a review step of your action > with a quick way to confirm by simply pressing enter. The big reason that we default to No is: yum install foo <ret> <ret> ...having the failure case here be "you have to run the command again" can be annoying, but having it be "you got no review" has a whole lot more downside risk. This was mostly a "fail in the best way" for user error, but I've also seen more than a few X/gnome-terminal/whatever bugs where it likes to repeat a key you've typed N times. > Personally I prefer something like "yum install foo" with a dialog like > Is this ok [Y/n]: > having a short glimpse over the dependencies and just hit enter over > specifying -y which will just move ahead and do the action. Right, but putting the code in the prompt UI means it applies to anything that prompts ... not just the simple "install foo"s that you mostly want to ignore. Eg. installing CA GPG keys. > Putting it another way, it's a lesser form of "assumeyes". The problem is that people might not realize that it's almost an exact form of assumeyes, depending on "minor" bugs in other software or PEBCAK. _______________________________________________ Yum-devel mailing list Yum-devel@lists.baseurl.org http://lists.baseurl.org/mailman/listinfo/yum-devel
