exit status of elog, posted by Heiko Scheit on Thu Jul 4 17:09:09 2002
|
The exit status of elog is always 1. It should be zero for
a successful submission. |
|
Re: Participation on development of ELOG, posted by Heiko Scheit on Wed Feb 19 14:48:56 2003
|
> > We are interested in using your ELOG (which we consider to be a wonderful
> > application) even more. We would like to make a few adaptations in your
> > source code, above all to add some functionality that we are missing.
|
|
missing '.' in emails, posted by Heiko Scheit on Wed May 7 16:04:45 2003
|
missing '.' in emails
-----------------------
|
|
not proper HTML, posted by Heiko Scheit on Thu Jul 31 16:02:41 2003
|
I just upgraded from 2.3.5 to 2.3.9.
|
problem with boolean attributes, posted by Heiko Scheit on Fri Aug 1 13:18:42 2003 
|
Boolean attributes were not displayed correctly in version 2.3.9.
Patch is attached. |
|
width of the textarea is too large (after reply), posted by Heiko Scheit on Mon Aug 4 14:02:52 2003
|
The width of the textarea after pressing reply is too large.
The problem is that the algorithm that searches for the longes line
looks for the next '\r' which it does not find and therefore takes the
|
|
speed is very slow if logbook contains many entries, posted by Heiko Scheit on Wed Nov 12 12:25:44 2003
|
This is not really a bug, but elogd was getting really slow with our
logbook. It took about 4 1/2 seconds just to get the default page in
threaded mode with 15 entries. The logbook has in total about 2000
|
segmentation fault, posted by Heiko Scheit on Fri Feb 13 12:18:19 2004
|
Around line 2240 (in loc()) in elogd.c the following is written,
which results in an infinite loop, since loc() recursively with
|