Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 352 of 807  Not logged in ELOG logo
ID Date Icon Author Author Email Category OSdown ELOG Version Subject
  800   Thu Nov 18 09:40:25 2004 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux2.5.4-6Re: compiling elog on AMD64
> When compiling elogd on AMD64 (in 64 bit mode) there are many 
> warnings like these:
> 
> src/regex.c:3769: warning: cast from pointer to integer of different size
> src/regex.c:3769: warning: cast from pointer to integer of different size
> src/regex.c:3775: warning: cast to pointer from integer of different size
> 
> The reason is the (int) cast, which (I think) is not necessary.

Unfortunately I don't have a 64-bit compiler to try. Can you please check if
elogd.c has similar warnings or only regex.c? The ones in elogd.c I can fix,
but regex.c is straight from the GNU C library, so we would have to wait intil
they fix it. Or can you get it from the 64-bit C library? The point is that I
need the source code, so that I can compile it under Windows as well. Can you
try to compile elogd without regex.c, like 

gcc -g -O -W -Wall -o elogd src/elogd.c

If that works fine, we don't have to compile regex.c under linux. But I guess
it's still needed fot Solaris and other non-GNU Unix brands.
  802   Sun Nov 21 00:46:28 2004 Reply Heiko Scheith.scheit@mpi-hd.mpg.deBug reportLinux2.5.4-6Re: compiling elog on AMD64
> > When compiling elogd on AMD64 (in 64 bit mode) there are many 
> > warnings like these:
> > 
> > src/regex.c:3769: warning: cast from pointer to integer of different size
> > src/regex.c:3769: warning: cast from pointer to integer of different size
> > src/regex.c:3775: warning: cast to pointer from integer of different size
> > 
> > The reason is the (int) cast, which (I think) is not necessary.
> 
> Unfortunately I don't have a 64-bit compiler to try. Can you please check if
> elogd.c has similar warnings or only regex.c? 

  elogd.c shows the same warnings.

> The ones in elogd.c I can fix,
> but regex.c is straight from the GNU C library, so we would have to wait intil
> they fix it. Or can you get it from the 64-bit C library? The point is that I
> need the source code, so that I can compile it under Windows as well. Can you
> try to compile elogd without regex.c, like 
> 
> gcc -g -O -W -Wall -o elogd src/elogd.c

  This works OK.
 
  807   Wed Nov 24 00:44:09 2004 Warning Rich Persauddev2id at yahoo dot comBug fixLinux2.5.4-6Konqueror and Calendar widget
Date selection from the calendar widget does not work in Konqueror.  

Clicking on a date results in year being populated, but month and day are 
blank.
  815   Wed Nov 24 14:19:01 2004 Warning Stefan Rittstefan.ritt@psi.chBug fixLinux2.5.4-6Re: Konqueror and Calendar widget
> Date selection from the calendar widget does not work in Konqueror.  
> 
> Clicking on a date results in year being populated, but month and day are 
> blank.

I use following Javascript to populate the date:

function submit_day(day)
{
  opener.document.form1.d3.value = "24";
  opener.document.form1.m3.value = "11";
  opener.document.form1.y3.value = "2004";
  window.close();
}

which workes everywhere except in Konqueror. If you tell me how to convince
Konqueror to accept this, I'm happy to put it into the elog code.
  820   Thu Dec 2 14:39:50 2004 Question Heiko Scheith.scheit@mpi-hd.mpg.deRequestLinux implement 'hide attribute' and 'sort attribute'
Could you implement a 'hide attribute' and 'sort attribute' config option?
While sort is probably not so easy to do the hide option would already 
be very useful.  What I want to do is to use elog to collect bibtex entries
which are then used to generate a bibtex file.  So, e.g. if the entry 
type 'Article' is selected I would like that all fields that do not make
sense are hidden.  Currently I just lock them.  The config looks like
this:

Attributes                  = Login, Bibtex Key, Entry Type, Address,
Annote, Author, Booktitle, Chapter, Crossref, Edition, Editor, Howpublished,
Institution, Journal, Key, Month, Note, Number, Organization, Pages,
Publisher, School, Series, Title, Type, Volume, Year, URL, Short Comment
Options Entry Type          = Article{1}, Book{2}, Booklet{3}, InBook{4},
InCollection{5}, InProceedings{6}, Manual{7}, MastersThesis{8}, Misc{9},
PhDThesis{a}, Proceedings{b}, TechReport{c}, Unpublished{d}
Required Attributes         = Entry Type
; ARTICLE
{1} Comment Author          = [required]
{1} Comment Journal         = [required]
{1} Comment Title           = [required]
{1} Comment Year            = [required]
{1} Locked Attributes       = Address, Annote, Booktitle, Chapter, Crossref,
Edition, Editor, Howpublished, Institution, Key, Organization, Publisher,
School, Series, Type


Instead of Locking the attributes, hiding them altogether would make the
entry form look much nicer.  
A further improvement would be to sort the attributes, e.g. for author I
would sort the like this, i.e. the more important entries first:

{1} Sort Attributes    = Author, Title, Journal, Volume, Pages, Year, Month,
Number, Note

Attributes not mentioned in the sort line could then be displayed 
in any order. 
  840   Thu Dec 9 18:39:15 2004 Question auserauserQuestionLinux Anyone try doing majordomo->Elog?
Hi all,

We currently have Elog postings mirrored on to a majordomo email list. 
Invariably, people on this list reply to the listserv and not to the Elog. 
Has anyone tried getting emails to a listserv to autoformat and register as
proper elog entries.  Didn't see any mention of this in the docs or forums.

Thx 
  841   Thu Dec 9 19:22:12 2004 Question Qiangshijialeee@yahoo.comQuestionLinux form posting
hello, 

i need to use a perl script with LWP to automatically update our elog
entries. we use ELOG internally.

however, I am not sure what elog checks for when doing the post through
form. and the auto-submit script always failed and returns "200 EOF". i can
get to the login part and grab form entry. its only the submittion failed.

let me know if you need more info to help me solve the problem.

thanks.


QiAng
  842   Sun Dec 12 12:40:53 2004 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux Re: form posting
> however, I am not sure what elog checks for when doing the post through
> form. and the auto-submit script always failed and returns "200 EOF". i can
> get to the login part and grab form entry. its only the submittion failed.

What you can do is run the elog submit utility with the "-v" flag (verbose) and
grap the output. It's HTML code, but you should see any error message there.
ELOG V3.1.5-3fb85fa6