You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Many tools follow the convention of upper case letter used for the default value in y/n prompts. I think it is a good and concise way to convey an important aspect.
apt install shows Do you want to continue? [Y/n] prompt when the disk space requirement is significant. This is a case where the default value is Yes or Y and hitting <enter> without typing anything will continue with installation.
docker system prune on the other hand has the opposite default and shows the prompt Are you sure you want to continue? [y/N], which means hitting <enter> without typing anything will do nothing.
Is this convention out of scope of the document?
Moreover, we might also want to describe that a yes/no should accept all variations of yes, no, y, and n in case-insensitive manner.
The text was updated successfully, but these errors were encountered:
I think, continuing with the process is a careful choice and must not be made accidentally. so capital-Y Y should be used for yes, while n be used for no. keep it simple and rigid. and yes, it should must be case-sensitive.
Many tools follow the convention of upper case letter used for the default value in
y/n
prompts. I think it is a good and concise way to convey an important aspect.apt install
showsDo you want to continue? [Y/n]
prompt when the disk space requirement is significant. This is a case where the default value isYes
orY
and hitting<enter>
without typing anything will continue with installation.docker system prune
on the other hand has the opposite default and shows the promptAre you sure you want to continue? [y/N]
, which means hitting<enter>
without typing anything will do nothing.Is this convention out of scope of the document?
Moreover, we might also want to describe that a
yes/no
should accept all variations ofyes
,no
,y
, andn
in case-insensitive manner.The text was updated successfully, but these errors were encountered: