Synchronising

I use LFTP and I automate the synchronisation process after I exit my editor.

Differences from MediaWiki

TODO: Make a conversion script from the raw version, e.g. [1] into the markup language I use here. It seems easy enough to do, and that work would be the backbone of conversion scripts from various languages.

Also, if I support certain languages well, I could use other people's tools to convert to that base language and then my own scripting to convert from that base language to my own. Sweet.

For lists, I use a dash (-) instead of an asterisk (*).

Configuration

Editors

I use Geany for a number of reasons:

I already program in it.
1. Code folding
2. Syntax highlighting
3. Inline terminal
Fast
Spell checking

Any editor will do. However, there are some things to watch for:

Make sure your editor doesn't remove trailing spaces
- Otherwise you cannot have a <pre> block with empty lines, without resorting to using a space and   to create one.

Setting up a web browser

This is to let you easily open source files in an external text editor.

Setting up Firefox

This is a clusterfuck at the moment, and seems to be intentionally screwed up. It's changed a number of times and I'm only able to get what I want working because stuff I did a long time ago was grandfathered into the most recent Firefox. =( I'll have to revisit this issue another time, to help others with this problem..

[2] Firefox

[3] File types and download actions

[4] mimeTypes.rdf
- Edit > Preferences > Applications
- [5] What are MIME types?
- To find your mimeTypes.rdf directly, visit about:support

[6] Managing file types

Apparently you're expected to hack your mimeTypes.rdf directly.

I think what ended up happening is that I piggybacked asc on a pgp application to open using a text editor.

<RDF:Description RDF:about="urn:mimetype:application/pgp-signature"
                 NC:value="application/pgp-signature"
                 NC:editable="true"
                 NC:description="">
  <NC:fileExtensions>asc</NC:fileExtensions>
  <NC:fileExtensions>sig</NC:fileExtensions>
  <NC:handlerProp RDF:resource="urn:mimetype:handler:application/pgp-signature"/>
</RDF:Description>

I'm not sure though! To get a new profile working, I ended up just copying my entire mimeTypes.rdf from an old-and-working profile.

earlier stuff which did work but doesn't anymore

[7] Mime edit
- This was removed by its author. It worked at the time and the settings stuck.

MIME Type: text/ascii
Description:
Extension: asc

FIXME?: For unknown reasons, .txt doesn't work as an extension.

notes

[8] Force Content Type
- Was tested, but it's not needed.
Mozex
- Mozex does not respect accesskeys or pressing enter. I have to click with the mouse. So:

soh:///mnt/sda8/live/Projects/compiled-website/0.4.7/source/missing-index/missing-index.asc
.. becomes:
/home/user/soh:/mnt/sda8/live/Projects/compiled-website/0.4.7/source/missing-index/missing-index.asc
.. I am expecting
/mnt/sda8/live/Projects/compiled-website/0.4.7/source/missing-index/missing-index.asc

If you use NoScript then for some unknown reason JavaScript must be enabled for accesskeys to launch the local .asc links and summon the editor. Yuck.

Setting up Midori

Midori

It prompts to open the .asc file. Is there a way around that? I think that it thinks .asc is for PGP files.

It saves stuff to /tmp before opening it with an editor. So your changes are useless! Can that be changed?

A workaround might be to know about the /tmp and alter the various internal paths to fetch the file from /tmp when a change is seen. This seems needlessly complex.