[texworks] Cached version of .sty being used?

Paul A Norman paul.a.norman at gmail.com
Tue Jun 29 14:31:56 CEST 2010


On 29 June 2010 05:28, Stefan Löffler <st.loeffler at gmail.com> wrote:
> Hi,
>
> Am 2010-06-28 03:37, schrieb Paul A Norman:
>> Yesterday I made repeated changes to an .sty and they were never
>> reflected in the output .pdf, either poplar or acrobat reader.
>>
>> I checeked the date stamp on the .sty and it was updating with ewach
>> save, I even monitored it from another editor, and the changes were in
>> the saved version.
>>
>
> This is strange indeed. I never noticed it, and couldn't reproduce now
> either.
>  * Can you reproduce it?

No its fickle.

>  * If so, does the problem persist when you run pdflatex from the
> command line (without closing Tw, though)?
>  * Where was the .sty file located? (custom file in the same directory
> as the .tex, custom file in a local texmf tree, official file in the/a
> system-wide texmf tree, ...)

Miktex registeed directory for user .sty(s)

>
>> In the end I closed and re-opened TeXWorks and all was finally working.
>>
>> Hence I see some possible connection to Tw editor, and the processes
>> it spawns to compile .pdfs
>>
>
> Hm, Tw runs pdflatex anew each time you press typeset, so there
> shouldn't be any "hidden persistent data". But I'm also not sure how/if
> latex internally caches files (I wouldn't think so, but maybe it does to
> avoid having to re-search the texmf tree each time; this may even depend
> on the distro).

MikTex 2.8 Poretable

> In any case, if you can reproduce the problem we might be able to track
> down the problem. If not, let's hope it stays that way ;).
>

I belive that it happened once before, but I rebooted that time and
all came right, this time I tried to solve it.

I do not always make intensive changes to my .sty(s) and I have only
noticed this twice.

> Cheers,
> Stefan
>



More information about the texworks mailing list