Comments (2)
Yes or not. One advantage of the sharing of a directory would be that, if two documents with same properties (width, size etc.) use the same score, it wouldn't get compiled two times. And we could write lists dependent on the name of the original .tex
to let users choose which files they want to remove. I think it would be an argument againts the purge
option, and to let users remove unnecessary files with their own commands.
That said, I agree that hard-code is generally a bad thing, and that letting users choose what they prefer is a good one. So we could add an optional argument to change the default tmp_ly
, and a purge
option ; users who don't want to use them won't have to change anything, those who want will be able to.
from lyluatex.
One advantage of the sharing of a directory would be that, if two documents with same properties (width, size etc.) use the same score, it wouldn't get compiled two times.
This is indeed a good argument. But of course I didn't want to suggest to have individual temp directories per document but the option to have them. I agree that the default use case would probably be to have one shared temp directory and leave all files as they are, doing the clean-up with some other tools and schedules.
Having the possibility to have a shared or individual temp directories will in any way add flexibility for users to create their workflows. And since there's a reasonable default they don't have to bother with it.
from lyluatex.
Related Issues (20)
- lilypond environment, command give different results with the same input
- Lilypond, Texlive 2018 -> Texlive 2020 and... nothing works anymore HOT 7
- Fatal error: missing \begin{document} HOT 10
- Lilypond not recognized HOT 5
- Adding new Lilypond parts (TexLive 2020)
- Too much empty space on a page
- Failing to auto-compile HOT 3
- LilyPond raw-pdf does not give hoffset
- cannot start lilypond HOT 4
- Unprecedented error! Need Help! HOT 3
- Doctoral Thesis in musicology HOT 3
- lilypond 2.23.x and lyluatex (fragments not inserted) HOT 19
- Latex Error: ./filename.tex:62 Too many }'s. HOT 3
- Adjust text font size in lilypond HOT 3
- Missing final system on recompile HOT 6
- Trying (i.e. Failing) to Use Lilypond HOT 5
- Undefined control sequence HOT 2
- Lyluatex fails to compile documents in GitHub Actions HOT 12
- \setmainfont causes problems HOT 6
- The score doesn't contain any music HOT 5
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from lyluatex.