Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. Other Discussions
  3. Site Bugs / Suggestions
  4. The ="" issue

The ="" issue

Scheduled Pinned Locked Moved Site Bugs / Suggestions
beta-testinghelptutorialquestion
3 Posts 3 Posters 8 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • K Offline
    K Offline
    k5054
    wrote on last edited by
    #1

    We've all seen posts in QA where code blocks are littered with ="" decorations. The usual response has been to assume that the OP has done something wrong when cutting and pasting the code. But I have an example here where there is no cut/paste operation being used, and still the ="" decoration appears: In this case, it seems to be something to do with the octothorpe (#), the forward slash (/) and possibly the < and > symbols as well. Maybe there's an issue in the markdown processing?

    "A little song, a little dance, a little seltzer down your pants" Chuckles the clown

    J P 2 Replies Last reply
    0
    • K k5054

      We've all seen posts in QA where code blocks are littered with ="" decorations. The usual response has been to assume that the OP has done something wrong when cutting and pasting the code. But I have an example here where there is no cut/paste operation being used, and still the ="" decoration appears: In this case, it seems to be something to do with the octothorpe (#), the forward slash (/) and possibly the < and > symbols as well. Maybe there's an issue in the markdown processing?

      "A little song, a little dance, a little seltzer down your pants" Chuckles the clown

      J Offline
      J Offline
      jeron1
      wrote on last edited by
      #2

      k5054 wrote:

      octothorpe (#)

      New word of the day, at least for me. :)

      "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

      1 Reply Last reply
      0
      • K k5054

        We've all seen posts in QA where code blocks are littered with ="" decorations. The usual response has been to assume that the OP has done something wrong when cutting and pasting the code. But I have an example here where there is no cut/paste operation being used, and still the ="" decoration appears: In this case, it seems to be something to do with the octothorpe (#), the forward slash (/) and possibly the < and > symbols as well. Maybe there's an issue in the markdown processing?

        "A little song, a little dance, a little seltzer down your pants" Chuckles the clown

        P Offline
        P Offline
        Peter_in_2780
        wrote on last edited by
        #3

        I've been bitten a couple of times. I work around it by replacing the literal < with the encoding &lt;. (Both encoded another level as I type this, of course!)

        Software rusts. Simon Stephenson, ca 1994. So does this signature. me, 2012

        1 Reply Last reply
        0
        Reply
        • Reply as topic
        Log in to reply
        • Oldest to Newest
        • Newest to Oldest
        • Most Votes


        • Login

        • Don't have an account? Register

        • Login or register to search.
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • World
        • Users
        • Groups