Hi Chris
Thanks very much for the prompt answer!
The appended samples - taken from a TeX forum (slight insignificant changes) -
could serve as MWEs
They kind of work, but the files are created deeply in a temp directory and
then immediately deleted when the compilation ends - thus practically unusable
for further work
Previously everything worked fine, until I updated to W10...
It still works fine with command-line texify --pdf, i.e. the files are created
in the current folder and are not automatically deleted
Thanks
Radu
---
First MWE
---
\documentclass{article}
\usepackage{newfile}
\newoutputstream{comment}
\openoutputfile{xxx.comment}{comment}
\begin{document}
\section{Test}
text one
\addtostream{comment}{\noexpand\item comment one at page \thepage}
text two
\addtostream{comment}{\noexpand\item comment two}
\section{Comments}
\closeoutputstream{comment}
\begin{enumerate}
\input{xxx.comment}
\end{enumerate}
\end{document}
---
---
Another MWE attempt
---
\documentclass{minimal}
\newwrite\tempfile
\begin{document}
\immediate\openout\tempfile=yyy.tex
\immediate\write\tempfile{yyy: this is quite interesting}
\immediate\write\tempfile{}
\immediate\write\tempfile{yyy: this too}
\immediate\closeout\tempfile
\input{yyy.tex}
this is bizarre
\end{document}
---
-----Original Message-----
From: Christopher Weedall [mailto:[email protected]]
Sent: Wednesday, November 15, 2017 1:35 PM
To: A place for MiKTeX users to discuss MiKTeX related questions.
Subject: [FORGED] Re: [MiKTeX] writing custom files
Hi Radu,
Without the exact file you wrote, it's difficult for us to say whether this is
actually a MiKTeX problem or not. I'm inclined to say it's the way you wrote
it, because when I use \newwrite, my files remain - both using the default
compilation methods in MiKTeX's TeXworks and my own custom ones (command line
calls which change the build file output folder to be a subfolder instead).
Take a look at this answer about a question with \newwrite and see if it
answers your question somehow:
https://tex.stackexchange.com/a/323464/78866
As an unrelated point to \newwrite, you can change the output folder by specify
the -aux-directory=DIR and -output-directory=DIR options (for example, when
calling miktex-xelatex.exe). I don't have any problems with these build and
output files disappearing ever - unless I manually delete them, of course.
If you are still having problems, I suggest you providing the list with a
minimal example of what you *are* doing that causes problems. We can run it
locally and identify if we receive the same behavior as you, or not. If not,
then the problem is likely your MiKTeX installation. If the behavior is
identical, then technically, you should directly your question to a different
site/list, because that will mean it's a (La)TeX problem instead, probably.
Hope that helps!
Best,
Chris
On Tue, Nov 14, 2017 at 5:42 PM, Radu Nicolescu <[email protected]>
wrote:
> Apologies for the perhaps trivial question
>
> Basically, I am working on Windows 10 and I need to keep the files
> which I create, e.g. via \newwrite or \newoutputstream of package
> newfile
>
> By default, these files used to be stored in the same folder as the
> main .tex file
>
> Currently, they seem stored in a temporary folder, which is
> automatically and quickly deleted at the end of the compilation, e.g.
>
> C:\Users\user\AppData\Local\Temp\mik85410\_src
>
> Can I configure MiKTeX to revert to the expected behaviour or are
> there alternate ways to ensure that these files are not deleted?
>
> Interestingly, everything is as expected, if I compile directly from
> the command-line, i.e. using texify --pdf
>
> Any suggestion would be much appreciated
>
> Thanks
>
> Radu
>
>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Q: How can I leave the mailing list?
> A: See http://docs.miktex.org/faq/support.html#leavingml
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most engaging tech
sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Q: How can I leave the mailing list?
A: See http://docs.miktex.org/faq/support.html#leavingml
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Q: How can I leave the mailing list?
A: See http://docs.miktex.org/faq/support.html#leavingml
