Timeline for Should the keys be written in uppercase?
Current License: CC BY-SA 4.0
14 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Jun 12, 2020 at 14:35 | history | edited | CommunityBot |
Commonmark migration
|
|
Jul 2, 2018 at 16:30 | comment | added | user17723 |
@Melebius - your argument is a logical fallacy of equivalence, they two are not the same at all, That version of BASIC still REQUIRED line numbers, newer languages do not, it was not a stylistic choice to put line numbers. I explain why it is they way it is and why using all caps is still the correct way to document key usage in written/printed documentation. Do whatever you want, you have to deal with the tech support of your users not me.
|
|
Jul 2, 2018 at 6:34 | comment | added | Melebius |
I appreciate the historical excursion. However, things evolve. We don’t prepend numbers to our codes like we did with Commodore 64, for example. There is a better way to highlight keys on Stack Exchange than writing them in all uppercase: the <kbd> tag. Even without the tag (like in a comment), I find things like Ctrl+F1 well readable. Moreover, there is a PrtScn/SysRq key on my keyboard, would it be still readable if written as PRTSCN/SYSRQ ?
|
|
Jun 29, 2018 at 14:14 | history | edited | user17723 | CC BY-SA 4.0 |
deleted 14 characters in body
|
Jun 29, 2018 at 14:08 | history | edited | user17723 | CC BY-SA 4.0 |
added 2 characters in body
|
Jun 29, 2018 at 14:03 | history | edited | user17723 | CC BY-SA 4.0 |
added 2 characters in body
|
Jun 29, 2018 at 13:56 | history | edited | user17723 | CC BY-SA 4.0 |
added 90 characters in body
|
Jun 29, 2018 at 13:54 | comment | added | user17723 |
if you read it as a history lesson and nothing else, you missed the point that it is exactly the historical relevance in ASCII text based documentation that this has always been and is still the valid idiom for documenting keystrokes. Same reason that RFC documents use Must , Shall and May and go to great lengths to document exactly what the semantics of each word are in ever RFC document. Specificity and disambiguation, which I explain in my answer as well.
|
|
Jun 28, 2018 at 17:16 | history | edited | user17723 | CC BY-SA 4.0 |
added 122 characters in body
|
Jun 28, 2018 at 17:11 | history | edited | user17723 | CC BY-SA 4.0 |
added 8 characters in body
|
Jun 28, 2018 at 17:05 | history | edited | user17723 | CC BY-SA 4.0 |
added 781 characters in body
|
Jun 28, 2018 at 17:00 | history | edited | user17723 | CC BY-SA 4.0 |
added 781 characters in body
|
Jun 28, 2018 at 16:54 | history | edited | user17723 | CC BY-SA 4.0 |
added 781 characters in body
|
Jun 28, 2018 at 16:48 | history | answered | user17723 | CC BY-SA 4.0 |