|
|
and that's all the proof she needed.
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
|
|
|
|
|
Did I ever mention that Mrs Wife's father used to run a brewery? :innocentWhistle:
veni bibi saltavi
|
|
|
|
|
"Used to" as in "until Nagy came along"? 
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
It was before we met; honest.
veni bibi saltavi
|
|
|
|
|
She was only a...
...bricklayer’s daughter, but she was certainly stacked.
...cobbler’s daughter, but she was built to last.
...statistician’s daughter, but she knew all the standard deviations.
and 56 more (not all KSS)
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack.
--Winston Churchill
|
|
|
|
|
|
We have the option for using Markdown but something I've been thinking about adding for, well, way too long, is auto-formatting of things like _underline_, *italics* and **bold**.
I'd also be looking automatically turning
- item 1
- item 2
and
1. Item 1
2. Item 2
Into unordered and ordered lists respectively.
It's "Markdown Extra Lite", really. Markdown without the surprises. Full Markdown would still be offered.
Would this completely ruin society as we know it, or would a change like this "just work". Essentially I'm looking for examples of were auto-formatting like this would be A Bad Thing.
cheers
Chris Maunder
|
|
|
|
|
I'd love to see rudimentary tables
===
header1 | header2
===
aaa | BBB
111 | 222
xxx | YYY
===
|
|
|
|
|
Sometimes I do use list's in my answers, like
1. ...
2. ...
3. ...
or
* ...
* ...
* ...
It can be nicer to get it formatted at the end, but didn't found it such a problem to disturb you 
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
But my ordered lists always start with zero (as they should, BTW). I refuse to kowtow to lesser minds that think VB is "the one true way".
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
Amen.
Either zero-based, or not at all.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
What about (a), (b), (c)?
|
|
|
|
|
They should be converted to integers so they can be correctly ordered.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
John Simmons / outlaw programmer wrote: They should be converted to integers so they can be correctly ordered.
They are integers, he just started at 10
|
|
|
|
|
I can't think of any, other than it should start with "0. Item 1"
Edit: Same as previous answer.
|
|
|
|
|
I freaking hate autoformatting and usually prefer the plain old ASCII pseudoformatting. Usually the autogenerated lists are a pain to use with paragraph as the autoformatters tend to understand the "carriage return" as "hoo-ray! on to the next element of the list!" which then prompts to sequences of "Delete, Delete, Delete, Swearing, Rewrite, Enter, Swearing, Control-Enter, Swearing because the broswer interpretes it...".
And when I write *this* I really want to write "*this*" bacause if I wanted to write this I'd simply exert a bit more my fat fingers to either click on the relevant button or to write the 7 characters of the relevant tags.
DURA LEX, SED LEX
GCS d--- s-/++ a- C++++ U+++ P- L- E-- W++ N++ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t++ 5? X R++ tv-- b+ DI+++ D++ G e++>+++ h--- ++>+++ y+++* Weapons extension: ma- k++ F+2 X
If you think 'goto' is evil, try writing an Assembly program without JMP. -- TNCaver
When I was six, there were no ones and zeroes - only zeroes. And not all of them worked. -- Ravi Bhavnani
|
|
|
|
|
I do not think we need that.
If implemented (because this is no democracy, after all), then please with 0-based index.
|
|
|
|
|
My problem with *italic* is when it affects code: *myPointer*2 for example.
If it can be disabled, then I'm fine with it - but I do admit I have no problem finding italic or bold on the toolbar.
Lists would be a nice touch - it's a bit of a pain to insert the <ul>, <ol>, and <li> tags (if only because I can never remember which I need and have to Google). But will you detect "related" text:
- Item 1
Next line - Item 2
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
But you always put code inside <pre> tags, don't you?
He can make it so that it doesn't auto-format code.
The difficult we do right away...
...the impossible takes slightly longer.
|
|
|
|
|
That didn't work with markdown in QA ... 
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
Make it a user profile option, and default it to "off".
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
Perhaps just a few more HTML elements? Even for your lists, you could pop out the opening/closing elements and the user can fill in the blank (or like a link, highlight the text and select the HTML markup). The additional items could be in a drop-down
You may notice I'm not a fan of wiki markup.
| Ravings en masse^ |
|---|
| "The difference between genius and stupidity is that genius has its limits." - Albert Einstein | | "If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
Typing isn't actually that hard, and all the words that anyone might need are available in plain text, so is it really worth the effort it would take to implement and maintain?
A bullets button might be handy, but numbered lists are by nature buggy (especially if someone wants more than one such list), so they could be more trouble than they're worth.
Less (time spent working on formatting) is more (time spent working on content)
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Mark_Wallace wrote: Typing isn't actually that hard
Be careful - you're establishing a precedent that will cause new programmers to be forced to give up their copy/paste coding technique.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
