search for: eol

Hello All, R 2.11.1 Windows XP, 32-bit Help says that default is eol=''\n''. To me, that represents Linefeed (LF) >From Help: eol the character(s) to print at the end of each line (row). For example, eol="\r\n" will produce Windows'' line endings on a Unix-alike OS, and eol="\r" will produce files as expected by M...

I'm curious about the estimated EoL date on 6.2-RELEASE. Current estimate is listed as Jan 31 2008. That's just about 5 months away now. Suggestions for those who are about to be EoL'ed? Thanks.

...ollowing problem: I use R to issue a system call the execute a command in the OS. For example: system("DOSOMETHING TOSOMEFILE") In most situations, this task completes successfully and control returns to R. However, in rare situations, the target file (TOSOMEFILE) is missing an EOL character in its final line. In that situation, the task DOSOMETHING hangs and control never returns to R. Exiting R requires that I kill the process. I believe that a solution would be to add an EOL character to the final line of the target file before executing DOSOMETHING. I presume...

...ffff cx88[0]: cmds: risc pc : 0xffffffff cx88[0]: cmds: iq wr ptr : 0xffffffff cx88[0]: cmds: iq rd ptr : 0xffffffff cx88[0]: cmds: cdt current : 0xffffffff cx88[0]: cmds: pci target : 0xffffffff cx88[0]: cmds: line / byte : 0xffffffff cx88[0]: risc0: 0xffffffff [ INVALID sol eol irq2 irq1 23 22 21 20 19 18 cnt1 cnt0 resync 14 13 12 count=4095 ] cx88[0]: risc1: 0xffffffff [ INVALID sol eol irq2 irq1 23 22 21 20 19 18 cnt1 cnt0 resync 14 13 12 count=4095 ] cx88[0]: risc2: 0xffffffff [ INVALID sol eol irq2 irq1 23 22 21 20 19 18 cnt1 cnt0 resync 14 13 12 count=4095 ] c...

...g to handle UTF-16BE or UTF-32, because doing those would mean R would have to handle the translation of LF itself, and I'm too lazy to do that. So far this is working for writes, but not reads. I still have to track down what's going wrong there. Duncan Murdoch > > The default eol for write.csv (via write.table) is "\n" and always gives > as.raw (c (0x0d, 0x0a)), that is, <Carriage Return> <Line Feed> as adjacent > bytes. This is fine for UTF-8 but wrong for UTF-16 and UTF-32. > > EXAMPLE: Using UTF-32 for exaggeration (note also that 3 nul...

I've been using the mono-repo [ http://llvm.org/docs/GettingStarted.html#for-developers-to-work-with-a-git-monorepo] and this morning I ran into an issue where I am unable to submit using the mono repo. I traced this down to the fact that many files explicitly have the property svn:eol-style set to native. On the git side, we have core.autocrlf=false, which means that git will checkout as-is, commit as-is. So if a file has LF endings in the repo, git will check it out with LF line endings, and then on Windows, the local SVN clone will check out according to the value of the pro...

Hello, I'm new to R-help, although I am a frequent user of its resources. I am using the package REACTRAN to run some relatively simple transport modeling (which we hope will evolve greater functionality over time). I would like to optimize model parameters to match observed field data, and am interested in using UCODE_2005 for this, which our lab has previously used to great success. The

Thanks for looking into this. A few notes regarding all the UTF encodings on Windows 10 ... The default eol for write.csv (via write.table) is "\n" and always gives as.raw (c (0x0d, 0x0a)), that is, <Carriage Return> <Line Feed> as adjacent bytes. This is fine for UTF-8 but wrong for UTF-16 and UTF-32. EXAMPLE: Using UTF-32 for exaggeration (note also that 3 nul bytes are missing i...

On 30/04/2017 12:23 PM, Duncan Murdoch wrote: > No, I don't think anyone is working on this. > > There's a fairly simple workaround for the UTF-16 and UTF-32 iconv > issues: don't attempt to produce character vectors, produce raw vectors > instead. (The "toRaw" argument to iconv() asks for this.) Raw vectors > can contain embedded nulls. Character vectors

Peter wrote: > > What confuses me here is why would Red Hat rebase a package so close to > EOL. Now that they have they're stuck with either leaving a severly > broken firefox or providing a fix less than 6 weeks before EOL. I > honestly don't know which way they'll go here but it just seems to me > like it was a very poor decision to rebase firefox in RHEL6 so close t...

Dear R users, When dumping an R matrix object into a file -- typically via the 'write.table' function -- the 'eol' option can be used to specify the end-of-line character(s) which should appear at the end of each row. However the argument to 'eol' seems to be restricted to have length 1, whereas ideally I would like different rows to be written to file each with its own end character string. For...

...h mismatch at scanline 965 (got 2176, expected 1728). Fax3Decode2D: Warning, (FakeInput): Line length mismatch at scanline 967 (got 1730, expected 1728). Fax3Decode2D: Warning, (FakeInput): Line length mismatch at scanline 969 (got 2657, expected 1728). Fax3Decode2D: Warning, (FakeInput): Premature EOL at scanline 971 (got 1723, expected 1728). Fax3Decode2D: Warning, (FakeInput): Premature EOL at scanline 972 (got 1723, expected 1728). Fax3Decode2D: Warning, (FakeInput): Line length mismatch at scanline 973 (got 1729, expected 1728). Fax3Decode2D: (FakeInput): Uncompressed data (not supported) at...

...ing nfs-ganesha to storhaug was a huge change to be absorbed for a minor release version and was made bigger when storhaug does not appear to be ready go given the recommendation to go back and use 3.10. With the release of 3.12 ltm and now 3.13 stm, when 4.0 is released 3.10 is shown to be at eol; Version Status ???? Release_Date EOL_Version EOL_Date 3.10 ?? LTM ??? ??? 2017-02-27 ?? 4.0 3.11 ?? EOL ??? ??? 2017-05-30 ?? 3.12 ??? ?? 2017-8-30 3.12 ?? LTM ??? ??? 2017-08-30??? 4.3 3.13 ?? STM ??? ??? 2017-12-7???? 4.0 4.0 ??? Planned STM about 2018-01 4.1 4.1 ??? Planned LTM about 2018-04 n...

Hallo! I had ordered a Sipura SPA-3000 in the UK, but the supplier turned out to be unreliable and never shipped. Yesterday I went looking for alternative suppliers and found the Linksys SPA3000 device. It's a different box, but the specs look very similar. Is this the same device? Has anyone used this Linksys SPA3000 successfully with Asterisk? Thanks, Frank

Hi everyone, http://php.net/eol.php says that PHP 5.5 and 5.4 are EOL, but a freshly installed Centos 7 box, then fully upgraded, gives me PHP 5.4.16-42.el7. What do people do about maintaining current versions of software on a variety of machines? We have some users who manage their own machines, and would rather not force them...

Can anyone answer if we will get zfs de-duplication before SXCE EOL? If possible also anser the same on encryption? Thanks -- This message posted from opensolaris.org

...r be supported by the FreeBSD Security Team. Users of either of these FreeBSD releases are strongly encouraged to upgrade to FreeBSD 5.5, FreeBSD 6.1, or the upcoming FreeBSD 6.2 before that date. Discussion concerning FreeBSD releases which are no longer supported should take place on the freebsd-eol@freebsd.org mailing list. For an explanation of the rationale behind the EoL of FreeBSD 4.11, please see my earlier mailing list post on this subject: http://lists.freebsd.org/pipermail/freebsd-security/2006-October/004111.html The current supported branches and expected EoL dates are: +-----...

...r be supported by the FreeBSD Security Team. Users of either of these FreeBSD releases are strongly encouraged to upgrade to FreeBSD 5.5, FreeBSD 6.1, or the upcoming FreeBSD 6.2 before that date. Discussion concerning FreeBSD releases which are no longer supported should take place on the freebsd-eol@freebsd.org mailing list. For an explanation of the rationale behind the EoL of FreeBSD 4.11, please see my earlier mailing list post on this subject: http://lists.freebsd.org/pipermail/freebsd-security/2006-October/004111.html The current supported branches and expected EoL dates are: +-----...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Everyone, On June 1st, 21 days from now, FreeBSD 4.10 will have reached its two year End of Life and will no longer be supported by the FreeBSD Security Team. While some security fixes may be merged to the RELENG_4_10 security branch after the EoL date, the Security Team will only investigate new issues if they affect supported branches; consequently, the FreeBSD Security Team strongly recommends upgrading existing systems running FreeBSD 4.10 to a newer release. FreeBSD 5.4 had been planned to expire at the same time, but in light of delay...

Hi Everyone, Do we have an EOL date for version 3.6? I was looking into the Release Planning wiki and EOL is not yet defined. Thank you, Lester