At work I have cause to edit a TWiki that my team uses for internal documentation. I wanted to use Emacs for this task, so that I wouldn’t need to interact with a web browser text area widget. I couldn’t find anything that did that, so I took the closest thing I could find, erin.el, a TWiki markup mode, and added connectivity to it via Emacs’s url package.
The result is a fork of erin.el that supports these new operations:
| Log in: | M-x erin-log-in |
| Edit a topic: | M-x erin-edit-topic |
| Commit edits: | C-c C-c |
| Cancel edits: | C-c C-k |
| Log out: | M-x erin-log-out |
without ever leaving Emacs. Now with EWW to see the resulting pages, there’s no need to leave Emacs at all.
This being a fork, it doesn’t qualify for MELPA, and I can’t get in touch with the original author, so it will stay in limbo as a raw repo, without ever being packaged.
A while after I did this development, emacs-twiki-mode sprang up. It looks like it has some nice advantages, like orgtbl editing. If it used Emacs’s built-in URL handling instead of an external bash script I would probably switch to it. For now my erin.el fork works well enough for me. I do wish there were one monster Emacs mode that would handle all Wiki server implementations, including connectivity; a sort of Gnus for Wikis. Oh well.