This problem has been fixed in the current version. Please get it from bitbucket.org. 

Ok, I tried updating my SVN working copy, but I didn't get any updates past elog rev. 2494, mxml rev. 74.  I undid my changes to Makefile, tried to compile, but got the same errors.  

I then pulled down elog and mxml with git, and these are working for me with no errors.  Thanks!

SVN is obsolete and will NOT be maintained any more, since we completely switched to GIT. Actually I will disable the service soon. 

> [13 Nov] > As my threads have lots of replies, I end up with a forest of ">" characters which makes it difficult to read > earlier quoted entries (what with word-wrapping of the browser). > I thought to replace the ">"s by a simple date entry prepended to the start of each reply. - much as I have > given at the top of this initial entry. > > So this is what I put in the config file: > > .... > Time format = %a %d %b %y > Date format = %d %b > Prepend on reply = [$date] \n > ... > > The time is used in the string for the Thread display. > > Only I don't get the date, with the date format, prepended to replies but the time, in the time format, as > > [Wed 13 Nov 13] > > Now this is hardly a disaster, but any ideas why the date formatting is being ignored?

https://midas.psi.ch/elogs/Forum/67405

Why all the > Characters?  Maybe back off the version as stated in above link?  Not sure about the date issue.

 I don't know what happened here - I mean, I understand the ">" characters being added to the start of every line of a quoted previous entry, but now what then happened to the formatting.

By default in plain mode elog adds ">" to the start of every quoted line, just as quoting an email will do (some mailer programs).

If you're beyond your nteenth reply, word-wrapping of the browser etc makes past comments difficult to read.  Of course it would be equally difficult in in html mode as the boxes would get more and more nested.

Not sure if your link here about html is relivent to the use of the ">" to indicate a quoted reply or not, although that wasn't really my question - which was about date format in the config file.

 I'm having same issue. Kerberos is working on Apache on same ubuntu 12.04 server. I used the USE_KRB5 option for compiling elog.

Does anyone  have an idea to solve that problem? 

Please read the documentation in https://midas.psi.ch/elog/config.html und the option "Use Lock". If you don't need locking, just turn it off.

> [13 Nov]
> As my threads have lots of replies, I end up with a forest of ">" characters which makes it difficult to read
> earlier quoted entries (what with word-wrapping of the browser).
> I thought to replace the ">"s by a simple date entry prepended to the start of each reply. - much as I have 
> given at the top of this initial entry.
> 
> So this is what I put in the config file:
> 
> ....
> Time format = %a %d %b %y
> Date format = %d %b
> Prepend on reply = [$date] \n
> ...
> 
> The time is used in the string for the Thread display.
> 
> Only I don't get the date, with the date format, prepended to replies but the time, in the time format, as
> 
> [Wed 13 Nov 13]
> 
> Now this is hardly a disaster, but any ideas why the date formatting is being ignored?

Hi David,
yes, a $date is substituted with the "Time format" in the function build_subst_list().
I guess that is a bug, but it could break many existing logbooks to change it.
I leave this to Stefan.

There is a simple solution for your problem: you can execute a shell command.

Prepend on reply = $shell(date '+[%d %b]') \n
Reply string =

That snipped will do exactly what you want :-) (of course you need to have the "-x" option to start elogd.)

Kind Regards
Andreas