|
You can always un-tick the "Use Markdown formatting" option to get the old behaviour back.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
O crap, I need more coffee.
Hadn't seen that checkbox yet.
Thanks that helps (here is hoping my selection is saved).
[EDIT]
Wohooo it is saved, all problems solved
Thanks
[/EDIT]
Tom
|
|
|
|
|
I've made a change (not yet deployed) which will restore linebreaks.
You can have your cake and eat it, too. Or something.
cheers
Chris Maunder
|
|
|
|
|
*homer simpson voice*
Hmmmmmmm caaaaaaaaakkkkkkeeeeeee ...
*/homer simpson voice*
Tom
|
|
|
|
|
Your Enters are back
cheers
Chris Maunder
|
|
|
|
|
Sorry to be a pain, but that fix is now adding extra line-breaks to code blocks.
Typing:
Line 1<br />Line 2
Produces:
Line 1
Line 2
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
This makes me want to punch Markdown in the head.
OK, gimme 5.
cheers
Chris Maunder
|
|
|
|
|
Time to send a squad off these[^] to the Markdown headquarters?
Tom
|
|
|
|
|
OK, try this
var line1;
int line 2
That seems to have
fixed that.
cheers
Chris Maunder
|
|
|
|
|
var lion1;
int lion2;
Yes,
it has.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
Hi,
I would like to propose an suggestion. For example consider i am posting a question and few users are responding to it and there is a particular user who is more involved in resolving the question. Just give an option or add an icon so that i can chat with the user instantly like Skype or g talk. This shall provide more user friendly environment to the users.
|
|
|
|
|
I think this idea has been brought up in a few different ways over the years, and the general response is that all communication should be public domain and not private because your discussion could potentially help others. However, I could be wrong in my recollection.
|
|
|
|
|
You're correct. I have had a number of people over the years try to get into a private support chat, but always refer them back here. If I want to have private clients then I will want to make money from them.
|
|
|
|
|
Richard MacCutchan wrote: If I want to have private clients then I will want to make money from them.
Yeah my Aunty makes lots of money doing that.
|
|
|
|
|
You can always ask them. But the majority here won't do it; we answer questions in our own time at our own pace. If you want private consultancy then you will have to pay for it. And the overriding principle of CodeProject is that everything is free to everyone.
|
|
|
|
|
To add to what Richard says, live chat doesn;t help many people: it helps one original questioner, but everybody else with the same problem doesn't get the benefit - just the conversation up to the point at which the conversation "went private". Since pretty much by definition the problem isn't solved by then, that just means that the problem has to be solved again (and again, and again) for each of them.
Why increase the amount of work the good volunteers do answering questions?
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
We had this with Google Helpouts integration and it never took off.
cheers
Chris Maunder
|
|
|
|
|
Be fair Chris - that wasn't your fault.
If Google had opened it up to "helpers" outside the USA it might have worked a little better!
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
For some time now I have noticed that I don't always see all the threads to a post, in thread view. If I change the view state to Normal, then I see all the threads.
Normal View[^]
Thread View[^]
This has been going on for a while now, and seeing that the problem isn't going away, thought I would report it.
I am using the latest version of Chrome, Windows 7 64 bit and viewing on WEB01
|
|
|
|
|
In my code was a bug.
Into source code I dug.
With a mighty crash,
That bug I did smash.
Take that you bad, bad bug.
New code will be deployed shortly.
|
|
|
|
|
Thanks, Matthew. I am glad you found the issue. I am also glad that my report didn't send someone on a wild goose chase, looking for a bug, that didn't exist. Which is why I am usually reluctant to report.
|
|
|
|
|
You sought it here
You sought it there
That elusive bug
Could be anywhere
In the high code
Implemented in Node
So many JavaScript lines
It left no signs
Was it a problem of type
Chris did grumble and gripe
With two fixes apiece
'Tis time to release
|
|
|
|
|
I don't know if you deployed the code fix yet, but things have been working fine yesterday and today; if that helps.
|
|
|
|
|
The fix was deployed yesterday. Good to know the fix fixed it.
cheers
Chris Maunder
|
|
|
|
|
Probably the first of many bugs for the new Markdown formatting option!
According to this[^] (raw version[^]), I should be able to do this:
```javascript
var s = "JavaScript syntax highlighting";
alert(s);
```
The expected output is:
```javascript
var s = "JavaScript syntax highlighting";
alert(s);
```
However, with the "Use Markdown formatting" option selected, it produces:
</p>
var s = "JavaScript syntax highlighting";
alert(s);
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|