Timeline for What to do with <!-- language: bash --> edits?
Current License: CC BY-SA 3.0
13 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 14, 2017 at 17:29 | comment | added | Sergiy Kolodyazhnyy | @ravery That's cool ! My first coding experience was with Turbo Pascal, with that blue background editor a la MS Edit, I don't know what sort of computers those were - I was in middle school and didn't really care back then. | |
| Nov 14, 2017 at 14:50 | comment | added | ravery | @JacobVlijm -- No. Just saying that text format is just as valuable. In most cases the compiler/interpreter doesn't care about text formating, It is included for readability. | |
| Nov 14, 2017 at 14:16 | comment | added | Jacob Vlijm | @ravery not sure what we are actually discussing here, are you suggesting syntax highlighting is useless? | |
| Nov 14, 2017 at 13:14 | comment | added | ravery | @JacobVlijm -- Framework and structure can also be seen by looking at the first word of each indent level. As in the examples above. it is easily seen that the script is a if/then statement within a while loop. As noted earlier, I started programing long before a GUI desktop and text color was available on PCs. Code formating (line breaks and indents), is more significant to me than highlighting. My first experience with programing was an Atari with a BASIC cartridge installed then BASIC and FORTH on a Tandy TSR-80. | |
| Nov 14, 2017 at 12:36 | comment | added | Jacob Vlijm | @ravery psychologically, the recognition order of what the mind detects is color > shape. There are numerous interesting tests on that. The fact that it distracts you actually confirms that. It means you are not trained to get the advantage of highlighting, simply because you never used it. For anyone else, in a single glimp, the framework and structure of the code appears. Highlighting exists for a reason. Suggesting it is related to a degree is, well... | |
| Nov 14, 2017 at 12:27 | comment | added | ravery | @SergiyKolodyazhnyy -- I understand everyones point about syntax highlighting; but when I look at highlighted code, my eye jumps from keyword to keyword completely ignoring the text in between. I have to force myself to ignore the highlighting in order to read the script and understand what it is doing. I'm pretty sure that I am not alone in this. Perhaps the difference stems from earning an MA degree instead of a MS degree - ie many years scanning voluminous text for significant or relevant information. | |
| Nov 14, 2017 at 0:51 | comment | added | Sergiy Kolodyazhnyy | @ravery Exactly - you've coded for 30 years, and that's admiring, but we also have users who're clueless about programming, and it kinda helps - they'd go "oh, that blue thingy is a keyword!" | |
| Nov 11, 2017 at 21:50 | history | edited | Jacob Vlijm | CC BY-SA 3.0 |
added 3 characters in body
|
| Nov 11, 2017 at 17:59 | comment | added | Jacob Vlijm |
@ravery Writing python, unhighlighted coded is nearly unreadable for me. Look at the weird highlighting of the .desktop file. The default on AU on anything defined as code
|
|
| Nov 11, 2017 at 17:51 | comment | added | ravery | I normally use a plain text editor for writing html code. So for me the colors are distracting. PS - I started writing code 30 years ago and have never relied on a syntax highlighter. | |
| Nov 11, 2017 at 17:18 | history | edited | Jacob Vlijm | CC BY-SA 3.0 |
added 25 characters in body
|
| Nov 11, 2017 at 17:08 | history | edited | Jacob Vlijm | CC BY-SA 3.0 |
added 15 characters in body
|
| Nov 11, 2017 at 17:01 | history | answered | Jacob Vlijm | CC BY-SA 3.0 |