slash commands are a must-have
Slash commands for just about every type of function are a must have. They are familiar and easy to use without having to touch your mouse, they are UI-agnostic. Admittedly not terribly discoverable – but the UI is even worse, as their is no real option for auto-completion of UI elements, now is there?
We’re updating our command library all the time, so keep checking the menu in the command box to see what’s new by typing / or @.
The whole point of using the keyboard for commands is to not have to move your **** mouse up to the search box. COME ON, the entire point is missed. Please take the time to think about why you are adding a feature.
John Carney commented
Command bar for slash commands, a chat window for just the chat is tedious to use and very unitituive. There needs to be a single point of control for the interface. It's not as good as slack.
Johan Schmidt commented
It is fantastic! Slash commands in a separate box! Why?
Using Mac OS where someone "forgot" to add shortcut keys https://microsoftteams.uservoice.com/forums/555103-public/suggestions/18718825-macos-shortcuts-and-keyboard-interactions
You can now use FIVE tab strokes to move to the new Command box put in your /Command and the push TAB twelve more times to come back to the chat box. Amazing job, congrats to all great thinkers at MS ;)
Ajith Ramakrishnan commented
Just like how we could easily build custom slash commands in Slack, we should be able to do the same in Teams. And I totally agree with everyone else that the slash command should work from the chat box and not from elsewhere.
Why this was not just implemented into the chat box is beyond me. Teams was built after the rise of Slack, how could you not copy some of the fantastic things they do? I can't help but feel like a chat addon for VS Code would just be a better overall outcome. Dev is faster, new features make sense, everything actually works...
Almost there... but not quite :P
Not what I was expecting. The command bar is not the place for slash commands, this should be inline with the chat.
Jo Rhett commented
If you read the list of slash commands from anything which implements them, they are overwhelmingly channel-specific. So putting MS-specific commands in the command bar requires us to use the mouse to get to the command bar, and then doesn't provide us with anything that was requested.
The need was not to have some new commands that do completely different things than existing slash commands that happen to start with a slash. The need was to do things within a channel without taking your hands off the keyboard.
We asked for a car, you gave us a donkey on wheels. While a wheeled donkey is novel, the donkey doesn't go 100kph on paved roads without fresh water.
This feature is not satisfied, even partially, and won't be until you meet the requirement clearly listed in the initial description WITHOUT HAVING TO TOUCH YOUR MOUSE.
And before you say "you can hit tab" test it yourself and realized that HITTING TAB 28 TIMES TO GET FROM A CHANNEL TO THE COMMAND BAR ain't what we are looking for.
The the command box should be removed while the functionality of the command box should be moved to the chat box. The purpose of the slash commands is to not have to use the mouse.
Needs to be in the chat box. Simple.
David Millar commented
Slash commands in the search bar are too far out of reach from the rest of the UI to be useful. They ought to be in the chat area instead.
What, slash commands only work in the search box? Move the command to the chat box, and make /s the search command. I think someone hasn't figured out why slash commands are wanted in the first place. Hint: it's because we don't want to move our hands away from the keyboard.
Ben Mueller commented
Slash commands need to be in the chat box. Having a separate command box is unacceptable. Teams has to be fast, and needing to click into a different box means it's slow. Please fix.
The command box should stay there, but renamed to the Search box and that is where you go for searching the Teams app.
I WANT to move to Teams from Slack, but I can't roll it out until you get real slash commands working, it's THAT important.
/commands need to be in chat - not a secondary field.
Come'on... Slack/Hipchat/Flowdock/Mattermost etc. knows this.
Even terminal based IRC-clients from 1990's had this figured out
Comming from Slack and Mattermost, having the commands translated to my OS locale is a major turn-off!
I would prefer having commands in English, unless I explicitly ask otherwise.
Same reason why I dropped Excel in favour of GoogleDocs/LibreOffice/OpenOffice/CSV files
Adam Fasl commented
This is a real conversation we just had in Hipchat
[9:26 AM] Team Member A: I can't believe Teams still doesn't have /giphy or @giphy
[9:26 AM] Team Member A: They're missing out on so many customers
[9:26 AM] Team Member A: Like us
[9:26 AM] Team Member B: haha
[9:26 AM] Team Member B: We can just go to Discord :p
[9:27 AM] Team Member A: I really want to use Teams
[9:27 AM] Team Member A: It has so much stuff that is awesome
[9:28 AM] Team Member C: this company would fall apart without the gifs
[9:28 AM] Team Member B: lol
[9:28 AM] Team Member A: It has a gif button, but not as fun as /giphy
[9:29 AM] Team Member A: I'm aware that you would all quit
[9:29 AM] Team Member C: its really the randomness that sells it...
Adam Fasl commented
The new update doesn't cut it. The slash commands need to be in the chat. Such as /giphy /weather /lmgtfy
The current implementation is really cumbersome. When I saw the bar in the blog post I expected a behavior more like Visual Studio Code. Having an additional textbox just for typing a command is totally missing the point.
Still waiting on an update for the Slash Commands. I hope the Teams team understands how much I miss my s/. Please hepl bring by joy back.
s/joy back./joy back. My heart is slowly turning black.
/remind For the love of all that is holy