- Isn't there a HTML tag that we could set a CSS style on to work this way?so is deciding on a markdown representation. For example, prefixing each line with '! ', the same way block-quotes use ' ' This is a block quoteusing current syntax.but, the following is a spoiler!! This is a spoiler,! Using a new syntax.
- Markdown’s presence has only grown since its introduction, and it continues to do so. Markdown is the unofficial standard on popular coding sites such as GitHub. It is also the default formatting option for popular communication tools such as Skype, Slack, and (to a lesser extent) Facebook Messenger.
Katie Notopoulos, complaining at BuzzFeed about the way Slack now renders text wrapped in tildes (“~like this~”) as strikethrough:
Ok, so this is almost certainly because of Markdown, a tool thatturns text into HTML. In Markdown, putting tildes around a wordmakes it appear as strikethrough text. Using Markdown makes somesense, I ~guess~, since many of Slack’s clients use it for codingand other technical purposes.
Me and the Boys as single Emotes - discord emoji/emote for your discord server! Browse thousands of other custom Discord and Slack emoji on emoji.gg. A HTML to Markdown Service. View Docs at Docs.
But what about the rest of us? Those of us who don’t know shitabout Markdown or coding or who John Gruber is or ~whatever~ man?What about the people who NEED our tildes back so we can actuallycommunicate with each other in the language that is ~native~ toonline discussion???? WHAT ABOUT US???????
There is no strikethrough syntax in Markdown. Go ahead and look at the official syntax. Tildes have no meaning, and are passed through as-is by any good Markdown processor. If Slack didn’t have their heads up their asses and actually used Markdown-style formatting syntax, there’d be no problem. (And we’d get italics instead of bold when we did
*this*, as we should.)
Adding support for a strikethrough syntax is a longstanding request for Markdown, but I omitted it by design. For one thing, there is no good punctuation to represent strikethrough. Tildes don’t look like strikethrough at all — tildes are squiggly, but a strike is a straight line. The most-requested syntax — wrapping the to-be-struck-through text in hyphens, like
-this- — is visually hard to distinguish from dashes used to indicate a pause or parenthetical clause. To me, there is no punctuation that better represents struck-through text than the raw HTML
<del> tag. The primary goal of Markdown is to remain readable as plain text.
For another thing, strikethrough isn’t used frequently enough to justify a shortcut. If Markdown provided its own syntax for all of the various HTML tags that people think that they want, it would be a minefield of special cases that you’d need to be aware of at all times while writing. A big part of Markdown’s (still growing) success is that I kept the syntax relatively small.
Update: Tildes-for-strikethrough comes from the GitHub-Flavored Markdown (which is a Markdown variant I like a lot — I just don’t think the syntax for a programmer-oriented variant is applicable to a general-purpose audience like Slack’s). BuzzFeed has updated Notopoulos’s article accordingly.
★ Thursday, 5 November 2015
Slack has just recently rolled out a “WYSIWYG text input” widget to its Web browser interface.(Apparently, the phased rollout started at the beginning of November 2019, but it’s just now starting tohit the workspaces that I participate in.) The user experience of using this new input method isreally, really, really bad.
First of all, there is no way to go back to plain old Markdown input.(See @SlackHQ’s responses in this massive Twitter thread.)If you prefer the old interface… well, screw you, says Slack.
It wouldn’t be a problem if the WYSIWYG interface supported “editing” in the way that Slack usersare used to. But right now a whole lot of stuff is broken — not just “I typed some slightly wrongsequence of characters and now the text looks messed up,” but “I cannot figure out how to recoverthe original formatting without deleting my entire message and starting over.”
Html To Slack Markdown Code
For example: In Markdown, if I have typed
it will display, unsurprisingly, as “when you do
foo() it foos the bar.” However, in the new WYSIWYG editor,it displays as
That is, closing backticks are not respected! If you want the proper display, you must hit right-arrowafter the closing backtick (but before the space). That’s quite a gymnastic for someone with decadesof muscle memory.
Now suppose you’ve gotten it displaying right, and now you realize (before hitting Enter) that you reallywanted it to say
bar.foo() instead of
foo().In the old Markdown interface, I can just left-arrow until the cursor is located immediately before the
foo,and add the new characters
bar. In the WYSIWYG interface, if you follow that same sequence of steps,even though the cursor is clearly displayed inside the code span when it’s located immediately before the
f,what you’ll see after typing
bar. is this:
I think the only way to insert text at the beginning of a code span in the WYSIWYG editor isto highlight the first character of the span and type over it (thus cloning all its formattingonto the new text you’re typing).
I wish Slack would provide a way to disable the WYSIWYG rich-text-input box. I don’t think it’suseful, and it’s extremely annoying to have to keep backspacing to fix mistakes. I’m already startingto reduce the amount of formatting I use on Slack (e.g., typing “when you do bar.foo() it foos the bar”without any code highlighting) just so that I can maintain typing speed. But I really don’t want to haveto do that! I just want to be able to type Markdown at speed and have it render the way I’ve grown used to.
If you know someone who works at Slack, please feel free to send them a link to this post!
Front-page-of-Hacker-News UPDATE: First of all, whoa! I didn’t expect this postto go quite this viral.But very cool. :)
Funny story: This blog runs on Jekyll, which means I write these posts in Markdown.I pushed this post so quickly that I didn’t notice until a day later that I had accidentallyput both the “raw Markdown” and “rendered” examples above into code blocks, so that readerswere seeing raw Markdown syntax (with backticks) for both the “before” and “after” cases.Nobody seems to have remarked on that, which I take to mean that the 50,000-some people whoread this blog (before my free plan with Mixpanel stopped tracking the hits) are pretty muchcomfortable seeing “
bar.`foo()`” and mentally interpreting it, without any lossof fluency, as “bar.
When I posted, I had tested my two examples in Safari; I didn’t think to check whether they reproduced in other browsers.As of 2019-11-22, here’s what I see in my two browsers of choice:My first example above reproduces in Safari but not in Chrome; and actually in Safari you have to hitright-arrow instead of space, not in addition to space.My second example reproduces in both Safari and Chrome.
Here’s a third example, reproducible in both Safari and Chrome. If you type
Slack Markdown Code
into the new WYSIWYG editor, it will display as:
Here I had to switch from Markdown to HTML in the “rendered” version, because (as far as I know)there is literally no way to generate “italic teletype text” font in Markdown.For example, Alexander Dupuy says:
Markdown allows monospaced text within bold or italic sections, but not vice versa
R Markdown Tutorial
Being a C++ programmer, I use multiple underscores in code a lot. I would like them not to be messed with, please.
Finally, as long as I’m getting traffic to this post, this might be the place to mention thatbesides talking about C++ a lot for free,I also do corporate training! If you’re looking for a multi-day training course, with exercises,on pretty much any aspect of the C++ language, feel free to shoot me an email by clicking onthe leftmost icon below.
Html To Slack Markdown Download
Partial Victory update: As of 2019-12-03, Slack has added an option to the browser version:“Preferences > Advanced > Format messages with markup.” See full details here(Chris Hoffman, 2019-12-03). Setting the option in your “Preferences” for a given workspace willcause it to carry over to that workspace, in the browser, on any computer. However, setting the optionfor one workspace will not affect any other workspace; and setting the option in the browser willnot affect that workspace on the Android mobile app.
On the Android mobile app, “Preferences” is called “Settings”, and it’s hiding at the bottom of the overflowmenu as described here. It has an“Advanced” section, but no markdown-related options in there as far as I was able to tell.