I fixed that in revision 1.496 (see CVS).

> I

I implemented experimentally RSS feeds into Elog. Before releasing this new
addition, I would like to collect some experience with it. This forum now
supports RSS feeds, for which you can subscribe with a RSS feed reader like
Mozilla Firefox. Please give it a try and send me any feedback.

For an introduction to RSS feeds, please see 

http://www.webreference.com/authoring/languages/xml/rss/intro/

To subscribe to a logbook, enter following URL into your RSS reader:

http://<your-elog-host.domain>/<logbook>/elog.rdf

From the newest Mozilla Firefox browser, you can also click on the RSS box at
the lower right corner of the browser (see attachment).

> 1) elogd should report quota or disk-full problem:  In case a logbook           
>    entry cannot be saved (quota or disk full) then a message like               
>    'Could not save last entry.  Please contact administrator.' should           
>    be displayed.  Currently nothing happens.  Only the submitted                
>    entries 'vanish'.                                                            

That has been fixed in meantime.

> 4) mark messages as unread/read on a per user basis: The                        
>    implementation of this might be quite involved but it would be               
>    rather useful.  One way would be to add a default attribute 'Seen            
>    by' to each entry, which lists the login names of the users.  Or 
>    files LOGIN_NAME.has_seen can be created which contain the entry 
>    IDs of the viewed entries for each user.

There is an elegant way to achieve this already now: Use an RSS reader (like
SharpReader for Windows or Straw from Linux) and subscribe to a logbook. Then don't
read the entries directly in the logbook, but read them in your RSS reader. Once you
read them, they become automatically marked read.   

> 5) alignment of attribute table (using <td colspan=2> for multi line            
>    stuff): see elog:669 :)                                                      

Has been fixed as well.

> - Use "and" and "or" operands in queries                                        

Elog supports now regular expressions. So for a "<str1> OR <str2>" one can write

<str1>|<str2>

and for a "<str1> AND <str2>" one can write

<str1>.*<str2>|<str2>.*<str1>

Looks a bit complicated, but maybe some day we will get some code which rewrites
"AND" and "OR" as regular expressions.

> If I make changes to the elog source, How do I re-compile it and not 
> distrupt the program??????

There ist only a problem if you replace the currently running executable. You
sould first stop elogd, then replace the executable, then restart it. This ist
true both for Windows and Linux.

> If I make changes to the elog source, How do I re-compile it and not 
> distrupt the program??????

You first have to stop the running elogd server, then replace the executable,
then restart the server.

> 2) default page view per user, i.e. the 'Back' link goes to                     
>    ?mode=Full,summary,... depending on the user that is logged in.              
>    Some users complained that 'Back' is not really back.  Maybe                 
>    consider renaming 'Back' to 'Default View' or something.                     

I replaced the "back" link with a "list" link, hope that this makes now more sense.

> Is it possible to submit an entry with a html body using the elog client?

I added a "-H" flag for that. New version of elog.c under CVS and in the next
release.