|
So I want two lines to not be treated as a paragraph.
Like this:
Line1
Line2
Not this:
Line1
Line2
Google, find this. Says:
A paragraph is consecutive lines of text with one or more blank lines between them. For a line break, add either a backslash \ or two blank spaces at the end of the line.
In Bitbucket's wiki, backslash doesn't work. Two blank spaces does. So now there is a totally f***ing invisible whitespace that indicates a line break.
God, I hate markdown.
Latest Article - A Concise Overview of Threads
Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny
Artificial intelligence is the only remedy for natural stupidity. - CDP1802
|
|
|
|
|
It annoys me enough in QA, and I have it disabled there! Even disabled, it manages to creep in and add code blocks, strike throughs, and such like stupidity to code. Fortunately, it's only there until I refresh a solution, but ...
Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Amen.
I just dug through a work request that was in part fixing a boatload of markdown documents so that code blocks in the middle of lists were formatted correctly. Gotta make sure all our text lines up nicely... 
1. something
```
is wrong
```
1. with this
---
1. but this
```
is fine
```
1. gah
TTFN - Kent
|
|
|
|
|
String programming* is fantastic.
But white-space programming...that's another level of genius altogether!! 
|
|
|
|
|
Exactly! If I had wanted to program in Python, I would have hit myself upside my head with a brick.
TTFN - Kent
|
|
|
|
|
Kent Sharkey wrote: Exactly! If I had wanted to program in Python, I would have hit myself upside my head with a brick.
Genuine LOL!
But I think it might be more on the order of a boulder-size stoning.
|
|
|
|
|
Especially variable pitch fonts. That leads to using fixed pitch fonts OR inserting tabs and then you have another rabbit hole to dig yourself out of.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
|
|
|
|
|
raddevus wrote: But white-space programming..
Can we even call it that anymore?
".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
|
|
|
|
|
raddevus wrote: white-space programming
I seem to remember there was a Brain![Elephant | [mastadon]](https://www.codeproject.com/script/Forums/Images/elephant.gif) [^] variant that used space, tab, carriage return, and line feed characters in place of some of the commands.
Software Zen: delete this;
|
|
|
|
|
That's an interesting subject and a good wiki entry. thanks for sharing.
|
|
|
|
|
I like Markdown in general, but dislike the case you ran into: there are so many Markdown implementations that *mostly* work the same way, but you run into edge cases like the line break where it's inconsistent across implementations - some do it one way, others do it another way, and others don't support it at all.
Interestingly, the documentation you linked to is from Commonmark - which is an attempt to standard Markdown and give all implementations a common spec to target.
Maybe we should give Bitbucket a hard time for using a substandard Markdown parser. 
|
|
|
|
|
Just because Mark Down spells his name correctly...
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
I was so fed up with Markdown that I wrote my own processor and then hit the wall when trying to decide which version to follow. John G who first came up with it deliberately left the spec vague and ambiguous, which is a little annoying because he's commands a lot of clout in the industry and does owe part of his livelihood to his infamy.
Fair's fair, John: nail down the standard so we can fight over it and create new standards. Otherwise all is chaos!
cheers
Chris Maunder
|
|
|
|
|
Last night, SWMBO commented on the poor quality of dark scenes in some movies.
I suspect it's simply the way the movies are mastered on the original DVD since the crappy picture varies quite a bit from movie to movie. However, I'm willing to consider it may be the video card.
I currently use a GTX-1050 (2gb ram) in the home theater box. Would a video card with more RAM resolve the problem we're seeing? If so, I'm looking at getting a 1050ti (twice as much memory as the current card, and still doesn't need an external power connector).
".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
|
|
|
|
|
Before spending money on new hardware, try downloading some calibration software for the display. Assuming you (or SWMBO  ) aren't colour-blind, you should be able to ensure that your screen is giving you the best picture that it can give.
Win10 has built-in calibration software; I assume that similar software is available for Linux.
(You can also spend money on external calibration hardware, if you've got money to burn)
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
I don't think it's a matter of calibration. The TV is a fairly new 75-inch 4k unit, and the 1050 video card has HDMI 2.0.
Non-video stuff looks fine, and even HD youtube stuff looks good. I still think it's just poor mastering of the movies (most look fine), but SWMBO doesn't seem to be convinced. Like I said, it only happens on dark scenes - you can even see the pixels changing their blackness for given scenes (this is why I think it's the way the movie was mastered).
I was just wondering if more RAM would mitigate it. I don't want to get too much video card because of heat issues (that's why I picked the 1050 to begin with instead of the 1050Ti). Hell, I don't even want to replace the existing card if I don't have to.
Before you ask, when I rip movies to a hard drive, I do not use any compression (to save space on the drive).
".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
|
|
|
|
|
Have you tried fiddling with the TV's settings to help with this? I would think you will have more luck with the TV settings than with buying a new video card, after all digital is digital if you know what I mean.
|
|
|
|
|
The TV itself is fine. HD and 4K stuff from the DVD player, and TV shows (over our satellite connection) look good. None of them play through the HTPC box though. I'm thinking the standard def movies being stretched over a 75-inch screen could be a factor. That's why I was asking.
".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: I'm thinking the standard def movies being stretched over a 75-inch screen could be a factor.
That could be the TV's interpolation/smoothing to reduce pixelation.
Large black areas are also problematic when the TV is set to adapt to ambient lighting. You might try turning that off and see if it has any effect.
Software Zen: delete this;
|
|
|
|
|
I think you hit on it with your last paragraph. I had forgotten about that but I have seen it cause problems in the past.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
|
|
|
|
|
These are DVDs and not blue-ray, correct? If you are watching DVDs, then this is probably more due to the resolution SD trying to be interpreted to HD. DVDs are only capable of 720 x 480 pixels per frame (SD). If the system is trying to compensate and go to HD, the system will try to replace missing pixels with colors of existing pixels resulting in darker than normal dark scenes. That also may explain why the results are inconsistent from movie to movie. I don't believe this is a hardware issue, but more of a configuration issue.
When you are dead, you won't even know that you are dead. It's a pain only felt by others.
Same thing when you are stupid.
modified 19-Nov-21 21:01pm.
|
|
|
|
|
Donathan.Hutchings wrote: more of a configuration issue.
But where? I have no idea where to try to fix this.
".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
|
|
|
|
|
I found this page:
https://lifehacker.com/how-to-get-better-picture-quality-from-your-home-theate-1700412363
I'm going to try these settings and see if it helps (CP's automatic URL formatting doesn't seem to be working today).
".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
|
|
|
|
|
Cool. I found this page as well, but not sure if it will be of any help. How do I setup my NVIDIA based graphics card to work with my HDTV?
I've run into problems like this before with my home built HTPC. It was either the graphics driver settings or the DVD-player (software) settings.
When you are dead, you won't even know that you are dead. It's a pain only felt by others.
Same thing when you are stupid.
modified 19-Nov-21 21:01pm.
|
|
|
|
|
I would advise you to pay special attention to the part of the article regarding "RGB Limited" vs. "full-range RGB". Back in the day, television signal black levels rode at something called "setup" ( 7.5 out of 100 IRE or 16 out of 255 levels in digital terms). The purpose was to keep the video signal from interfering with retrace blanking levels, horizontal sync and other TV stuff. A black level of 0 came to be called "negative black". Anyway, flash forward to today, many devices automatically compensate for this archaic "setup" by raising black levels going from digital to analog and pushing them down going the other way. Sometimes, this will happen unnecessarily and sometimes it can happen more than once. This results in either super-crushed, murky-looking blacks or, alternatively, smokey, grey-looking blacks, lacking detail in both cases. This might be what you and SWMBO are experiencing.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
