> now the brave Emacs user of 2024 is forced to spend lots of time not in Emacs, thus defeating the point of using Emacs. If you can just get your email in Ema

> now the brave Emacs user of 2024 is forced to spend lots of time not in Emacs, thus defeating the point of using Emacs. If you can just get your email in Emacs, you can get a lot of integration you need. Luckily, email is still a must-have for many services. For things like slack, teams, etc... it's much much harder. Glancing at my "emacs for everything" roam node, I was last looking at utilizing matterbridge[0] to get access to teams, slack, etc by bridging to IRC. However, more ideal would be bridging to matrix especially if attachments/etc can be bridged over. Taking actions based upon notifications though all the way from beginning to completion, then using elisp to customize the process, is definitely where emacs has the most impact. Coworker pasted some code? You are reading it in an emacs buffer and have a function to open the code block at point in a python buffer with a repl split to the right to test it with no effort. 0: https://github.com/42wim/matterbridge https://github.com/42wim/matterbridge