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
Thanks for the heads-up about the issue with Slack.
Here's the deal:
Slack's input fields are a mess. Unlike Gmail or Github that use standard contenteditable elements, Slack's implementation is non-standard and doesn't play nicely with third-party extensions. It would need a lot of reverse-engineering and custom handling.
Since Slack is proprietary, any change they make could break our integration, meaning more time and effort just to keep it working.
Before I dive into this rabbit hole, can you tell me if you’d actually use Slack with this extension if I manage to get it working? Or are you just exploring its capabilities?
By the way, instead of trying to get this working, you might want to check out emacs-slack. Personally, I use a fork of it, isamert/emacs-slack, and it works like a charm.
Unfortunately, I’m unable to use any third-party Slack clients (such as Emacs) because, in the corporate environment, these are typically blocked.
Before I dive into this rabbit hole, can you tell me if you’d actually use Slack with this extension if I manage to get it working? Or are you just exploring its capabilities?
To be honest, I’m primarily exploring your extension. I currently use https://github.com/tecosaur/emacs-everywhere, which allows me to use Emacs from any input field at the OS level, including in Chrome or other apps like Slack. I was particularly interested in the sync feature of your extension, but I’m not sure if it would be something I’d continue using. Please feel free to prioritize this issue at the end of the backlog.
I've tried using it in https://app.slack.com/ but it doesn't work.
The extension opens a frame with this content:
I can see that new lines are synced to the text field conversation, but then, no content is added to the text field.
The text was updated successfully, but these errors were encountered: