Re: Expanding column width when viewing in Summary mode, posted by David Pilgram on Sun Jul 19 13:14:36 2020
|
Anyone who knows me knows I (ab)use elog a lot. And this one is another of a long list of cheats and work arounds rather than modifying the
code properly.
In summary mode, the top row are titles, and if they are long, they will dominate the width of that column. Similarly if they are short, |
|
Re: Duplicate entries, posted by David Pilgram on Wed Dec 2 15:57:25 2020
|
I'm not sure if this is what you want.
If you want to prevent "accidental" replies being identical to the original message, you can force a situation where the user will
be alerted that they have to do something if they really want to make a reply. |
|
Re: Duplicate entries, posted by David Pilgram on Wed Dec 2 18:22:37 2020
|
Hi Harry,
I'm just an elog (ab)user, not one of the developers. My original 2017 reply was to report an issue that was due to hardware, but somehow
overcame a configuration flag (no multiple replies to a single entry), which might have been the same problem as the original poster, Alan Grant, was observing, |
|
Re: elog server go to high CPU and hangs, posted by David Pilgram on Thu Feb 18 12:05:52 2021
|
Dear Stefano,
Try the entry I wrote some time ago elog:68655
|
|
Re: Planned maintenance at the top of ELOG listing, posted by David Pilgram on Mon Nov 21 13:32:04 2022
|
The way to do this is to ensure that the date of the entry is in the future. As a hard -core linux (ab)user of elog, I create an entry, then dive
into the yymmdda.log files, and edit it so that the date at the top of the entry is, for example, Sat, 31 Dec 2022 23:59:59. Then, that entry will
remain at the top of the listings until the New Year. I do this very thing for the very same reason, i.e. to keep one entry at the top of the listings |
|
Re: Wikipedia Article deleted, posted by David Pilgram on Sat Jan 28 14:26:07 2023
|
I am rather with John on this.
I deliberately stopped contributing to Wikipedia years ago after I added an observation to an entry. That is, a piece of what could be
called original research. It was shot down in flames for being precisely that: original research. From what I read in the Draft:Elog |
|
Re: Maximum number of attributes, posted by David Pilgram on Mon Jan 8 15:56:40 2024
|
In my case, I had a number of attributes which had a varied prefix. For example, "progressed" , which could have no prefix, or prefix
"I", "To be", "Strongly", "Seriously"... and that was true (the same prefixes, or at least many of them) for a
number of attributes. Splitting them into two groups, the prefixes and the action, allowed me to gain more actual attributes without having to recompile. |
|
Re: Maximum number of attributes, posted by David Pilgram on Mon Jan 8 17:30:42 2024
|
Or what about the "ticket number" feature? Every new entry thread (sorry, confusing terminology on my part) would
increment the ticket number by one, and there is no limit as far as I am aware. This is all explained in the elogd configuration documentation.
Stefan |