I am trying to install and use LaTeX on my Mac. I have used it on Windows before without issue, but after installing MacTex when I try to typeset a document in pdflatex it comes up with an error, even though nothing has changed in the code from when I created it in Windows.
On my Windows PC I used TeXworks to edit, and MikTeX was installed. I feel like the issue must be that I don't have a particular package installed on my Mac but I don't know what it is. I tried to install MikTeX on the Mac but I can't download it, and I've been lead to believe that the MacTeX package should provide the same functionality.
This is the start of the code, and the point at which it appears to get stuck:
\documentclass[a4paper,12pt, twoside]{article}
\usepackage{geometry, graphicx,float,appendix, times}
\usepackage[font=small]{caption}
\geometry{
a4paper,
inner=30mm,
top=20mm,
outer=25mm,
bottom=40mm,
}
\renewcommand{\thefootnote}{\fnsymbol{footnote}}
\begin{document}
\pagestyle{empty}
...
This is the output that shows when I attempt to typeset[1]
https://i.stack.imgur.com/oQuHB.png
I'm afraid I'm really a novice with this sort of thing so any help would be appreciated!
The error message you show indicates that there is some error in the .aux file. This can for example happen if the previous compilation did not finish successfully or if one switches between tex distributions that might have different versions of latex and/or the packages.
Fix:
Delete all the auxiliary files and compile again
Today, I wanted to create a Setup file for Project in VS Community 2017. When I import file .sln in Advanced Installer 11.1. I receive notification from Advanced Installer.
Latest Version: Not my exertise, but off the top of my head: 1)The first thing you might want to do is to download the latest version of Advanced Installer (15.0.1 at the time of writing), to see if this solves the whole problem.
Language Issue?: If that doesn't solve things (which it just might do), then 2) I suppose this may have to do with the language. It looks like you have a Vietnamese VS project? That Advanced Installer project you show is set to "English" (look at title bar - it says "English US"). Maybe check the view "Translations". It does not look like Vietnamese is one of the supported, built-in languages for Advanced Installer (as of now). Towards the top right, select "All" in the "Show" box and select Vietnamese.
Path Issue?: 3) Perhaps also try to copy the VS project to a path which does not have Vietnamese character in the file and path name? Then try to run the import again.
VS Project Issue?: 4) Perhaps there are weird characters inside the VS Project that cause the problems? I guess there certainly are characters in there that are not normal, Western characters in your case.
Advanced Installer Community: That was just a couple of thoughts off the top of my head - essentially all about language and encoding, there could obviously be further issues. Also reminding you of the Advanced Installer Community Forums. Please try your luck there if you don't get any good answers here.
Some Links:
https://www.advancedinstaller.com/forums
I'm very new to LaTeX and its distributions so this might be a very newbie question.
I was following this tutorial and I'm not being able to compile the document. The code so far is very simple i don't think there are any typos and also I did not find a similar question in the forum.
can someone point me in the right direction ?
I'm using windows XP and I've installed TexMaker 4.4.1 found here
The code I have so far is simply:
\documentclass[11pt]{article}
\begin{document}
This is my first LaTeX document.
\end{document}
the error I'm getting is:
Could not start the command. pdflatex -synctex=1
-interaction=nonstopmode %.tex
Cheers !
If you meet the error:
Error : could not start the command
while executing TexMakerX commands in Windows 7 x64, it is probably due to environment path of LaTex compiler.
The following steps may help you solve this error:
Make sure that you did install a LaTex compiler like MiKTeX. You know, TexMakerX is just an editor of latex input, not a compiler.
Locate the bin directory in the installation directory of the LaTex compiler.
Add the directory of bin like d:\Program Files (x86)\MiKTeX 2.9\miktex\bin to the environment paths of Windows.
Right click computer in start menu, choose properties.
Find the "Advanced system settings" in upper left corner.
Click the button "Environment Variables".
Find the row of variable path in the group of "System Variables" and add bin path like ;d:\Program Files (x86)\MiKTeX 2.9\miktex\bin to the tail.
Remember to add a semicolon to separate different path.
Then, try it again...
I found this question on another forum and it says that you should install MiKTex for windows too. Worked like a charm !
I came across a page which mentions that MiKTeX has two major bugs due to which users haven't been able to compile at all.
Use TeX Live compiler instead
Source
https://wiki.lyx.org/Windows/TeXLive
Most of the time errors occur due to space in the file names. while saving the Latex file one should always remember don't put spaces in between the file name.
I want to write some short numerical programs in chapel. Can somebody just tell an IDE, or text editor which supports code highlighting for chapel (chapel-aware), is there an elisp-file for emacs? I don't prefer vim, even if a script for vim exists.
I tried searching, but I couldn't find anything. I neither know emacs-lisp nor am completely aware of chapel's syntax to configure it to make this chapel-aware.
the elisp files and .vimrc files ship along with chapel tar.gz file , so after extracting the tar.gz file in a folder chapel-version/highlight/vim or chapel-version/highlight/emacs there the vimrc or elisp files are present and in the README , instructions are also given how to add to init files ~/.emacs or ~/.vim.
I have just come across a plugin for the Atom Editor that does Chapel Highlighting
There is an Emacs mode for Chapel at MELPA. So if you are using an Emacs with package management you can just install chapel-mode.
https://melpa.org/#/chapel-mode
What solutions are there for working on a LaTeX document on both Windows and Linux?
It's a large document, and I will be working daily on both platforms so compatibility is essential if it's two different pieces of software.
Bonus points for a solution that includes easy previewing.
Writing text is not very different from writing software. Similar management techniques apply when scaling up.
Modularity: Split the document to smaller pieces e.g. a separate .tex file for each chapter. I also like to keep the preamble and other LaTeX set-up separate from the body text. My chapter files themselves just have the body text with some markup but do not define any new commands.
Source control: Keep all the source files in a version control tool such as subversion. Transfer files between systems using the tool.
Builds: Have a Makefile or similar to control the build process: it should be consistent and repeatable. Build regularly and fix build problems as soon as possible. If you want easy previews, you can set up a Makefile rule to launch e.g. a PDF viewer after the target PDF has been compiled.
Editing: Use whatever you're compatible with. It does not matter that much, though some good advice has been given by other answerers.
Communication: If there's more than one person working on the same stuff, no tool is a substitute for interpersonal communication.
TeXworks is a new cross-platform TeX editor with a built-in PDF preview that has source-output synchronisation. Click in the source to go to the matching part in the output, and vice versa. It's not the most feature-rich editor, by design, but the simplicity/power trade-off is just right, in my opinion.
I've used Emacs and its AucTeX mode, which is great for editing, as it has a set of very consistent shortcuts to insert many common commands and environments. There are also preview modes that display maths graphically in the Emacs window but I haven't used them.
As with VIM, there's a learning curve of course.
Unlike Legoolas, I'd advise for direct-to-PDF compilation using pdfTeX, but maybe Windows/Linux doesn't have a PDF viewer that automatically reloads the file? I'd be surprised if so (I use Skim on Mac). Check if your viewer supports synctex, as it's quite handy to navigate from PDF to source and back, without the cons of pdfsync.
To compile, my tool of choice is latexmk which is included in TeXlive. It completely automates the build, and can watch the .tex source to rebuild automatically.
Try LyX – The Document Processor, a "What You See Is What You Mean" editor for LaTeX.
Eclipse with its TeXlipse plugin should solve the IDE problem. More important are, however, issues like using only fonts that are available or installable on both platforms.
For previewing I am using Emacs with its Preview Latex feature in the AucTeX package.
For windows, you can use the TeXnicCenter, that is one of the best IDE for windows.
For Linux, you can use simply use Kile (it is possible to use kile with KDE on CygWin, but it is not the perfect solution).
There is no problem to switch from one IDE to another one (since you just save the .tex file and nothing else)
It also exists some cross-platform IDE, but I do not know them:
TeXmaker
TeXmakerX: a fork from TeXmaker
Since you'll probably not want to change text editor from whatever you usually use just for editing LaTeX docs (unless you use an editor which can't do syntax highlighting for LaTeX as well as whatever else you code/write in it), I'd recommend the simple following set of tools:
Whatever text editor you are used to, as long as it can highlight LaTeX markup. If it can't, then find a better editor for using with everything you do!.
Install MikTeX or TeXLive and just use the DVI viewer which comes with them by double-clicking on your DVI file. This will automatically update whenever the dvi file is changed by your editing of the latex file and re-creating the output.
I use Emacs as my text editor of choice, on both Linux and Windows. Setting up some scripts or makefiles to build the latex document when I hit a key is pretty easy, and fits in with everything else I use Emacs for nicely.
Other cross-platform options (many of which have already been mentioned by others in this thread):
LyX
TeXlispse for Eclipse
I've used VIM, combined with the VIM-LaTeX plugin, with great success. It does have a bit of a learning curve though.
Gummi is the best LaTeX editor. It is a free, open source, program written in python, featuring a live preview pane.
http://gummi.midnightcoding.org/
e4 http://gummi.midnightcoding.org/wp-content/uploads/20091012-1large(1).png
Get your work in some kind of version control system, then when you move from computer to computer you just update from a central server and its just like you left it.
It doesn't matter about the IDE, as you are saving just the .tex file, as noted above. If you want to use the same editor though, for the sake of coherency, use texmaker.
I use version control, and just use MikTex/WinEDT on Windows and TexShop on the mac.
IF your document doesn't compile on both, you're probably forgetting to keep the two directories synchronized or use funky commands, I like the sanity checks of knowing that it "compiles" cleanly on two platforms.
I use some text editor, and then I have a cron job that does a compile hourly from my source control.
Tex files are just text. I would recommend using a version control system (you should be using that anyway) to keep the source in sync. You can then use any (or different) editors on each system, e.g. Kile for linux and winEdt for windows. Both com with nice viewrs.
For a simple solution for the source control that just works with minimum knowledge and hassle, consider dropbox.
Revisiting my own question after quite a few years, I thought I'd add
https://www.writelatex.com/
not strictly what I had in mind, but have used it for collaborative writing
An excellent multiplatform LaTeX IDE is Texmaker.
For Debian or Ubuntu, I made a tutorial easy to follow: Install LaTeX on Ubuntu or Debian. This tutorial explains how to install LaTeX on Debian or Ubuntu and how to create your first PDF.