> Could you implement a 'hide attribute' and 'sort attribute' config option?

I implemented it as 'hidden attributes = <list>' and 'sort attributes'.

> 'sort attributes' sorts the logbook entries when they are displayed.  Or?

Right

> What I want is to rearrange the entry mask.  E.g. if 'Entry type' article is
> selected then the attributes 'Author', 'Journal', 'Title', and 'Year' 
> should be listed first, as they are required for this bibtex entry type.
> Is it possible with the current elogd version to also sort (rearrange) the 
> attributes in the entry mask?  If yes, how?  

Attributes are shown in the order you specify them in the config file, so what about

Attributes = Entry type, Author, Journal, Title, Year     ???

> Only the sorting (of the entry mask!) is missing! :)

Ok, I put that on my wish list. So once the second or third person asks for it, I will
implement it (;-)

> I can export the Attributes I define easily and the Subject. Can't seem to 
> export the Entry Date and the Text fields.

The XML export contains both the Entry Date and Text fields. In CSV format,
it's hard to export the Text field since it can span several lines, which would
break the CSV format (one line per entry). Or do you know how multi-line
entries can be encoded in CSV?

> I can export the Attributes I define easily and the Subject. Can't seem to 
> export the Entry Date and the Text fields.

I added at least the date and message ID to the CSV export. New version under CVS.

> Have tried to use "Menu commands =" to list menu commands available as per:
> "Menu commands = List, Back, New, Edit, Delete, Find, Config, HELP, Logout"
> 
> but it does not seem to work; with command above I get default menu 
> structure.
> 
> Using:
> "Find Menu commands = List, Back, New, Edit, Find, Delete, Config, Logout, 
> HELP"
> 
> I get the menu I want.
> Q what's the difference?????

"Find menu commands" apply to the LIST of entries, while "Menu commands" apply
to the page where a SINGLE entry is shown. I know that "Find menu commands" is
a misleading name, but it's historical, I should change it to "Menu commands"
and change the other to "Entry menu commands", does that make more sense?

> If an attribute uses MOptions and is also extendable, clicking "Add 
> <attribute name>" and entering a value adds the value to the MOptions, but 
> does not put the value into the log entry. The log record has that 
> attribute blank.
> You have to go back into the record and edit it to put the new value in.

I fixed that bug just now, thanks for reporting it. It's available in revision
1.535 under CVS.

> I have a logbook with an attribute that has a number of fixed values. I 
> use MOptions to prevent typos when entering and allow multiple "keywords".
> When searching the users can only search on one keyword.
> Is there any way to search on multiple values (AAA|BBB|CCC)? If I do not 
> use MOption, they can do this, but the users entering logs may mistype the 
> keywords.

Even with Moptions, you can put into the "Text:" line

(AAA|BBB|CCC)

and click on "Search text also in attributes". This is a valid regular
expression with searches for AAA or BBB or CCC. Unfortunately you still can
mistype the values. If I would add check boxes in the find page, it would not
be clear if one searches for an "AND" of several values or an "OR" (Most people
would probably think that they want an "AND" because this happens if they
restrict several attributes).