![]() ![]() ![]() Responsibility to consult the organizations responsible for the desktop, testing, and/or production environments These decisions areīased upon the best information available as of the most current date. The VA Decision Matrix displays the current and future VA IT position regarding different releases of a TRM entry. TRM Technology, obtained from the vendor (or from the release source). The Vendor Release table provides the known releases for the For additional information or assistance regarding Section 508, please contact the Section 508 Office at Decisions Section 508 compliance may be reviewed by the Section 508 Office and appropriate remedial action required if necessary. The Implementer of this technology has the responsibility to ensure the version deployed is 508-compliant. This technology has not been assessed by the Section 508 Office. Prior to use of this technology, users should check with their supervisor, Information Security Officer (ISO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation. Users must ensure sensitive data is properly protected in compliance with all VA regulations. Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 61 VA Directives 6004, 6513, and 6517 and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). The technology supports scripting for programming languages such as HyperText Markup Language (HTML), LaTeX, C++, Java, Python, R, Perl, Ruby, PHP, and shell scripting language. More information on the proper use of the TRM can be found on theĪquamacs is an open source build of the Emacs text editor. Make sure you read the `Updating For El Capitan' document linked there especially the last section on creating the /Library/TeX/texbin link and the proper file in /etc/paths.d for pre-2015 MacTeX installs.Technologies must be operated and maintained in accordance with Federal and Department security and Please go to and read about El Capitan and MacTeX. That, of course, still was able to use /usr/texbin so /Library/TeX/texbin wasn't created since El Capitan wasn't even a ``glimmer in Apple's eye'' at the time. > Note: I see that you are using MacTeX-2014 (TeX Live 2014). > As I said, the problem was that the latex command in AUCTeX was changed from latex to pdflatex (don't know when?) and the pdf mode was selected so Aquamacs was trying to execute pdfpdflatex. > The only time we've seen problems with using that is if someone played with /etc/profile and eliminated the processing of the contents of /etc/paths.d. MacTeX-2015 installs a file in /etc/paths.d which sets /Library/TeX/texbin as part of the PATH variable. ![]() I didn't really know how to find it until Etore gave the incantation to me (haven't used emacs since the 1980s). ![]() So, that route will require people to upgrade their MacTeX install after installing El Capitan. > Aquamacs will pick up the /Library path in a future version, but not the /usr/local/texlive/2014 one. > export PATH=/Library/TeX/texbin:/usr/local/texlive/2014/bin/x86_64-darwin:$PATH > In that case I would suggest adding the following to their ~/.bash_profile script: > I suspect that their LaTeX isn’t available from the command line either. > On Oct 30, 2015, at 7:53 AM, David Reitter wrote: > On Oct 30, 2015, at 9:10 AM, Herbert Schulz wrote: My message was in response to your comment "Now, why are some other folks saying that Aquamacs isn't compiling LaTeX files for them under El Capitan? I'm getting these comments via the mactex-support list as well as personal emails from folks I've helped in the past.”. Previous message (by thread): Aquamacs & El Capitan.Aquamacs & El Capitan David Reitter david.reitter at ![]()
0 Comments
Leave a Reply. |