Tag Info

Hot answers tagged

2

TXS uses an internal scanner to detect packages and classes. It currently only searches the standard tex folders not the local folder. If the internal parser cannot locate the file (maybe because it's in the local folder), the package or class name are highlighted in the editor and the toolitp says "package not found". This is merely a hint. It does not ...


2

The settings for syntax highlighting are stored in the settings file. Section [formats] contains all changes done by the user. If a format is not listed there, its default will be used. So you can just delete all entries. Note: TXS has to be closed before editing texstudio.ini, otherwise the changes will not take effect and will be overwritten when you close ...


2

Thanks to the helps from above, I find a solution for this. Install cm-super package in MiKTeX Start -> MiKTeX folder -> Maintenance (Admin) -> Package Manager (Admin) -> Search cm-super -> Install Update pdftex.map (if it doesn't take effect) Start Task Manager(Ctrl+Alt+Delete) -> File -> New Task (Run...) -> Type "cmd" and hit enter -> Run command ...


2

Use Show advanced options. See the image below. You can edit almost everything. Go to Options menu. On the Build tab you can see the pdfchain. I guess that what you want is txs:///pdflatex | txs:///bibtex | txs:///pdflatex | txs:///pdflatex | txs:///view-pdf


1

I tried to use the same combination of Texlive (2014) and Texstudio on a flahs drive and ran into the same issues. Providing the direct path worked fine but would probably not on another computer. Using relative links didn't work. At some point I ommited the dots in the beginning of the link (i.e. "/texlive/bin/win32/pdflatex.exe" -synctex=1 ...


1

From http://texstudio.sourceforge.net TeXstudio has been forked from Texmaker in 2009, because of the non-open development process of Texmaker and due to different philosophies concerning configurability and features. Originally it was called TeXmakerX because it started off as a small set of extensions to Texmaker with the hope that they would ...


1

Just to point out the answer is as indicated by @Johannes_B, where the dvips option for package color causes the problems. All credit to @Johannes_B Regards Roberto


1

I figured out the issue. I had an old hard drive with a version of LaTeX installed on it, so when the compiler ran it was calling packages from the old copy- resulting in an endless loop of sorts. Deleting any and all LaTeX files from the hard drive, plus a clear install on the new one, resulted in all the problems being solved. In hindsight I should have ...


1

Select subfile.tex > ALT + O + M > Build & View.



Only top voted, non community-wiki answers of a minimum length are eligible