Over at TAONAW, JTR has a short post post on how his changing work duties—that now include more technical writing—has caused him to evolve his Emacs workflow. A lot of his work involves writing Knowledge Base articles that get added to the ServiceNow platform.
Of course, being an Emacs user, JTR wants to do his writing in Emacs and then import it into ServiceNow. He did this by exporting his Org document to HTML and using a browser to paste it into the ServiceNow platform. Apparently Service Now is not very forgiving about its input so JTR had to tweak his Org headers to get acceptable HTML to import.
The real problem, though, was getting changes made within ServiceNow back out to Emacs. There doesn’t seem to be a good way to do that so JTR was reduced to manually copying the changes back to Emacs.
The big takeaway for me in his post was the ends that an Emacs user will go to to do their work within Emacs. I can sympathize. I’m also willing to jump through some hoops just so that I can do my work in Emacs. Once you’ve been spoiled by an Emacs workflow, it’s hard to use anything else.