-
Notifications
You must be signed in to change notification settings - Fork 351
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clean Auxiliary Files does not clean all files (new suggestions) #39
Comments
The .synctex.gz file is intentionally left in place by default. It allows you to sync between editor and viewer. We want to keep this functionality even after cleaning. You are free to add it to the files to be removed yourself. |
Okay, but the *.run.xml file definitely deserves to be incinerated since it is a Biber artifact. What do you think? |
Agreed. |
One more suggestion. If someone is using minted for source code highlighting, it will create .pyg files by default. I suggest that .pyg files should be deleted as well. |
Unsure. We cannot include every possible file generated by some package. On the other hand, it wouldn’t do much harm here. |
Biblatex creates an auxiliary file "-blx.bib", which cannot by cleaned with the current interface. |
In his first reply, timhoffm wrote that if one wants to always remove a particular file type one could: "You are free to add it to the files to be removed yourself." I didn't find a way to configure which files are cleaned. Could you please advise how this can be done? |
In the "clean auxiliary files" dialog, there is a comma-separated list of extensions, that we users can extend ourselves. There is currently no way to delete files, whose extension doesn't start with the period (e.g. |
Great, got it - thanks. I see though once I set something, e.g., add an extension, it stays there until I change it or revert to default. Is there a way to modify the default? |
Not that I know of; Why would you want to? The interface is meant for deleting auxiliary files, which you usually will either want to keep or remove all of. That said, we have moved quite off-topic. For usage questions that are not answered by looking into the manual, the mailing list or superuser.com are more appropriate and I expect the most recent comments to get deleted or hidden before long. I can especially recommend superuser.com (or other sites of the staxkexchange network as appropriate), since it is good at showing previously asked related questions and answers based on the given question title, that wouldn't easily be found be a google search (though most are). |
Noted, thanks. |
.run.xml was added, the rest stays as it is. |
What about extensions from auxiliary files from |
Specifically, there are two more extra files that need cleaning:
Normally, this function should leave only the PDF and the TeX source, am I right?
The text was updated successfully, but these errors were encountered: