# LaTeX doesn't pick up changes to style file

I installed the widetext package and was happily using it until I decided to edit the style file widetext.sty. Happily, LaTeX immediately picked up the changes and compiled correctly. I then decided to undo those changes to widetext.sty, and I did so, but now latex doesn't seem to pick up this fact (ie it still thinks the changes are present). If I rename widetext.sty to something else, LaTeX properly fails to compile and says it can't find widetext.sty. However, if I intentionally put garbage text in widetext.sty to cause the latex compile to fail, LaTeX doesn't seem to notice and happily compiles the last "working copy" of widetext.sty it seems to have stashed in some form of cache somewhere.

I tried to delete all output files in the working directory. No luck. widetext.sty is located in C:\Program Files\MiKTeX 2.9\tex\latex\widetext. Thoughts?

• @BoB: Welcome to tex.sx! Note that it is unusual around here to have any greeting. Mar 10, 2011 at 19:27
• @BoB: I would not change a .sty file. Instead, I recommend to use \renewcommand (or \def etc.) to make changes within your document or your own style file. If you edit styles or classes, 1. your document is not portable, it would look different when compiled on other systems, 2. other files would look different or won't work when compiled at your sytems with modified styles. Mar 10, 2011 at 19:33
• Most likely you have a second copy of the file somewhere which is used instead. Just try to search for other files called widetext.sty Mar 10, 2011 at 19:40
• Take a look in your log file for the filename widetext.sty and see which version it thinks it is using (I mean, where on your system it is located). Mar 10, 2011 at 20:06
• thanks for the comments everyone. @Stefan -- I agree, this was just a quick fix I wanted to try. @Martin/Andrew -- strangely the log file points to the correct copy of the style file...
– BoB
Mar 10, 2011 at 23:12

• This sounds like the 'magic' Windows 7 performs if a non-admin tries to edit a file inside Program Files: it makes a local copy. This is a double-edged sword for many programs, unfortunately. Feb 3, 2013 at 19:55