Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Slack’s new WYSIWYG input box is terrible

quuxplusone.github.io

Post reply on HN
Print view View original

851–860 of 1001 posts

Re: Slack’s new WYSIWYG input box is terrible

#851

Post by abbadadda »

samanthalee233 wrote: post #785
abbadadda wrote: post #169

Earlier quoted context omitted.

Atlassian Jira/Confluence SUUUUUCKS. They have given up on making anything better. I try to do as much as possible on Markdown files in a GitLab repo using Atom's Markdown preview (e.g., documentation). Gliffy diagrams are still OK.

GitLab employee here, nice to hear that GitLab is helping solve some of these workflow issues for you.

For sure! One thing to take a look at might be markdown numbering rendering in the browser. E.g., if I use `1. 1. 1. ` I only get ones, not 123 (last I checked).

Re: Slack’s new WYSIWYG input box is terrible

#852

Post by christefano »

sharken wrote: post #524
chris_wot wrote: post #502

Earlier quoted context omitted.

Given that Microsoft Teams is literally an existential threat, they really want to listen to feedback internally!

Not until Microsoft Teams gets the layout fixed, see https://microsoftteams.uservoice.com/forums/555103-public/su...

Thanks for the link. I’ll be watching it.

Out of curiosity, what do you think of the Stylish userscript that enables a compact mode in Teams and offers dark and light themes?

https://userstyles.org/users/727497

Re: Slack’s new WYSIWYG input box is terrible

#853

Post by [deleted] »

jsjohnst wrote: post #610
randunel wrote: post #498

Earlier quoted context omitted.

Why are you trying to track us? Please post non-tracking links https://exp-platform.com/Pages/HiPPO_explained.aspx

Any time I see a bitly link like that, I always copy rather than click and add a + to the end. I should make an extension to do it on hover I guess.

[deleted]

Re: Slack’s new WYSIWYG input box is terrible

#854

Post by CharlesColeman »

ailideex wrote: post #569
chris_wot wrote: post #502

Earlier quoted context omitted.

Given that Microsoft Teams is literally an existential threat, they really want to listen to feedback internally!

Microsoft Teams is pretty horrible

> Microsoft Teams is pretty horrible

Doesn't matter, since it comes with Office so it basically costs $0.

It's crap, but that's not stopping my employer from replacing literally everything they can with it. Even our desk phones, purportedly.

Re: Slack’s new WYSIWYG input box is terrible

#855

Post by christefano »

jsjohnst wrote: post #610
randunel wrote: post #498

Earlier quoted context omitted.

Why are you trying to track us? Please post non-tracking links https://exp-platform.com/Pages/HiPPO_explained.aspx

Any time I see a bitly link like that, I always copy rather than click and add a + to the end. I should make an extension to do it on hover I guess.

Good tip on adding the ‘+’ to the end. Thanks! To anyone wondering, adding the plus (when logged in to Bitly) displays an info page with the referrers (refererers) and locations by country.

And where the link goes to, obviously. No idea if this counts toward the Bitly link open rate.

Re: Slack’s new WYSIWYG input box is terrible

#856

Post by wickchuck »

criddell wrote: post #775
ailideex wrote: post #569

Earlier quoted context omitted.

Microsoft Teams is pretty horrible

It would be a great time for them to add markdown support and in the press release say we're listening .

It's been requested and denied. Still quite a few comments on it since I last posted tho. Go vote and get them to have a powermode to enter normal markdown with no WYSIWIG https://microsoftteams.uservoice.com/forums/555103-public/su...

Re: Slack’s new WYSIWYG input box is terrible

#857

Post by [deleted] »

pjscott wrote: post #108
Tade0 wrote: post #45

As someone who used to be part of a team developing one of the most popular in-browser WYSIWYG editors: 1. Browser WYSIWYGs are really hard to make. 2. All browser WYSIWYGs are terrible. Avoid rolling your own WYSIWYG if you can. Even if you have a team of 1500 people at your disposal.

Especially if you have a team of 1500 people. One person trying to make a browser WYSIWYG is bad enough; can you imagine how buggy it would be if 1500 people worked on it?

[deleted]

Re: Slack’s new WYSIWYG input box is terrible

#858

Post by jsjohnst »

Kalium wrote: post #828
jcsiracusa wrote: post #827

Earlier quoted context omitted.

Click the “Aa” icon in the WYSIWYG text input area toolbar to go back to the old non-WYSIWYG text input field.

I'm sorry to say, but this is incorrect. Clicking that button hides the strip of formatting buttons, but does not return to the old text input behavior.

EXACTLY! If hiding it restored the old behavior, almost nobody would be complaining.

Re: Slack’s new WYSIWYG input box is terrible

#860

Post by e12e »

dijit wrote: post #628
e12e wrote: post #576

Earlier quoted context omitted.

Sure it does: /edit (opens $EDITOR, in my case neovim). Link to wee-slack: https://github.com/wee-slack/wee-slack

TIL, that's amazing! :D EDIT : Turns out, I spoke too soon, there is no such option according to docs or from reading the code, maybe you have another plugin doing this? EDIT2 : found it: https://github.com/keith/edit-weechat

Whoops, sorry about that. I'll have to double check I was 90% that was standard in weechat or wee-slack - I've installed very few non-standard plug-ins.
Post reply on HN