News for hackers. Stuff that matters.
Re:Slack’s new WYSIWYG input box is terrible by paulddraper on Wednesday November 20, 2019 @10:29PM (#21591187)
For the life of me, I cannot figure out how to create two adjacent but separate code blocks.

    ```
    one
    ```
    ```
    two
    ```
I've tried and tried.
Re:Slack’s new WYSIWYG input box is terrible by jackweirdy on Thursday November 21, 2019 @04:21AM (#21592545)
The flow of pasting such strings is not great either. Previously you could paste a string with backticks and it would be formatted correctly on send.

Now the behaviour is to ask you every time to apply formatting. There is an option for "don't ask again" which I tried assuming it would make autoformatting the default, but it turns off the behaviour completely with no way to get it back!

Re:Slack’s new WYSIWYG input box is terrible by ajscanlan on Thursday November 21, 2019 @05:04AM (#21592749)
`CMD + Shift + F` applies formatting.

Unfortunately it must be done every time, no autoformatting by default it seems.

Re:Slack’s new WYSIWYG input box is terrible by _asummers on Wednesday November 20, 2019 @10:45PM (#21591263)
If you add a blank line between them, then it won't combine them.
Re:Slack’s new WYSIWYG input box is terrible by paulddraper on Wednesday November 20, 2019 @11:04PM (#21591348)
I didn't really want an extra blank line between them.

Still...I could have swore I had tried that anyway. Huh.

Re:Slack’s new WYSIWYG input box is terrible by jschuur on Thursday November 21, 2019 @05:18AM (#21592814)
You can exit a code block by hitting Command Option Shift C. I found this out by hovering over the code block icon in the bar below the editor box.

The trick seems to be to add a blank final line, otherwise, it will not include the last line you typed in a code block.

Re:Slack’s new WYSIWYG input box is terrible by pulse7 on Thursday November 21, 2019 @05:38AM (#21592895)
So in other words: you still need to be "tech savvy" to do this...
Re:Slack’s new WYSIWYG input box is terrible by mdaniel on Thursday November 21, 2019 @05:28PM (#21600431)
Only if you care about that level of specificity of the results; and given that non-technical people love pasting code snippets into slack without the code fences, I'm guessing this change isn't even wanted by non-technical people, and only made detail-oriented folks upset
Re:Slack’s new WYSIWYG input box is terrible by djsumdog on Thursday November 21, 2019 @10:57AM (#21595408)
You don't need the key combo, just as you said, you just need another line, with text or a blank line. I guess before now you could but them right back-to-back? This has never been my use case, but if it was, I can see how this is annoying.
Re:Slack’s new WYSIWYG input box is terrible by another-dave on Friday November 22, 2019 @08:06AM (#21605185)
I'm fairly sure you also used to be able to put bullets in blockquotes, right?

e.g.

  > * My quoted bullet point
I can't double-check it now as all my workspaces have converted
Re:Slack’s new WYSIWYG input box is terrible by sgustard on Wednesday November 20, 2019 @10:45PM (#21591259)
Typing option-return between the two blocks works for me.
Re:Slack’s new WYSIWYG input box is terrible by kjer on Thursday November 21, 2019 @12:00PM (#21596271)
insert newlines until your eyes bleed