> > We use ELOG for our accelerator operation logbooks. As part of the shift handover every shift prints out all
> > entries made during the shift and files the printouts. If one entry in the shift was plain text without
> > appropriate linebreaks (like this one), then this screws up the printout: the whole window is scaled to the
> > width of this line and either the printout is cut off at the right side, or the whole content is scaled down to
> > very tiny scale, which makes it unreadable.
> > 
> > Is there a way to enforce line breaks in plain text entries?
> 
> Obviously there is: this logbook does add line breaks?!?
> 
> Maybe it is only a problem with entries made by the "elog" command?
> I'll find it out and re-post.
> 
> Cheers
> Andreas

Yepp, this is a (missing) feature of the elog command. Can you pre-process your messages outside of it, or do I have to add code to elog to do that?

Stefan

> > We use ELOG for our accelerator operation logbooks. As part of the shift handover every shift prints out all
> > entries made during the shift and files the printouts. If one entry in the shift was plain text without
> > appropriate linebreaks (like this one), then this screws up the printout: the whole window is scaled to the
> > width of this line and either the printout is cut off at the right side, or the whole content is scaled down to
> > very tiny scale, which makes it unreadable.
> > 
> > Is there a way to enforce line breaks in plain text entries?
> 
> Obviously there is: this logbook does add line breaks?!?
> 
> Maybe it is only a problem with entries made by the "elog" command?
> I'll find it out and re-post.
> 
> Cheers
> Andreas

Okay, I found two ways to add very long lines:
- if the very long line does not contain a space then this will screw the printout.
- if the line has been added as plain text using the elog command, there will be no line breaks added.

It would be nice if the elog command would have an option to break lines to a maximum line length.
But for the moment I'll just modify the applications that make use of the elog command.

> We use ELOG for our accelerator operation logbooks. As part of the shift handover every shift prints out all
> entries made during the shift and files the printouts. If one entry in the shift was plain text without
> appropriate linebreaks (like this one), then this screws up the printout: the whole window is scaled to the
> width of this line and either the printout is cut off at the right side, or the whole content is scaled down to
> very tiny scale, which makes it unreadable.
> 
> Is there a way to enforce line breaks in plain text entries?

Obviously there is: this logbook does add line breaks?!?

Maybe it is only a problem with entries made by the "elog" command?
I'll find it out and re-post.

Cheers
Andreas

We use ELOG for our accelerator operation logbooks. As part of the shift handover every shift prints out all
entries made during the shift and files the printouts. If one entry in the shift was plain text without
appropriate linebreaks (like this one), then this screws up the printout: the whole window is scaled to the width
of this line and either the printout is cut off at the right side, or the whole content is scaled down to very
tiny scale, which makes it unreadable.

Is there a way to enforce line breaks in plain text entries?

UPDATE:

After days of head banging and trying different syntax combinations, I finally stumbled on my own answer. It involved some syntax adjustments, and then splitting the task into these two consecutive operations:

      1. wget --no-check-certificate --cookies=on --save-cookies cookies.txt --keep-session-cookies -O e:\export1.csv "http://localhost:8080/demo/?uname=agrant&upassword=skipper"

      2. wget --no-check-certificate --cookies=on --load-cookies cookies.txt --keep-session-cookies -O e:\export2.csv http://localhost:8080/demo/?mode=CSV1

All is working fine now.

Is it possible to use wget to log into elog and export all of a logbook's data into a CSV file?

I can accomplish this perfectly when authentication IS NOT required by using:  wget --no-check-certificate -O e:\export.csv http://localhost:8080/demo/?mode=CSV1

However, I cannot accomplish it when authentication IS required by using:  wget --no-check-certificate -O e:\export.csv "http://localhost:8080/demo/?mode=CSV1&uname=agrant&upassword=skipper"

The latter appears to show that I've logged in, but the export file only contains a bunch of HTML tags, not the actual data as in the former.

How should I construct the wget command?

> I'm trying to send an email based on an attribute, in other words, a lookup and not $user_email of the author.
> 
> For instance, if I set a an attribute "Assignee" with a valid user full name (i.e. John Smith), I'd like to look up John Smith's 
> email address from the password file and send him an email. I can't seem to find it something like that in the docs, I can write 
> a script to do that, but was looking for a less cumbersom way of doing it. Thanks in advance.

Unfortunately such a feature is not implemented in the current version.

Stefan

> Did you ever get an answer or figure out how to preload Options from a CSV?


Only what is posted here in this thread.

Stefan