Word of warning about fake email addresses - if your system suddenly does start to send out messages to them, you'll start getting otherwise mysterious email messages back about being unable to deliver and other such comments.  I speak from experience - although in my case the puzzle was finding what was generating the messages in the first place (not elog, another program as it happened).

I suggest you also include

Suppress default = 3

in your configuration file, which also stops them being generated in the first place. 

Although I was unaware (or had totally forgotten) that there was a 'Suppress email button' as mentioned in the documentation.

I use plain encoding, cannot answer for the others but it should do the trick as it's in the documentation.  I'm using Firefox some large number and 2.9.2.-2475

I do what I believe you want, and get it by having the following line in my config file for that logbook (which is part of elog.cfg):

 Prepend on reply = \n

This gives a blank line at the "top" of the entries when you start a reply, and all the previous entries gain another "> " unless you've also altered that default behaviou (as in fact I have).  The result then looks like:

Latest line of text

> Previous entry

> > Previous entry to that

 I use elog's built-in ticketing system, and use the auto-generated ticket number to cross-reference with other matters/documents/files.  Much of the documentation for tickets is rather buried away under Subst <attribute> = <string>.

I've not found a way to link from an entry to a set of entries in another thread by their ticket number, particularly across more than one logbook.  [This is possible via their elog entry number, and which logbook it is in].  The former would be usefil to cross-reference an incident which you identify external to the elog system - "Oh, it's another one like [Ticket no] NOV12-001" possibily easier than "Oh it's another one like elog:archive12/67142 ".  Oh, the last bit should be highlighed as a (non-existant) link here, to show my point, nice of the ticket could be as well.

On the plus side, you can arrange the ticket number to show up in the thread display, quick search by ticket number, run different ticket colours (as it were) in different logbooks (i.e. different prefixes).  Just ensure you don't archive the latest entry, as that can lead to duplication of ticket numbers.

Message ID is the internal numbering of each entry.  It is the number that is used internally for generating the threads, and which you can reference with the elog:[message ID] code within an entry to cross reference the entry with that message ID.

"Ticket" is the name of an attribute.  You define the attribute "Ticket", and can preload the attribute with the format  you require(*).  In the following extract of an elog.cfg file are the relivent lines to generate tickets, show the ticket number in the thread display, search for a particular ticket, and allow it to be edited when writing an entry - there are reasons.  The attribute "Organisation" here is an example of another attribute you would enter with the initial entry, of course there will be others specific to your requirements.

Attributes = Ticket, Organisation, ...

Preset ticket = T#####

Thread display = $Ticket: $Organisation, ...

Quick filter = Ticket, ID

When you start an new entry, the Ticket attribute is prepopulated with a number.  The first time will be T00001, subsequently it will be one higher than the currently existing highest ticket number in the logbook.

Why might you edit the ticket number?  You may wish to go back and edit an old (complete) entry's ticket number so it has some obvious name - perhaps the solution of what proves to be a stock problem, that has become known by a pet phrase, so it can be found by searching for that phrase in the quick fillter "Ticket".  That is a more advanced use of the ticket system.

 (*) Further on the format of the ticket is in the documentation under Subst <attribute> = <string>

Sorry for multiple edits, why cannot I cross-reference an entry in this forum as I can in my local logbook?

 Hi Barend,

The counting of entries, or even "tickets", only works within a particular logbook.  If you archive a set of entries to another [archive] logbook, the archived set disappears from view of the original logbook.  Should that entry, from logbook to archive, be the *latest* thread, then there is the danger of over-writing message ID, Ticket No and the like.

My policy to prevent the problem is to archive only threads that are say (depending upon use) a month after last entry..

 In the documentation:

>In addition to the #'s one may specify format specifiers which are passed to the strftime function. This allows to create tags wich contain the current year, month >and so on. Once the date part of the attribute changes, the index restarts from one. The statement

>Subst Number = XYZ-%Y-%b-###

>results in automatically created attributes

of the form

>XYZ-2005-Oct-001
>XYZ-2005-Oct-002
>XYZ-2005-Oct-003

A little playing around with the %[Alpha character] s of strftime probably will  generate a format that will suit your requirement - to the second if needs be.

For example I've checked that

Preset Ticket = T%y%m%d%H%M%S#

Generates a ticket number T1302061705141 at that particular moment.

Unfortuately for this to work, you have to have the "#" suffix, which will add a trailling "1" at the end of every ticket (unless you generate two new entries within a second of each other).  There are plenty of ways to format all this available in strftime, and unless you keep changing the clock on your computer (which I am guilty of), the ticket numbers can be as unique as you care to make them, and sequentially increasing.

Having said that, I share the view with Stefan that the problem is moving a thread or entry to another logbook rather too early.  Personally I keep a thread in the current log book for at least a month after it is "closed" before I move it, although partly that's because sometimes these threads come back to life.  Although also because I ran into the same issue (moving the latest entry and finding the ID duplicated), and, realising the problem, then took the "wait" option to solve it..  

> > Hi all, 
> > 
> > Is it just my system or do others have this odd issue.
> > 
> > I have a pdf file which is 'upside-down', I attached it to an elog entry, and the .png image thumbnail was
> > generated.  Now this too was upside-down, so I tried to use the left (or right) rotation buttons along the top
> > of the image in elog to do a 180 degree rotation.
> > The first 90 degree rotation was fine, but the second attempt just made a smaller image.  
> > It happens with various pdf files generated by various software (in case).
> > I also tried it with a jpg file, in that case the second attempt enlarged the image.
> > 
> > I could not find any way to actually invert the .png image using elog; but I was surprised that a second
> > rotation ddid something different (change magnification) rather than nothing at all if it could only cope with a
> > 90 degree rotation.
> > 
> > It's not a vital fix for me, but I have found the thumbnail (png) manipulation functions have a few rough edges,
> > so when necessary I use xv or gimp on the .png file to get what I want.
> > 
> > Or is this just my system?
> 
> I just tried on the demo logbook:
> 
> https://midas.psi.ch/elogs/Linux+Demo/14
> 
> and it worked fine in rotating the image twice. Can you try yourself and find out if it's related to your installation if ImageMagic, or the actual image file?
> 
> /Stefan

Hi Stefan,

Well I didn't crash the server this time, and I could invert the image in the demo logbook by doing two rotations.
But, this is elog v2.9.0-2435, and I am using v2.9.2-2475.  And I remember there was a recent issue about the image manipulation at some point, so I went to the
download section to read the subversion listing to find where this occurred.  But you've changed subversion!  I couldn't find my way around it, so I not only could
I find the changefile that showed what happened for each subversion issue, but even how I could download the current (or indeed any past) subversion issue.

As far as I can recall, you made a change, I reported an issue, and you undid the change, or partially undid it.  Do you know when this was?  Could it be relivent?

 It's probably not of much help, but for a short time I ran two elog daemons on the same linux box, using different ports.  It was thus able to run with two separate elogd.cfg files.   This is linux, and heavily biased to my eccentric way of running this linux box, but started them as:

/usr/local/sbin/elogd -p 8080 -c /home/logbooks1/elogd1.cfg -d /home/logbooks1

/usr/local/sbin/elogd -p 8081 -c /home/logbooks2/elogd2.cfg -d /home/logbooks2

Do note that as I was the only user on that linux box, I didn't have login etc.

However, I was soon asked questions by Andreas as to how I found this running, as he had encountered problems with an earlier version.  To be honest, that stopped me experimenting too far with this at that point, as well as a coincidental upgrading of my hardware.

But I was doing this *not* because I had to run two separate elogd.cfg files, but other reasons which meant splitting into two at that time vastly improved the performance of elog on the linux box at that time.  So while I didn't actually enounter any problems in doing so, I only have limited experience - and, of course, absolutely none on running even one [windows equivalent of a daemon] on Windows.

I am assuming here you have good reason for two separate elogd.cfg files, rather than just wanting to run two separate logbooks - guessing here, but one set public (no login) and one set private (with login)?