Comment on Two chemists walk into a bar

• FiskFisk33@startrek.website ⁨2⁩ ⁨years⁩ ago

  Image

  source

  • PoolloverNathan@programming.dev ⁨2⁩ ⁨years⁩ ago

    !technicallythetruth@lemmy.world

    source
  • exscape@kbin.social ⁨2⁩ ⁨years⁩ ago

    And on kbin it shows as strikethrough, so the 2s are crossed out.

    source
• Opisek@lemmy.world ⁨2⁩ ⁨years⁩ ago

  Now all I want is inline TeX.

  source

  • Zagorath@aussie.zone ⁨2⁩ ⁨years⁩ ago

    I do quite like how clear TeX is. The curly braces make it completely unambiguous how everything is supposed to be parsed, which means even though it’s a little more awkward to write, it’s still a lot easier to write if your comments are getting more complicated. Plus it’s so much easier for the parsing libraries to get right.

    source

    • Opisek@lemmy.world ⁨2⁩ ⁨years⁩ ago

      I just love how universal it is. Sure, it has its flaws, but its strength is how many different applications use it. Once you know how to write TeX, you can express any equation you want clearly and understandably, an opposed to trying to write it with Unicode. Bonus points for how easy it is to add TeX rendering to the web with libraries like KaTeX (my personal favourite) or MathJax. I was able to add TeX support to my blog in 10 minutes.

      I’m a bit of a sucker for TeX as might be apparent from my infodumping. If anyone’s as passionate and doesn’t know of it yet: You should try the texnique.xyz game. It’s a timed TeX typing game. I can get up to 70-80 points in it fairly consistently :D

      source

      • marcos@lemmy.world ⁨2⁩ ⁨years⁩ ago

        I just love how universal it is.

        Lol!

        Half of the stuff people expect to work is library code that isn’t even bundled at the default TeX context. Most of the symbols don’t even come packaged with the TeX interpreter.

        Somebody should really make a “standard TeX” and LaTeX should adopt it.

        source

        • -> View More Comments
• ADTJ@feddit.uk ⁨2⁩ ⁨years⁩ ago

  Your example doesn’t work for me but the one above is shown in superscript

  source

  • Zagorath@aussie.zone ⁨2⁩ ⁨years⁩ ago

    Oh that’s quite weird. What client is that?

    source

    • teejay@lemmy.world ⁨2⁩ ⁨years⁩ ago

      Sync

      source
    • readthemessage@lemmy.eco.br ⁨2⁩ ⁨years⁩ ago

      It does not work in Boost as well

      source
  • jaybone@lemmy.world ⁨2⁩ ⁨years⁩ ago

    Shows as superscript on Memmy.

    source
• T4V0@lemmy.world ⁨2⁩ ⁨years⁩ ago

  Works on Voyager at least.

  source
• Leate_Wonceslace@lemmy.dbzer0.com ⁨2⁩ ⁨years⁩ ago

  H~2 O~2

  source

  • theonyltruemupf@feddit.de ⁨2⁩ ⁨years⁩ ago

    Hey @ljdawson@lemmy.world this formatting doesn’t seem to work in Sync :)

    source
  • PoolloverNathan@programming.dev ⁨2⁩ ⁨years⁩ ago

    You need to surround the text. H~2~O~2~ = H~2~O~2~.

    source
• qaz@lemmy.world ⁨2⁩ ⁨years⁩ ago

  Your example is also rendered

  source

  • Zagorath@aussie.zone ⁨2⁩ ⁨years⁩ ago

    Huh? I know some clients fail to properly display superscript and subscript (which shouldn’t be a problem since it would be the same for my text as for the above text anyway), but I didn’t think there were any clients that would choose to render code snippets as formatted text. Anyway, here’s a screenshot of how it should look:

    Image

    source

    • qaz@lemmy.world ⁨2⁩ ⁨years⁩ ago

      Thanks, it seems to be a bug with the Thunder app.

      source

      • onion@feddit.de ⁨2⁩ ⁨years⁩ ago

        Also Infinity

        source
• brbposting@sh.itjust.works ⁨2⁩ ⁨years⁩ ago

  Worked in Voyager iOS at least, very cool

  source
• mnemonicmonkeys@sh.itjust.works ⁨2⁩ ⁨years⁩ ago

  Neat

  source