Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 298 of 808  Not logged in ELOG logo
    icon2.gif   Re: Suggestion additional ElCodes, posted by T. Ribbrock on Wed Jan 25 12:31:14 2006 

Stefan Ritt wrote:

Yes, I missed tables myself already. The headings I just put into the current SVN version (see this forum for how it works).


Very nice, thanks! I'm a bit torn as to whether I like the way I have to enter the level by keyboard or whether I'd rather see something like with the smileys (i.e. some "level menu" opens once "H" is pressed). The former is faster, while the latter doesn't require moving between the mouse and the keyboard. But that's just a detail - not really that important.


Stefan Ritt wrote:
Tables are a bit harder to implement and will come later. Do you have a proposal for a possible syntax?
[...]
Maybe somehting like

heading 1 heading 2 heading 3
data 1 data 2 data 3


this looks a bit like the "pipe" mode from a Wiki

what do you think?

Yup, I remember using that kind of "pipe" structure in Wikis and I actually liked it. I think it's a lot easier to read in the "source" as well - and it reminds me remotely of LaTeX... Wink Also, it doesn't require much to just type it out instead of using buttons to make the cells. Definitely good enough for the simple type of tables I had in mind!
    icon2.gif   Re: Substitutions in "Email all" do not work, posted by Stefan Ritt on Tue Aug 15 13:04:21 2006 

Ben Shepherd wrote:
Email All = $Cc


Substitution was not enabled for email addresses, but I added this for you. It's in SVN revision 1712 if you build elog yourself from the SVN, otherwise it will be contained in the next release.
    icon2.gif   Re: Substitutions in "Email all" do not work, posted by Ben Shepherd on Tue Aug 15 13:07:52 2006 

Stefan Ritt wrote:

Ben Shepherd wrote:
Email All = $Cc


Substitution was not enabled for email addresses, but I added this for you. It's in SVN revision 1712 if you build elog yourself from the SVN, otherwise it will be contained in the next release.


Great! Thanks very much. And quick too! Any idea when the next release will be available? Is there a mailing list I can sign up to to get notifications?
    icon2.gif   Re: Substitutions in "Email all" do not work, posted by Stefan Ritt on Tue Aug 15 13:09:18 2006 

Ben Shepherd wrote:

Stefan Ritt wrote:

Ben Shepherd wrote:
Email All = $Cc


Substitution was not enabled for email addresses, but I added this for you. It's in SVN revision 1712 if you build elog yourself from the SVN, otherwise it will be contained in the next release.


Great! Thanks very much. And quick too! Any idea when the next release will be available? Is there a mailing list I can sign up to to get notifications?


You are on the mailing list Wink, there is only this list. But you can check out the SVN version as described in the documentation.
    icon2.gif   Re: Subst variables and Execute, posted by Stefan Ritt on Wed Jul 21 16:38:05 2010 

soren poulsen wrote:

Hi

 

I am trying to use this line from the documentation:

Execute new = echo "New message wiht ID $message id of type $type from $long_name on $remote_host" >> /tmp/elog.log

It does not seem to have the intended effect (of printing a line with the message id, etc in the file /tmp/elog.log
)

How can I make this line work ?

Soren

Have you started the server with the "-x" flag as written in the documentation? 

    icon2.gif   Re: Subst variables and Execute, posted by soren poulsen on Thu Jul 22 10:17:29 2010 

Stefan Ritt wrote:

soren poulsen wrote:

Hi

 

I am trying to use this line from the documentation:

Execute new = echo "New message wiht ID $message id of type $type from $long_name on $remote_host" >> /tmp/elog.log

It does not seem to have the intended effect (of printing a line with the message id, etc in the file /tmp/elog.log
)

How can I make this line work ?

Soren

Have you started the server with the "-x" flag as written in the documentation? 

 Thanks a lot for replying despite the heat. Yes, I executed with the "-x" flag.

It is just a quoting problem, I guess. This line works:

Execute new = echo New message with ID $message id of type $type from $long_name on $remote_host >> /tmp/elog.log

It evaluates to:

SHELL "echo New message with ID 24706 of type elogtype from Soren Poulsen on 137.138.22.11 >> /tmp/elog.log"
 

So next step is to replace "new" with "edit" and "delete".

That works as well.

Soren

 

 

    icon2.gif   Re: Subst variables and Execute, posted by soren poulsen on Mon Jul 26 11:41:44 2010 

soren poulsen wrote:

Stefan Ritt wrote:

soren poulsen wrote:

Hi

 

I am trying to use this line from the documentation:

Execute new = echo "New message wiht ID $message id of type $type from $long_name on $remote_host" >> /tmp/elog.log

It does not seem to have the intended effect (of printing a line with the message id, etc in the file /tmp/elog.log
)

How can I make this line work ?

Soren

Have you started the server with the "-x" flag as written in the documentation? 

 Thanks a lot for replying despite the heat. Yes, I executed with the "-x" flag.

It is just a quoting problem, I guess. This line works:

Execute new = echo New message with ID $message id of type $type from $long_name on $remote_host >> /tmp/elog.log

It evaluates to:

SHELL "echo New message with ID 24706 of type elogtype from Soren Poulsen on 137.138.22.11 >> /tmp/elog.log"
 

So next step is to replace "new" with "edit" and "delete".

That works as well.

Soren

 

 

There is sometimes a problem with substitutions like "Execute delete = echo $message id".

It seems the problem is that if you delete a logbook entry that is not created with the current logbook attributes, the substitution variables are replaced with the variable name, and not the variable value.

In this example, according to the log file it becomes SHELL "message id" instead of SHELL "234", if the logbook entry is 234.

Soren

    icon2.gif   Re: Subst variables and Execute, posted by Stefan Ritt on Wed Jul 28 17:08:55 2010 

soren poulsen wrote:

There is sometimes a problem with substitutions like "Execute delete = echo $message id".

It seems the problem is that if you delete a logbook entry that is not created with the current logbook attributes, the substitution variables are replaced with the variable name, and not the variable value.

In this example, according to the log file it becomes SHELL "message id" instead of SHELL "234", if the logbook entry is 234.

Soren

I tried to reproduce it, but it always worked for me. So I need a step-by-step instruction from you on how to reproduce the problem, ideally starting from the demo logbook from the distribution. Only if I can reproduce the problem, I will be able to fix it. 

ELOG V3.1.5-3fb85fa6