> Hello,
> 
> I've had much success and use with ELOG.  However there is one thing that I wish I could figure out in order to 
> make ELOG work exactly as I need it.
> 
> When I either create a new ELOG entry, or, have one created via an automated scrip run by CRON, the paragraph 
> width is preset. 
> 
> I've read the notes and experimented with setting the text size, but it seems that if I either adjust it via the 
> config file, or, change the size by dragging the message box itself, then I end up with an ELOG entry that has an 
> irregular message size to it than all the others.  Consistency and uniformity is very important to me for how I 
> use ELOG.
> 
> It would be idea, if the log entries did not contain <CR>'s or justified lines.  In other words, I would like to 
> be able to have my ELOG entry fill the width of the screen, be it a wide screen or standard portrait scree, and 
> at whatever resolution and text size I have my browser set to.
> 
> By not filling the entire width (and also by not having it auto adjust depending on screen size, resolution, 
> etc.) there are large portions of the screen real estate that is lost and you end up with very long, scrolling 
> log entries versus entries that file the entire width and therefor take less vertical screen space.
> 
> With all that said -- Does anyone else have this issue?  And, is there anything I can do to correct this?  This 
> would make me a very happy user if it could be done.
> 
> Thank you in advance!
Hi Ryan,

Do you quote the previous entries in later entries, with the '>' character (as above)?  I ask this because that will
make what you are requesting much more complicated, soon making those previous entries very difficult to read
indeed.

For me, readabiliy of previous quoted entries is important - along with the indenting '>' character to denote each
entry - your request would be an issue for me simply because of how many times an entry may get re-quoted in later
replies - over 40 is not uncommon.  As such, I tend to keep my lines short when writing an entry, being aware
that it could soon have a large number of '>' characters preceeding it.

[Sep 03 07:30]
Not an aside as such, but I have tried to experiment with this quoting business, to remove the '>' character (easy
enough) but have each quoted reply headed with a simple date/timestamp *within* this text box, such as I headed this
paragraph.  It hasn't worked as I expected, and I'm not sure why - maybe it might even be a bug!  But if that
could be cracked, then your suggestion would be a boon to me as well.
 

 One hour adrift at this time of the year sounds like daylight saving.  Or compensation thereof.  What is your computer clock set to (not what time the clock reads)?

Personally I think it rather naughty that [at least older] Windoze automatically sets the clock one hour forward the first reboot after the spring switch forward, and the same in the autumn back.  What if you'd already done it, like all the rest of the clocks in the house?

I know two ways to do this. Either way you do need some kind of sysadmin status.

Stefan, Andreas, close your eyes for the next sentence.

1.  Set the computer/server clock to 5th October, make the entry, set the clock back again.

2.  Make the entry as normal, then go into the logbook directory and find today's 130912a.log entry - now create a new 131005a.log file, and paste in the relivant entry into this - not forgetting to change the day and date at the top.  Save the file.  Ensure that 131005a.log has the correct permissions and ownership (compare with all the other files) - you do mean you're using linux, didn't you.  Cannot answer for what to do/happen with Windows.

Now I too have this issue - there is one entry I want to keep at the very top of the list until a certain date has passed.  The way that Stefan/Andreas may offer probably will work, but I've never tried it - which is that the entry goes into today's log file, but has a "entry date" category.  I don't know if that would keep the entry at the top of the list until the 5th October has passed.  As I don't want to have an "Entry date" category, I resort to one of the two methods above.

The fact that the ID numbers become out of sequence doesn't seem to affect the performance of ELOG at all in my perhaps rather more extensive experience than the developers would have wanted me to try.

 Some computer programs/OS work with the computer clock as is.  Some make adjustment for Daylight Saving.  Some - Windows comes to mind, actually adjust the computer clock back and forth as Daylight saving ends and begins respectively.  I know this because I have a dual boot computer (I use windoze for AutoCAD and one other Windows-only Java based utility[!]), and when British Summer Time starts, my Linux automatically moves the screen clock forward.  But when I subseqently boot into Windoze, it sets the computer clock forward one hour, so when I then boot back into Linux, the clock is one hour fast.

I therefore suggest again you check what your computer clock *really* is, not what the OS reports it as being, as often they think they're being clever and automatically put in Daylight Saving.

Another test - Stefan and Andreas will be shuddering hard tonight - will be to set your computer clock to December, and see if the effect is still there or has disappeared.

 I cannot answer for Windoze, BUT there is more to this if you use Linux.

(Sorry for re-entry, I spotted a cut-and-paste error from first time around)

If you want to make a new logbook in linux manually, you need to do the following:

0.  Stop the elogd daemon.

1.  Edit elogd.cfg as Stefan said.  This will be in two parts - at the top, and then a block of entries which is what you normally see when you go to the "config" section of any logbook.  Easiest to copy and paste an existing block, only remember to put in a new header in the square brackets at the top - the name of your new logbook.  While most of the elogd.cfg is the same as in the documentation, the additional headers etc are pretty self-explanatory, and you only see these because you're editing the file raw rather than through the elog interface.  Once restarted, you can then edit the config for the new logbook in the usual way.

2.  Create a new subdirectory in your logbooks directory *with the same name* as the name you added in when editing elogd.cfg.

3.  Give that subdirectory the correct ownership and permissions.

4.  Only then, start elogd again.

As a windows user, which of the above you need to do: create the subdirectory (I imagine so) and/or anything else (I don't know).  I don't use Windows - apart from AutoCAD and one other javascript based program that non-the-less has windows dependancies (!).

David.

 On this linux box, using Firefox 12, if tabs are in use, Ctrl-Pgup/Ctrl-Pgdn goes throught the tabs.  If you force tabs off, then it goes through the entries.

Bavigation buttons work fine.

Hi Barend,

I can reproduce your point. 

I've found various work-arounds, but possibly the best one is to remove "Audit Date" and "Deadline" from the Required Attributes line.  True you won't get a warning saying that they were not entered for the first entry (if you didn't enter them, that is), but all subsequent replies run as you would want.

Another way is if you *preview* your entry, you can then submit it and that works.  This seems to work by bring up a different page where you can edit all those Fixed Attributes.  (I'm not sure that Preview is meant to do that, but it does and it's a work-around).

Or, if you remove "Audit date" and "Deadline" from the Fixed Attributes Reply (as you did) seems to work in the same way.  But I see that you don't want the opportunity for these to be changed.

I note that if you get this error message and go back, the message that you may have written is erased (this is unusual, it doesn't do this if you have not supplied an attribute on the first entry, say).

So I suspect this is a bug, possibly not detected before; perhaps no-one had tried this combination.

[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?