![]() The helpful people at the tex stackexchanged recommended I posted here to see if anyone had an idea as to where the error is and/or how to solve it. Both work fine (minus the expected failures in context) individual, however the macro of latexmk then metapost gives that error. For diagnostic purposes I tried running through the custom macro just latexmk, and just the custom metapost. When I try to run that macro, it gives the oh-so-helpful error of "Error : could not start the command". I have tried configuring the metapost to sage %.sagetex.sage and then created a macro to run latexmk then metapost then latexmk then pdfviewer as per this post here. The problem comes when I try to configure the quickbuild to get Texmaker to run all of this at once. I also adjusted the latexmkrc file as per. Thus everything seems to be running fine. ![]() sage file within sage itself, and then recompiled in texmaker via pdflatex and got a fully configured file. I have run the example.tex file that comes with sage through the pdflatex, which generated the. I’m not sure if TeXstudio will be my LaTeX editor for the next 15 years, but I’ll use it as my main LaTeX editor unless something better comes along, and I will encourage my research team and coauthors to use it too.After some toying around I have gotten sage installed, and I have Texmaker installed. It is easy enough to manually run BibTeX, but it would be nice if the need to do so was detected more reliably. One bug I have found is that BibTeX is not always called when it should be. I also turned off ToolTip-Help which I found annoying. By default, F3 is linked to YAP for dvi files, but I never use dvi files anyway. The only customizing I’ve done is to map F3 to the “Find next” so it matches other software I use. I think it will also lead to far fewer requests for help. But for the sort of work I do, it has all the facilities I need. It is not as powerful as WinEdt in it’s macro capability, and it only handles LaTeX (so no good if you want to use TeX, ConTeXt, or some other variant). I won’t use these but they might be useful to new LaTeXers. There are also wizards for figures and tables. It works on Windows, Unix/Linux, BSD and Mac OS X įor beginners, there are lots of buttons to assist with fonts, mathematical symbols, etc. One click build process for LaTeX documents Tree view of document structure automatically created and highlighting my position in the document Īutomatically works with MikTeX with no configuration required Įrror list with automatic linking to the relevant line of the document Integrated pdf viewer with syncing in both directions So I’ve been looking around for another LaTeX editor, and after trying a handful of alternatives, discovered TeXstudio (previously called TexMakerX) which seems very clean and simple, but does everything I need. The last alpha 3 release was nearly a year ago. V2.0 is an improvement, but is very buggy and progress is so slow that I’ll be dead before it is released! It was announced in 2008, but there still isn’t a beta version. V1.0 is very cluttered and messy which drives me crazy. I tried TeXnicCenter for a while, the most popular freeware LaTeX editor for Windows. When I tri to quick build it, it says 'could not start the command pdflatex - synctext 1. so I tried my first documentclass and stuff and wrote a line between begin and end. When I try to compile a document that is known to be valid, I get: could not start the command pdflatex -synctex1 interactionnonstopmode. So I installed MikTex and I also installed TexMaker. Jeromy Anglim has a nice post on configuring WinEdt 6.0, but it should work nicely without needing this sort of configuration. Ive just installed MiKTeX and then installed TexMaker. If a new person joins our research team, there is always a hassle getting WinEdt configured for their use. These aren’t that hard to fix, but they shouldn’t happen. When a coauthor at another university has a request for help, it is much more difficult. I regularly have requests for help from one of my research team because something in WinEdt is not working properly - such as pdf synchronization problems, or it is using an old version of MikTeX that no longer updates, or that it has switched to using another pdf viewer without warning. I’ve happily used WinEdt for all my LaTeX editing for about 15 years and I’ve encouraged my whole research team to use it. But I’m tired of problems with WinEdt that take up my time.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |