News for hackers. Stuff that matters.
Re:Slack’s new WYSIWYG input box is terrible by pbreit on Wednesday November 20, 2019 @11:01PM (#21591341)
Your asterisk example works OK for me. As does the blog writer's "when you do `foo()` it foos the bar".
Re:Slack’s new WYSIWYG input box is terrible by rerx on Thursday November 21, 2019 @05:41AM (#21592905)
I could not reproduce the example issues from the blog post, but the dual asterices inside the back ticks still fail for me.

The upside is that it's now possible to have bold passages in monospaced text. I missed that before.

Re:Slack’s new WYSIWYG input box is terrible by indosauros on Thursday November 21, 2019 @08:48AM (#21593906)
Here's a gif of the second issue from the blog post, just reproduced on my client

https://i.imgur.com/X8FZJhi.gif

Re:Slack’s new WYSIWYG input box is terrible by rerx on Thursday November 21, 2019 @10:16AM (#21594860)
Ah, earlier today the Slack app on my Mac had not updated yet -- there I experience the same issue.

The web client on Firefox works better, though: https://imgur.com/a/X53iIlm

Edit: On Chrome it's broken for me too....

Re:Slack’s new WYSIWYG input box is terrible by pbreit on Friday November 22, 2019 @07:26PM (#21611522)
Well, that just looks like a bug then.

I think the concern is mostly about what Slack was actually trying to achieve.

Re:Slack’s new WYSIWYG input box is terrible by narrowtux on Thursday November 21, 2019 @04:45AM (#21592661)
Yeah, seems this was fixed pretty quickly by not parsing the ` immediately but only after you've entered the closing `