#Texworksfor windows 8 code#
#Texworksfor windows 8 windows#

#Texworksfor windows 8 windows#

In that case, it would probably be best to report the issue to the TeXLive It is possible that Windows Defender (or some other Windows component) has something to do with this. I infer this based on how the date stamps change for these folders and subfolders when I run the different versions of From your comment before, I take it that both 0.6.5 and 0.7 downloaded from GitHub work fine (or at least used to work fine), but the one installed by TeXLive does not? If that's the case I suspect that there is something different with the TeXLive version (maybe something about the configuration, startup scripts, or whatever). The two versions of TeXworks in folders on the desktop have configuration files at It looks like the TeXworks installed with TeXlive has configuration files at The installed TeXworks shows one list of 'recent files.' The TeXworks 0.65 and TeXworks 0.70 located in separate folders on the desktop both display the same list of 'recent files', and this list is different from the 'recent files' for the TeXworks installed with TeXlive. I opened them separately with the TeXworks installed with TeXlive 2020, and with TeXworks 0.65 and TeXworks 0.70 that are located in separate folders on my desktop (as indicated previously). I created a file test-letter.tex from the letter template and a file test-xetex from the xetex article template. I verified before and after the actions below. Microsoft OneDrive and Adobe Creative Cloud are installed on this computer, but contain nothing. I think the problem on my machine is not caused by network drives because I can entirely reproduce the problem using *.tex files on my desktop. to where settings are stored) which may cause additional differences. I'll have to look into Can you confirm that the 'recent files' list (under File > Open Recent) is the same for the TeXLive installation and the manually downloaded ones? The reason is that the TeXLive version may have some modifications (e.g. The docs don't mention that the file is actually accessed for the things we need (mostly path manipulations), but maybe this still happens under the hood.

#Texworksfor windows 8 code#

Could someone (who does not - or no longer - experience this issue) try to open a file from 'My network places' (without mapping it to a drive letter), then disconnect from the respective network and restart yes, the code lines you mentioned are a very likely candidate for the cause of the issue.Could someone (who does not - or no longer - experience this issue) try to open a file on a mapped network drive (one that has a drive letter), then unmap the drive and restart Tw?.a USB drive), then remove the drive and restart Tw? Could someone (who does not - or no longer - experience this issue) try to open a file on an external hard disk (e.g.

Could someone (who experiences this issue) try with just deleting the openDialogDir key?.Could someone (who experiences this issue) try with just deleting the recentFiles key?.It seems that this problem relates to network drives. It may also be related to something in the underlying Qt framework, which could make it hard to track down, however. Another thing that has caused some problems in the past was spellchecking and highlighting huge documents, but that does not occur if you run Tw without opening a file in it. This requires crawling through directories (as given in the preferences), which may take some time although it should not amount to several minutes. One thing that has caused some issues in the past was checking which typesetting tools are available. Loading settings is one thing, of course, but that shouldn't be resource intensive. Some background: there is not very much Tw does during startup. what versions (of Tw and Qt) are shown under Help > About TeXworks.?.what is shown under Help > Settings and Resources.?.what paths are shown under Edit > Preferences > Typesetting?.does this problem occur also with the latest development version (obtainable from - there should be no problem running this side-by-side with the TL version, just put it in its own directory and don't overwrite the TL binary)?.

1 CPU core (i.e., do you have a hexacore i7?)

am I correct in assuming that 15%-18% correspond to approx.

as I understand it, this problem occurs only/predominantly on Win 10, but not on Win 7?.

Thanks for reporting and sorry for the inconvenience.