comment
ordered list format feature request -- subtopic numbering
ahh. well it could be done with plain text, as shown in the post; however i have been bashed for not using a system feature. Thus, the request to update the feature. I do agree that the need is for small corner cases.
comment
ordered list format feature request -- subtopic numbering
Writing actual code blocks does not work. For some reason, adding the
<ol type="">
causes the output to be an unordered/bullet list.
revised
Loading…
comment
ordered list format feature request -- subtopic numbering
@ThomasWard -- I've been bashed for not using the systems formatting, so I am formally asking for an update to that system. Note: as shown in the examples of what works, the system does support all elements of an outline except for differentiated numbering.
comment
ordered list format feature request -- subtopic numbering
Thanks for the response. I agree less is more: unless writing a strict outline. It can be easily overdone, but there are some cases when it helps.
revised
ordered list format feature request -- subtopic numbering
added 1576 characters in body
Loading…
Loading…
comment
Adding a comment = audit failed?
@zana -- everytime I have commented in an audit I have failed. almost makes you not want to comment while reviewing.
comment
Adding a comment = audit failed?
@zanna -- yes that one
comment
Adding a comment = audit failed?
@zanna -- low quality posts I think it was. a question about "./"
comment
Adding a comment = audit failed?
@zanna -- I just had another one. leaving a comment equals fail on the audit. After failing, the system revealed the comments made on the post, and my comment was almost identical to the first comment made.
comment
Tag synonym request: [soft-link] -> [symbolic-link]
doesn't symbolic link refer to both hard and soft links? Should we also make a synonym for hard-link?
comment
What to do with <!-- language: bash --> edits?
@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.
comment
What to do with <!-- language: bash --> edits?
@dessert -- appearantly the only thing that changes it is removing the space after --
comment
What to do with <!-- language: bash --> edits?
@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.
comment
What to do with <!-- language: bash --> edits?
@dessert -- it is automatic text formating. In text editors an long dash is usually entered with --. If you click edit you will see the -- is entered, but SE is displaying the dash.
comment
What to do with <!-- language: bash --> edits?
@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.
awarded
comment
What to do with <!-- language: bash --> edits?
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.
comment
What to do with <!-- language: bash --> edits?
I have never seen it before, is it a new feature? or just little used?