search for: catcodes

Is this still an issue to this community? If so, and results, I may pick this up. Intel does have C++ and Fortran compilers. You might see a compiler among the list under the links http://cedar.intel.com/cgi-bin/ids.dll/topic.jsp?catCode=BON. Evaluation licenses are available at http://developer.intel.com/software/products/compilers/ If they are promising, perhaps binaries could at least be

Using versions 3.53 and 3.54, I get that message with the following configuration file (which is under 8192 bytes) on a USB stick; it's the configuration file from PCLinuxOS 2007. It was originally named isolinux.cfg; I changed isolinux.* to syslinux* for booting from USB. There is no blank line at the end of the file. It works well with 3.11, but that version doesn't allow me to put all

.../config/pdftexconfig.tex) (/home/travis/R-bin/texlive/texmf-dist/tex/latex/base/latex.ltx (/home/travis/R-bin/texlive/texmf-dist/tex/latex/base/texsys.cfg) ./texsys.aux found \@currdir set to: ./. Assuming \openin and \input have the same search path. Defining UNIX/DOS style filename parser. catcodes, registers, compatibility for TeX 2, parameters, LaTeX2e <2014/05/01> hacks, control, par, spacing, files, font encodings, lengths, ==================================== Local config file fonttext.cfg used ==================================== (/home/travis/R-bin/texlive/texmf-dist/tex/latex...

...uot;d:\Program Files\MiKTeX 2.7\tex\latex\base\latex.ltx" ("d:\Program Files\MiKTeX 2.7\tex\latex\00miktex\texsys.cfg") ./texsys.aux found \@currdir set to: ./. Assuming \openin and \input have the same search path. Defining UNIX/DOS style filename parser. catcodes, registers, compatibility for TeX 2, parameters, LaTeX2e <2005/12/01> hacks, control, par, spacing, files, font encodings, lengths, ==================================== Local config file fonttext.cfg used ==================================== ("d:\Program Files\MiKTeX 2.7\tex...

...t/tex/latex/base/latex.ltx > (/home/travis/R-bin/texlive/texmf-dist/tex/latex/base/texsys.cfg) > ./texsys.aux found > \@currdir set to: ./. > Assuming \openin and \input > have the same search path. > Defining UNIX/DOS style filename parser. > catcodes, registers, compatibility for TeX 2, parameters, > LaTeX2e <2014/05/01> > hacks, control, par, spacing, files, font encodings, lengths, > ==================================== > Local config file fonttext.cfg used > ====================================...

On 15 Feb 2009, I uploaded a patch to tkGUI.r that allows Linux users to load/save their workspace history from the GUI. There was no response, so I presume I did not submit the code correctly. What is the correct mechanism for submitting a patch/new feature to R? -- View this message in context: http://www.nabble.com/Patch-for-tk-GUI-tp23165645p23165645.html Sent from the R devel mailing list