Re: Change / List Change doen't work anymore?, posted by Harry Martin on Tue Dec 1 02:12:14 2020
|
[quote="Stefan Ritt"][quote="Holger Mundhahs"]Hello @all,
I'm not sure if this is a bug, but after upgradeing from 2.7.0 to 2.7.7 the Change <attribute> and List Change <attribute> doesn't work anymore. In my |
|
Re: Change / List Change doen't work anymore?, posted by Harry Martin on Tue Dec 1 02:39:45 2020
|
[quote="Harry Martin"][quote="Stefan Ritt"][quote="Holger Mundhahs"]Hello @all,
I'm not sure if this is a bug, but after upgradeing from 2.7.0 to 2.7.7 the Change <attribute> and List Change <attribute> doesn't work anymore. In my |
|
Re: Change / List Change doen't work anymore?, posted by Harry Martin on Wed Dec 2 00:43:31 2020
|
[quote="Andreas Luedeke"][quote="Harry Martin"][quote="Harry Martin"][quote="Stefan Ritt"][quote="Holger Mundhahs"]Hello @all,
I'm not sure if this is a bug, but after upgradeing from 2.7.0 to 2.7.7 the Change <attribute> and List Change <attribute> doesn't work anymore. In my |
|
Re: Duplicate entries, posted by Harry Martin on Wed Dec 2 04:07:57 2020
|
I find that I can reply to a message ("original" message, if you will) without doing anything to the reply message (the "copy" of
the original message, if you will). If I then submit it, it gets saved as a new message, identical to the one I replied to.
I read through the options at the end of the docs. I did not see anything about a way to suppress identical messages, or a way to force |
|
Re: Duplicate entries, posted by Harry Martin on Wed Dec 2 17:54:51 2020
|
I was only commenting on the predicament as I have run into it also. I have required fields, but short of some sort of "abort" control
(curiously missing from the otherwise vast offerings of elog), I don't see any way to ensure that identical replies don't occur in any circumstance
that may arise. |
|
Re: Duplicate entries, posted by Harry Martin on Wed Dec 2 22:13:52 2020
|
David
Pilgram wrote:
Hi Harry, |
length of condition names, posted by Harry Martin on Wed Dec 2 22:45:16 2020
|
The documentation describing the use of conditionals uses a single character (letter or number) for names of conditions. I don't see any update/change
to that rule anywhere in the docs.
I have been using multi-character condition names successfully. I find these are easier to use since they can be more descriptive |
|
Re: Options <...> vs ROptions <...>, posted by Harry Martin on Thu Dec 3 01:51:49 2020
|
Same problem here, in version 3.1.3. It would be very nice if this worked.
Wolfgang
Bayer wrote:
According to section "Syntax of elogd.cfg" of the "Administrator's |