I don't know what happened here - I mean, I understand the ">" characters being added to the start of every line of a quoted previous entry, but now what then happened to the formatting.

By default in plain mode elog adds ">" to the start of every quoted line, just as quoting an email will do (some mailer programs).

If you're beyond your nteenth reply, word-wrapping of the browser etc makes past comments difficult to read.  Of course it would be equally difficult in in html mode as the boxes would get more and more nested.

Not sure if your link here about html is relivent to the use of the ">" to indicate a quoted reply or not, although that wasn't really my question - which was about date format in the config file.

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

Hi David,
yes, a $date is substituted with the "Time format" in the function build_subst_list().
I guess that is a bug, but it could break many existing logbooks to change it.
I leave this to Stefan.

There is a simple solution for your problem: you can execute a shell command.

Prepend on reply = $shell(date '+[%d %b]') \n
Reply string =

That snipped will do exactly what you want :-) (of course you need to have the "-x" option to start elogd.)

Kind Regards
Andreas

> > [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?
> 
> Hi David,
> yes, a $date is substituted with the "Time format" in the function build_subst_list().
> I guess that is a bug, but it could break many existing logbooks to change it.
> I leave this to Stefan.
> 
> There is a simple solution for your problem: you can execute a shell command.
> 
> Prepend on reply = $shell(date '+[%d %b]') \n
> Reply string =
> 
> That snipped will do exactly what you want :-) (of course you need to have the "-x" option to start elogd.)
> 
> Kind Regards
> Andreas

Hi Andreas,

Thanks for this, I'll give the solution a go.  
I take the point that if it's a bug, other logbooks may be affected if it were fixed; but perhaps another
parameter - $thedate or something could be created instead?

In the past couple of days, I seem to have developed a problem with making entries into elog's displayed with Chrome (the latest, 31.0.1650.63) on 
Mac OS (10.9.1, the latest).  The problem occurs with attempting to edit or enter HTML encoded pages with fckedit; although pages render correctly 
in list mode, if you try to edit or enter an entry, the page is blank, the cursor is missing, you can't see text or type new text.  I ran elogd -v by hand, 
and there were no obvious problems, and I looked at the developer consoles in Chrome, and the only place I see any hint of what the problem might 
be is the Javascript console which says this:

event.returnValue is deprecated. Please use the standard event.preventDefault() instead.
Uncaught SecurityError: Blocked a frame with origin "http://localhost:8080" from accessing a frame with origin "chrome-
extension://pioclpoplcdbaefihamjohnefbikjilc".  The frame requesting access has a protocol of "http", the frame being accessed has a protocol of 
"chrome-extension". Protocols must match.
 fckeditorcode_gecko.js:36

It works ok in Safari, but it would be nice to use Chrome, and it was working ok until recently.  I don't think the problem occurred when I updated to 
Mac OS 10.9.1, but I don't keep careful track of the Chrome version.  It's not critical, but I pretty much exhausted what I knew how to debug.  I have 
close to the latest elog (2.9.2-2455), although I see the same phenomenon on this elog (.2.9.2-2475) and I think it's related to this thread:

http://productforums.google.com/forum/#!msg/maps/hQhwWA56NbA/2XL35dU7le4J

I tried the prescription in the October 22 entry, but it didn't seem to help, although I wasn't sure I had really tested it with compressed javascript and 
cache and what have you.

> In the past couple of days, I seem to have developed a problem with making entries into elog's displayed with Chrome (the latest, 31.0.1650.63) on 
> Mac OS (10.9.1, the latest).  The problem occurs with attempting to edit or enter HTML encoded pages with fckedit; although pages render correctly 
> in list mode, if you try to edit or enter an entry, the page is blank, the cursor is missing, you can't see text or type new text. 

That's strange. I just tried myself (by accident I have the same versions of Chrome and OSX) and it just worked fine. The fckedit code has not change a long time, so I guess it's not related to the exact version of 
elogd. Anyhow I want to switch to ckedit when I get some time, which maybe fixes the problem. What happens if you try to write in this forum, do you have the same problem? Sometime the fcdedit code take 
quite long time to load when accessed remotely. If your browser gives up, you might hat to click on "reload". In chrome there is also the "Developer tools" window, which shows you all HTTP requests and 
responses on the network. Otherwise I run out of ideas what could be different for you compared to me.

Cheers,
Stefan

> > In the past couple of days, I seem to have developed a problem with making entries into elog's displayed with Chrome (the latest, 31.0.1650.63) on 
> > Mac OS (10.9.1, the latest).  The problem occurs with attempting to edit or enter HTML encoded pages with fckedit; although pages render correctly 
> > in list mode, if you try to edit or enter an entry, the page is blank, the cursor is missing, you can't see text or type new text. 
> 
> That's strange. I just tried myself (by accident I have the same versions of Chrome and OSX) and it just worked fine. The fckedit code has not change a long time, so I guess it's not related to the exact version of 
> elogd. Anyhow I want to switch to ckedit when I get some time, which maybe fixes the problem. What happens if you try to write in this forum, do you have the same problem? Sometime the fcdedit code take 
> quite long time to load when accessed remotely. If your browser gives up, you might hat to click on "reload". In chrome there is also the "Developer tools" window, which shows you all HTTP requests and 
> responses on the network. Otherwise I run out of ideas what could be different for you compared to me.
> 
> Cheers,
> Stefan

Later on, I tried the prescription pointed to in that thread that says in scripts/fckeditor/editor/js/fckeditorcode_gecko.js to replace

FCKTools.FixDocumentParentWindow = function(A){ if (A.document) A.document.parentWindow=A; for (var i=0;i<A.frames.length;i++) FCKTools.FixDocumentParentWindow(A.frames[i]);};

with: 

FCKTools.FixDocumentParentWindow = function(A){try{ if (A.document) A.document.parentWindow=A;} catch(e){};for (var i=0;i<A.frames.length;i++) FCKTools.FixDocumentParentWindow(A.frames[i]);};

and after I got all my brackets straight, my pages were visible.  I'm still not sure when this turned up, since I use my elog every day (hour) and so I'd hardly miss it when I upgraded various things, although I don't watch Chrome updating itself that closely.

Have a good holiday!

Hello,

You put the "Language = german" statement into the logbook section, but it has to be placed in the [global] section as written in the documentation. Unfortunately this section of the configuration file cannot be accessed through the web interface, so you have to edit the elogd.cfg file manually, which might require admin rights.

Viele Grüsse nach Reken,
Stefan