Hi, >> If you really think we should not mention the default value there that's >> okay but on the other side I request that the behaviour of the readline >> frontend is changed to at least present the user the current/default >> value if the libterm-readline-gnu-perl package is not installed. And >> make it very clear that hitting return means submitting an empty value. > >It does. It prompts as follows: > > Directory to dump databases: _ > >Barring some note that tells them there is a default, noone would expect >hitting enter to result in some default value here[1]. The convention is >that this means there is a default value: > > Directory to dump databases [/var/backups/slapd-VERSION]: _ > >Or this: > > Directory to dump databases: /var/backups/slapd-VERSION_
I suggest that the frontend should explicitly indicate if it cannot handle default values, although the there is one, e.g. like this: Default value: /var/backups/slapd-VERSION *** WARNING! You have to type the default value verbatim to use it! Directory to dump databases: _ I feel important to first display the default value, and then the warning message. (Please rephrase it if needed, as I am not a native English.) Another solution could be if the frontend asks a yes/no question to use the default value, if the question has one. >Debconf uses one or the other of these conventions when possible. Only >experienced users use these frontends, and experienced users are >expected to be aware of these conventions. I use readline frontend because I use debian since 5-6 years, and that time this was the only one with which I could look what happened so far (I do not know whether there are others now). And I was not aware that my frontend do not support default values. Ferenc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
