From [email protected] on January 10, 2010 14:21:36

Dear Dr. william,

I check out the latest version of latexdaemon and compile it. Then I find
that it doesn't work when the tex file is located under a path which
contain chinese characters.

Any hints on this issue?

Best regards.

Hongyi.

Original issue: http://code.google.com/p/latexdaemon/issues/detail?id=15

From [email protected] on July 11, 2008 11:32:44

I am using LatexDaemon Version 0.10 Build 42 in combination with MikTeX
2.7. I would like to use the SyncTeX facillity with SumatraPDF-sync and
WinEdt, but I cannot pass the -synctex=-1 flag to pdfLaTeX through
LatexDaemon. I would also like to use the -enable-write18 and -enable-pipes
flags.

Is it possible to add a possibillity use the (pdf)LaTeX command line flags
through LatexDaemon?

Thanks,
Martin Heller

Original issue: http://code.google.com/p/latexdaemon/issues/detail?id=2

From [email protected] on October 21, 2010 20:42:27

What steps will reproduce the problem? 1. Starting the program the dos box opens and runs
2. Then it stops and widows opens an error message 3. What is the expected output? What do you see instead? The error message: pdftex.exe has stopped working.

What version of the product are you using? On what operating system? The latest version 0.1 build 45. Windows 7, home pro Please provide any additional information below. Used to work fine with Miktex 2.8

Original issue: http://code.google.com/p/latexdaemon/issues/detail?id=19

From [email protected] on June 11, 2008 00:17:37

What steps will reproduce the problem? 1. 2. 3. What is the expected output? What do you see instead? What version of the product are you using? On what operating system? Please provide any additional information below. I have graphic files (.eps and .pdf) in a directory dedicated to such
files. My (pdf)latex.ini adds this directory to the path and I have no
problem compiling files that include those graphic files. However,when I
try to use latexdaemon, the log file complains that the graphic files
cannot be found. Would that be a problem due to the fact that MiKTeX
2.7's organisation of .ini files is different from MiKTeX 2.5's ?

Similarly, I have problems using french pro: it uses a special
language.dat different from that of babel (to be found in \mltex;
fr(pdf)latex.ini says to search first in \mltex, so at format making
time, initexmf finds the right language.dat. With latexdaemon, no format
can be made and it complains the language.dat is corrupted, which means
that it finds only babel's language dat.

Do you have any idea of what can be done to solve those problems? I
really find latex daemon useful: ordinary compiling time is about 20-25
seconds, and it would make me save a precious time!

Thanks in advance for what you can do.

Bernard Alfonsi

[email protected]

Original issue: http://code.google.com/p/latexdaemon/issues/detail?id=1

From [email protected] on February 20, 2009 16:15:39

What steps will reproduce the problem? 1. Just start latexdaemon What is the expected output? What do you see instead? One would expect to read "daemon>" as the command invite. Instead "dameon>"
is written (swapped "m" and "e") What version of the product are you using? On what operating system? Version 0.1 Build 44, on Windows Vista. Please provide any additional information below. Thanks for the great tool, I did not spot this typo myself (though using
latexdaemon every day) until a friend put the finger on it.

Original issue: http://code.google.com/p/latexdaemon/issues/detail?id=8

Proposal: detect references to .bib file in the .tex file then watch for changes in the bib files and start 'bibtex' upon modification.

From [email protected] on December 28, 2010 22:55:39

Latex Daemon Version 0.10 Build 46 does not work with Miktex 2.9 under windows 7. A window opens with error message: "pdftex.exe has stopped working".

The program runs fine with Miktex 2.8. (this was reported with an older version of latex daemon)

Original issue: http://code.google.com/p/latexdaemon/issues/detail?id=22

From [email protected] on April 27, 2014 08:27:45

It has worked fine until this morning when I launched it and loading a file on it. It kept crashing after I re-downloaded the programme and re-started my computer.

Original issue: http://code.google.com/p/latexdaemon/issues/detail?id=27

From [email protected] on November 06, 2008 09:00:27

Dear Dr. William,

When I use the following option in the tex file:

%Daemon> force=fullcompile

The latexdaemon will complain that:

Unrecognized command: 'force' (use help to get command line help)

I've tried other forms to invoke this option, such as,

%Daemon> force fullcompile
or
%Daemon> --force=fullcompile

But all of them failed to load. Why does this happen?

Regards,
Hongsheng

Original issue: http://code.google.com/p/latexdaemon/issues/detail?id=6

From lev.bishop on June 02, 2009 15:28:25

What steps will reproduce the problem?
1.

C:\test> type test.tex
\documentclass{article}

\begin{document}
front matter.
\end{document} 

C:\test>latexdaemon.exe -preamble=no test.tex

What is the expected output?

What do you see instead?

LatexDaemon Version 0.10 Build 45 by William Blum, May 11 2009
-Preamble precompilation deactivated (requires a file reload)
-Main file: 'C:\test\test.tex'
-Directory: C:\test\
-No additional dependency specified.
-Preamble: none
- the main .tex file has been modified since last run. Let's recompile...
  -- Compilation of test.tex ...
  [running 'latex -aux-directory=TeXAux -interaction=nonstopmode
  --src-specials  " \makeatletter  \newwrite\dependfile \immediate\openout
  dependfile = \"test.dep\"
  \ifx\DAEMON@ORG@InputIfFileExists\@undefined\let\DAEMON@ORG@InputIfFileExists\InputIfFileExists\fi
  \long\def\DAEMON@InputIfFileExists#1#2#3{\immediate\write\dependfile{#1}\DAEMON@ORG@InputIfFileExists{#1}{#2}{#3}}
  \let\InputIfFileExists\DAEMON@InputIfFileExists \makeatother  \input
  \"test.tex\" "']
  latex: Not enough room in an internal buffer.
  daemon@>

What version of the product are you using? On what operating system?

LatexDaemon Version 0.10 Build 45 by William Blum, May 11 2009
  Windows XP SP3
  This is pdfTeX, Version 3.1415926-1.40.9 (MiKTeX 2.7)

Please provide any additional information below.

Original issue: http://code.google.com/p/latexdaemon/issues/detail?id=11

From [email protected] on December 12, 2010 00:46:02

What steps will reproduce the problem? Compiling with the --custom_args=-synctex=-1 switch

instead of producing a .fmt file causes a pdftex error. No format, no pdf.

Compiling without this switch is OK

I'm using version build 46, under WinXP Service Pack 3.

Best regards,

B. ALFONSI

Original issue: http://code.google.com/p/latexdaemon/issues/detail?id=21

From [email protected] on September 07, 2010 15:10:43

1. This is a minimal example. The following file is placed in P:/Paul/tmp :

\documentclass{article}
\begin{document}
Test main

\input{P:/Paul/retest.tex}

Test main
\end{document}

1. latexdaemon is started with the command

latexdaemon --force -ini=latex --custom_args=-synctex=-1' "test.tex"

and the file is compiled correctly.

1. However, when I modify P:/Paul/retest.tex the daemon declares

."..\retest.tex" modified
."..\retest.tex" modified

(Note : there are two declarations after the second modification).

But it doesn't compile the file test.tex, as expected.

I'm using version 0.10 build 45 on Windows Seven.

Original issue: http://code.google.com/p/latexdaemon/issues/detail?id=17

From [email protected] on July 16, 2013 22:18:47

What steps will reproduce the problem?

1.Write a simple file to be compiled with xe/lualatex (\usefontspec etc.)
2. Launch latexdaemon with "latexdaemon --ini=xe/lualatex testfile.tex

What is the expected output? What do you see instead?

Creation of testfile-xelatex.fmt or testfile-lualatex.fmt and testfile.pdf

What version of the product are you using? On what operating system?

latexdaemon 0.10 build 46 on Xindows 7 x64 and MiKTeX 2.9

####provide any additional information below.
Message appearing at the console (two last lines):

pdftex: The memory dump file could not be found
pdftex: Data: lualatex.fmt
(or Data: xelatex.fmt)

Nothing more. Abolutely no file produced.

Original issue: http://code.google.com/p/latexdaemon/issues/detail?id=26

From [email protected] on September 24, 2009 10:16:03

Dear Dr. William,

I've updated the latexdaemon to its latest svn version, i.e., 0.10 Build
46. But, when I use it to work with my phdthesis, which is a huge
document, I meet the following errors:

LatexDaemon Version 0.10 Build 46 by William Blum, Sep 22 2009

-Initialization file set to "pdflatex"
-File modification monitoring activated
-Latex output: show error and warning messages only
-Custom argument to be passed to the TeX engine: '--synctex=-1 --shell-
escape'
-Automatic dependency detection activated
-Auxiliray files directory set to 'template.TeXAux'
-After-compilation job set to 'custom'
-Custom command set to '"F:\zhaohs\etc\bin\latexdaemon_afterjob.cmd"'
-Main file: 'F:\zhaohs\Desktop\GUCASthesis[Final_Version]
\GUCASthesis\template.t
ex'
-Directory: F:\zhaohs\Desktop\GUCASthesis[Final_Version]\GUCASthesis
-No additional dependency specified.
-Preamble: internal

• template.pdf does not exist. Let's create it...
  -- Compilation of template.tex ...
  [running 'pdftex -aux-directory=template.TeXAux -interaction=nonstopmode --
  synct
  ex=-1 --shell-escape "&template-pdflatex" "template.tex"']
  . ! File ended while scanning use of
  
  \par
  <*> &template-pdflatex template.tex

  ! Emergency stop.
  <*> &template-pdflatex template.tex

  ! ==> Fatal error occurred, no output PDF file produced!
  Transcript written on template.log.

Any hints on this issue will be highly appreciated, thanks in advance.

Original issue: http://code.google.com/p/latexdaemon/issues/detail?id=13

From [email protected] on February 23, 2009 17:35:44

Hi!

when I run latexdaemon command

l XXXXX.tex --afterjob=dvips

it generate dvi file but not ps file. The following
information appear:

Dependency detected but cannot be opened: size12.clo
Dependency detected but cannot be opened: .def
Dependency detected but cannot be opened: portuges.ldf
Dependency detected but cannot be opened: dvips.def
Dependency detected but cannot be opened: pstricks.tex
Dependency detected but cannot be opened: pst-plot.tex
Dependency detected but cannot be opened: pstricks-add.tex

Could you help me ?

Thanks in advanced.

Original issue: http://code.google.com/p/latexdaemon/issues/detail?id=10

From [email protected] on September 13, 2010 10:40:36

Is there a way to make latexdaemon fully compatible with MiKTeX 2.8? Many programs are incompatible with version 2.8 of MiKTeX: when a new package should be installed, MiKTeX won't show a GUI dialogue asking to confirm the installation. It just terminates with the error "GUI framework cannot be initialized".

Is it possible to latexdaemon to invoke MiKTeX in such a way as to avoid this problem? (Although I'd say this was a quite reckless change in miktex 2.8 ... it broke too many programs, not just latexdaemon)

Original issue: http://code.google.com/p/latexdaemon/issues/detail?id=18

From [email protected] on July 16, 2013 22:03:44

What steps will reproduce the problem? 1. Unzip latexdaemon.zip in LocalTeXMF\miktex\bin
2. Copy a test file (mytest.tex) in the same directory
3. Launch the command line from the same director : latexdaemon --ini=pdflatex mytestfile.tex

A format file should be made from the preamble of mytest.tex and there should be a mytest.pdf. No .fmt nor .pdf file but the console informing me that "I can't find mytest.tex" and a texput.log file (attached)

I use latexdaemon 0.10 build 46 with MiKTeX 2.9 64 bits on Windows 7 64 bits Please provide any additional information below.

Original issue: http://code.google.com/p/latexdaemon/issues/detail?id=25

From [email protected] on November 05, 2008 13:57:56

Read latexdaemon settings from a general startup file, say
latexdaemon.config, to avoid having to include the same configuration in
the tex file each time a new tex document is created.

Original issue: http://code.google.com/p/latexdaemon/issues/detail?id=3

From [email protected] on June 27, 2011 16:25:27

What steps will reproduce the problem? 1. Start editing a latex file while using latexdaemon
2. after a few compilations have happened, add bibliography, and include citations to it
3. save the file, so it gets automatically recompiled

Note that at this step the references show up as [?], no matter how many compilations happened.

1. now use the 'f' command to do a full compile

Again, the references show up as [?].

If I quit latexdameon, remove the TeXAux folder, and restart it, then it'll work.

Original issue: http://code.google.com/p/latexdaemon/issues/detail?id=24

From [email protected] on December 09, 2010 12:39:04

What steps will reproduce the problem? 1. my main.tex compiles to main.pdf
2. leave main.pdf open in Acroread
3. touch main.tex and see the compilation fail What is the expected output? What do you see instead? Is it possible to close acroread before launching the compilation. BTW this is what TeXnicCenter 2.0 does. What version of the product are you using? On what operating system? 0.10 build 46 Please provide any additional information below. Thanks!
mario

Original issue: http://code.google.com/p/latexdaemon/issues/detail?id=20

From [email protected] on November 05, 2008 16:17:43

Dear Dr. William,

I've found the Latexdaemon doesnot work with glossaries package.

About this package, you can find it in: http://theoval.sys.uea.ac.uk/~nlct/latex/packages/glossaries/ and in the ctan: http://www.ctan.org/tex-archive/macros/latex/contrib/glossaries/ The author supplied many examples with this package.

But nont of them I've tested can work with Latexdaemon. In short, the pdf
file just can be gererated when set -ini=pdflatex.

Regards,
Hongsheng Zhao

Original issue: http://code.google.com/p/latexdaemon/issues/detail?id=5

From [email protected] on November 05, 2008 16:00:42

Dear Dr. William,

I've use the following tex file to test the Latexdaemon for co-work with
TexLive 2008 for windows xp:

%Daemon> ini=pdflatex
%Daemon> watch=yes
%Daemon> filter=err+warn
%Daemon> custom_args="--synctex=-1 --shell-escape"
%Daemon> autodep=yes

\documentclass{article}
\usepackage{CJK}
\usepackage[pdftex]{hyperref}
\hypersetup{CJKbookmarks=true,colorlinks,linkcolor=blue}
\begin{document}

\tableofcontents
\section{china}\label{hello}
\ref{hello}

China, how are you!

\end{document}

But the latexdaemon will give me the following errors:

! Undefined control sequence.
l.9 \documentclass
! Undefined control sequence.
l.10 \usepackage
! Undefined control sequence.
l.11 \usepackage
! Undefined control sequence.
l.12 \hypersetup
! Undefined control sequence.
l.13 \begin
! Undefined control sequence.
l.15 \tableofcontents
! Undefined control sequence.
l.16 \section
! Undefined control sequence.
l.16 \section{china}\label
! Undefined control sequence.
l.17 \ref

What do you think about this issue?

Regards,

Hongsheng Zhao.

Original issue: http://code.google.com/p/latexdaemon/issues/detail?id=4

From [email protected] on February 22, 2009 05:10:39

Comments in the .tex preamble cannot contain unbalenced curly braces.
(Reported by Julien Cornebise.) What steps will reproduce the problem? 1. Save the following lines in foo.tex:

\documentclass{article}
% { Ceci est une parenthèse qui ne devrait pas poser de problème
\begin{document}
Exemple
\end{document}

1. load the file with latexdaemon What is the expected output? What do you see instead? It should precompile the preamble with no error. Instead the precompilation
   fails.

Original issue: http://code.google.com/p/latexdaemon/issues/detail?id=9

From [email protected] on February 11, 2011 19:14:26

What steps will reproduce the problem? 1. Install TeXLive 2010 in default directory
2. Create any sample texfile in any directory
3. try to use latexdaemon What is the expected output? What do you see instead? \documentclass{article}
\begin{document}
Exemple
\end{document}

I expect it to work, but the output is:
[...]
This is pdfTeX, Version 3.1415926-1.40.11 (Web2C 2010)
restricted \write18 enabled.
Source specials enabled.
format name test-latex not written in fmtutil.cnf.
Running the command C:\texlive\2010\bin\win32\fmtutil.exe
Sorry, I can't find the format test-latex.fmt'; will trypdftex.fmt'.
entering extended mode
(./test.tex
! Undefined control sequence.
l.1 \documentclass
{article}
! Undefined control sequence.
l.2 \begin
{document}
[1{c:/texlive/2010/texmf-var/fonts/map/pdftex/updmap/pdftex.map}] )
(see the transcript file for additional information)<c:/texlive/2010/texmf-dis
t
/fonts/type1/public/amsfonts/cm/cmr10.pfb>
Output written on test.pdf (1 page, 13403 bytes).
Transcript written on test.log.
pdftex: unrecognized option `-aux-directory=TeXAux'

kpathsea: Running mktexfmt test-latex.fmt

The command name is C:\texlive\2010\bin\win32\mktexfmt
[...]

Every command seems to raise an Undefined Control Sequence error. I know you only tested it with MikTex, but is it known how to fix this with TexLive? What version of the product are you using? On what operating system? TeXLive 2010, Windows7 Professional Please provide any additional information below.

Original issue: http://code.google.com/p/latexdaemon/issues/detail?id=23

Add the following options:

 --psviewer={gsview|path to a .ps viewer}

 --pdfviewer={gsview|path to a .pdf viewer}

 --dviviewer="c:\long path\yap.exe"
	to overwrite the default viewer associated with the corresponding files.

From [email protected] on July 07, 2009 10:44:58

Steps will reproduce the problem:

1. Keep .aux files from former compilations in the main folder
2. Add a \label and \ref to this label
3. Compile with latexdaemon

Expect to have the labels correctly resolved. Instead, latexdaemon
seem to ignore the "Latex Warning: Label(s) may have
changed. Rerun to get cross-reference right." and does not recompile. Most
likely due to the location of the .aux files generated by compilation from
latexdaemon that is not the same as the existing .aux files.

I use latexdaemon 0.1 build 44.

Thanks for the tool !

Original issue: http://code.google.com/p/latexdaemon/issues/detail?id=12

From [email protected] on October 17, 2009 15:53:02

Hi William,

Firstly, I have to commend you on this project. Windows was in desperate
need of something like this, and I was very glad to find a solid
implementation of a LaTeX daemon out there.

The only significant suggestion I might make is the following: a "manual
mode" where you could simply send "compile" to the stdin pipe. Of course,
this already is implemented, but can only be done in addition to the
automatic recompilations performed by the "watcher". My proposal would be
to have "--watch=no" leave the program running, but just not do any
automatic compilation. Unless I am misunderstanding something, the current
behaviour simply turns your program into a simplified version of "latex" or
"pdftex" in that it is no longer a daemon really.

If you could let me know what you think of this suggestion/perhaps clarify
my understanding, that would be great.

Thanks,
Alex

Original issue: http://code.google.com/p/latexdaemon/issues/detail?id=14

Currently messages reporting watched file modifications are not swallowed when the make thread is running. This is to avoid interleaving of stdout messages. A workaround is to buffer the messages and print them whenever the make "thread" terminates. Another solution is to implement a separate thread that would serialized stdout from all other threads.
Impact: low

From [email protected] on June 21, 2010 15:51:45

I find latex daemon quite useful. It would be still more useful if there was an afterjob option to convert from dvi to eps and then to pdf, in order to have pdf figures of the right size to be inserted in a document, compiled with pdflatex. My main use is for pstricks ansd its environment TeXtoEPS.

B. Alfonsi

Original issue: http://code.google.com/p/latexdaemon/issues/detail?id=16

Hi William, I have been using LatexDaemon since 2007 and, first of all, should thank you for creating it. :).

With updates to Miktex, however, it seems to throw this error how that I cannot resolve (On a 2019 version of miktex it does not)

! Extra \endgroup.
\document ->\endgroup
\immediate \closeout \preambledepfile \let \input \DAE...
l.5 \begin{document}

The latex file is a simple "hello world": ie.

\documentclass[12pt]{article}
\begin{document}
\title{LatexDaemon Error Message}
\author{Me}
\maketitle
\section{Test}
Hello world
\end{document}

Full error log output is in the "Output Snapshot.png" file for you to see, also showing the miktex version MiKTeX-TeX 4.3 (MiKTeX 21.8).

Could you, may be, help me find out what the problem is to fix it?

Thank you so much.