Hacker News Reader

Comment by LilBytes | Hacker News Reader

The specific example shown in the attached article works fine for me in Slack with the updated editor.

``` when you do `foo()` it foos the bar. ```

Looks fine for me? Only the `foo()` is highlighted, not the entire line as shown. Have they pushed out a fix for this already?

View on HN

According to the Slack twitter, yes (https://twitter.com/SlackHQ/status/1192199216157868037)

That tweet was posted Nov 6, this blog post was posted today.

FWIW I'm unable to reproduce both examples in the blog post - they work correctly for me in my Slack web interface.

That example worked fine for me, the second example (a variation on the first) worked as the article described. Once foo() was "code", I couldn't update it (at least I couldn't discover how to do so outside of killing that bit).

I'd bet the first example didn't work at some point, and then was quickly patched.

The second example worked correctly seamlessly for me as well. I can easily edit text inside a code block in the WYSIWYG editor. Maybe they just patched that too?

Hmmm... possibly testing a patch... I still can't get it to work and checked for updates before trying. There could naturally be a difference in our sequence of steps, too. Once "foo()" is entered and detected as code, I can't add "bar." after the fact. I can add new code text in the middle of the detected code.

it works for me too. I'm confused...

I can only assume it's been fixed then???

Perhaps this is mostly hyperbole to change. I mean, Markdown is amazing. But as stated it was only a `lite` implementation of the editor.

The new editor seems fine for me so far, though I'll gladly be proven wrong.

it works for me too and I have been using this editor for a while. I don't remember seeing this kind of bug at all :/ .

Reply on news.ycombinator.com