Re:Slack’s new WYSIWYG input box is terrible
by timcederman on Wednesday November 20, 2019 @10:50PM
(#21591282)
If you hit ctrl/cmd-z after it automatically changes something you can keep going like you used to. e.g. try typing `foo`, and then hit ctrl-z, it'll revert it to plain text. I've found that useful for getting around the autoformatting.
[ Parent
| on HN ]
Re:Slack’s new WYSIWYG input box is terrible
by igetspam on Wednesday November 20, 2019 @11:18PM
(#21591424)
That's ridiculous, right?. Cmd/Ctrl-z has a defined function. Slack is hijacking that because they've decided that decades of established patterns are wrong and creating another one-off for their very specific use case is the right thing to do. The hubris...
Re:Slack’s new WYSIWYG input box is terrible
by Doxin on Thursday November 21, 2019 @04:16AM
(#21592530)
It's not really that radical of a thing to do though. Word has the same sort of behaviour except utilising backspace. If you type " - " in word it creates a bulleted list, hit backspace once and you get the literal text you entered.
I'm not entirely sure which is the less-worse option here but at least it's not a wildly new concept, just a different button.
Re:Slack’s new WYSIWYG input box is terrible
by gmueckl on Thursday November 21, 2019 @06:11AM
(#21593049)
There are other products out there that put automatic changes on the undo stack. I regularly encounter this behaviour in Visual Studio: pasting code in the editor is decomposed into pasting text and reformatting it. So the first Ctrl-Z reverts the code to the exact text you copied. The second Ctrl-Z will remove it.
Re:Slack’s new WYSIWYG input box is terrible
by ikornaselur on Thursday November 21, 2019 @06:03AM
(#21593019)
Interestingly, if I do that, it will then send it unformatted. I want to format in the actual chat, just not in my input.