A note about configuration options

Looking over the posts on the blog and a few e-mails I realized that some comments about the configuration file might be helpful.

The configuration system is in flux and has grown rapidly and organically, particularly over the last nine months. Oracc software can access the configuration file, config.xml, via several interfaces, and some of the programs ignore options that don´t apply to them while others complain about misunderstood or illegal options.

In general, if you see an error message about a configuration option, just check that you haven´t mistyped an option or value name. Otherwise, leave suspicious options in the config.xml because some program or other may be secretly using them.

If you change 00lib/config.xml you need to use at least:

oracc config

To update the installed version. You may need to do:

oracc web

Or even:

oracc rebuild

Before you see the effects of your changes.

After the remaining to-do list items are dealt with, the configuration system will get a complete review. Some things that cannot be configured in config.xml will be added (like the buttons SAAo uses); others will be documented; others will be rationalized as there are a few places where multiple options do very similar things.

I am also hoping (expecting, even) to create a web interface with an easy form for managing config.xml that has the documentation built in to it and drop-downs with the valid option values etc.

So, this pain with config.xml is transient. I am expecting to have the new configuration system in place by the end of September.

Directory names have changed!

If you are struggling to do project management through emacs, it may be because you are still using the old (CDL) directory names. For instance:

• old sources/ is now 00atf/
• old lib/ is now 00lib/
• old cat/ is now 00cat/
• old websources/ is now 00web/
• old backups/ is now 00bak/
  

See Project Management through Emacs for step-by-step instructions and Project Files for a more systematic overview.

As always, do ask for help if you need it, but I may not be as speedily responsive as usual over the next few days (up to and including Wednesday), as I'll be doing tablet work in Berlin. I will have broadband access in the hotel though, so I'll be checking in at least twice a day.

Logging in into Oracc for the first time

If you're trying and failing to login to your Oracc project for the first time since the move, the problem might have one or more of the following causes:

1. All project passwords were reset to the default on the move. Try logging in with the default (if you don't know what I mean, please email me) and then change your password to something more secure, by typing passwd at the prompt and then following the instructions. Your new password should mix uppercase and lowercase letters, and use non-letter characters too.
2. If you are running Win32Emacs, you need to trash your old atf-mode files before you install the new ones: see here.
3. Before you can use Emacs for project work, you will need to initialise the secure connection by following the instructions here.

If these three solutions fail, email me. (Steve is away until August now.)