Want to take part in these discussions? Sign in if you have an account, or apply for one below
Vanilla 1.1.10 is a product of Lussumo. More Information: Documentation, Community Support.
1 to 5 of 5
I’m a fan of editing files in my favorite local editor instead of the web browser. Therefore I wrote a tiny tool to be able to edit the nLab that way. In the off chance that somebody else finds this useful, it is available on GitHub.
I know that there are browser extensions which go a step in this direction, for instance wasavi for Chromium and Firefox. But I enjoy the convenience of not having to close the editor when clicking on “Submit” (instiki-cli pushes to the wiki in the background) and the safety of having an honest file copy in case the browser crashes.
instiki-cli doesn’t download the full wiki or something like that, it’s strictly for editing single entries.
Nice! I think I also have both of those advantages with Firefox itsalltext and emacsclient, though.
Ah, I didn’t know that was possible. I assumed that itsalltext would wait until Emacs is closed and then present a new Emacs window when re-editing the entry. (In contrast, instiki-cli pushes changes each time one saves the file in the editor.)
Itsalltext also pushes changes to the browser every time the file is saved.
For the record, itsalltext also saves an honest file in case the browser crashes. (But it does delete the file at some point, so it's probably possible to confuse it and lose the file.)
Another nice extension (although with significant slowdown on slow computers) is Lazarus, which saves form field entries. Every time itsalltext (or whatever) pushes a change to the browser, Lazarus will save a copy. Those are only deleted after some time has passed or some global limit of saved texts is reached (depending on your settings). It will also save your changes every few seconds (depending on your settings) if you don't use an external editor.
1 to 5 of 5