You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Could it be changed as a setting? Or add a path detection if the command appears like a path string, then send directly. Now I always end up with copying and paste path (on linux or macOS) and input words. But the "No such commands" only contains the "path" part. The following words are lost, not in the notification message, which is annoying.
Steps to reproduce:
paste some path like /home/user/.ssh/id and enter message for others afterwards like "you should use this path"
Expected behavior:
Add an auto detection of path string and send the message directly. Or at least include the whole message in the "No such command:" warning
Actual behavior:
the notification message is "No such command: /home/user/.ssh/id" the following message "you should use this path" is lost
Server Setup Information:
Version of Rocket.Chat Server: 3.7
Operating System: Ubuntu 16.04
Deployment Method: docker
Number of Running Instances: 1
DB Replicaset Oplog:
NodeJS Version:
MongoDB Version: 4.0
Client Setup Information
Desktop App or Browser Version: 3.0.5
Operating System: Ubuntu 20.04
The text was updated successfully, but these errors were encountered:
Thanks. Sorry I can' t upgrade it frequently since it is a enterprise deployment. I tested it in https://open.rocket.chat/ ( does it run latest?) and the issue is the same as I described.
Description:
I saw #3697.
Could it be changed as a setting? Or add a path detection if the command appears like a path string, then send directly. Now I always end up with copying and paste path (on linux or macOS) and input words. But the "No such commands" only contains the "path" part. The following words are lost, not in the notification message, which is annoying.
Steps to reproduce:
Expected behavior:
Add an auto detection of path string and send the message directly. Or at least include the whole message in the "No such command:" warning
Actual behavior:
the notification message is "No such command: /home/user/.ssh/id" the following message "you should use this path" is lost
Server Setup Information:
Client Setup Information
The text was updated successfully, but these errors were encountered: