search for: _names_

..."mailMessageStore" gave me the correct settings: -------CUT------- mbox: data=/virtual/oeush.at/home/f.someone/mail/:INBOX=/virtual/oeush.at/var/mail/f.someone.oeush.at -------CUT------- I don't have any of the LDAP RFCs ready, but I think that per default the case of the attribute _names_ should not matter when querying an ldap server. Udo Rader -- B e s t S o l u t i o n . a t EDV Systemhaus GmbH ------------------------------------------------------------------------ udo rader technischer leiter/CTO mobile ++43 660 5263642 ----------------...

Note the edited subject line! I don't know why I typed it as it was before. This says that as.numeric(as.character(f)) will work regardless of the implementation, and I agree. It's the recommendation to use as.numeric(levels(f))[f] that has me wondering about section 2.3.1 of the language definition. I expect that this idiom is in widespread use, and perhaps the language definition

Hi When I call for the loadings of my plsr using the command, x <- loadings(BHPLS1) my loadings contain variable names rather than numbers. >str(x) loadings [1:94727, 1:10] -0.00113 -0.03001 -0.00059 -0.00734 -0.02969 ... - attr(*, "dimnames")=List of 2 ..$ : chr [1:94727] "PCIList1" "PCIList2" "PCIList3" "PCIList4" ... ..$ : chr

Hello, I am trying to call R from Perl running on Windows 2000. I have looked through the previous posts regarding running R from Perl and all have referred to the RSPerl package at Omegahat. Unfortunately the documentation for this package specifically states that it only works in Unix at the moment. Does anyone else have any suggestions about the best way to do this in the Windows

Hi all, hope you having a nice day, I ahve this weird results with identical (probably I am not understanding correctly what it does ...) I have these two data frames and I issue : > identical(temp, temp1) [1] FALSE However, these data frames are Nx2 and when I issue: > identical(temp[,2], temp1[,2]) [1] TRUE > identical(temp[,1], temp1[,1]) [1] TRUE and the results from str >

...g conflicting modules > apart. Different file name extensions are relevant for the core module, "ldlinux.*". It is not going to be relevant for non-core modules, especially non-library modules. I am still hoping some day my (one year old) suggestion for optional alternative file _names_ for configuration files will be merged in the official Syslinux code, as part of the solution for multiple architecture support. That goes in the same direction as ldlinux using different file name extensions, and has no relation to the question about the other modules using the same c32 extens...

> > For a KISS troubleshooting, *all* the c32 files should be located > together, in the root of the filesystem, where syslinux.efi and > ldlinux.e64 (for EFI x86_64) should be located too. > I should clarify, just in case. In my previous email, when I mentioned "all" the c32 files, I actually meant all the c32 files that pertain to the adequate firmware's