You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, fizz will put the output of its latest run into a timestamped directory under out/, so that as one runs it repeatedly, the directories under out keep accumulating.
At least in my usage, the output directory of the last run is the only one I'm interested in 99% of the time. But something as simple as "show me the latest graph.dot in a GraphViz viewer" requires a bit of shell scripting if I want to make it into a repeatable command, e.g. something likexdot "out/$(ls -t1 out/ | head -n 1)/graph.dot".
Proposal
This could be made a lot easier for myself and others if Fizzbee maintained a symlink, let's call it out/latest, which it would update at the end of each run so that it points to the timestamped output directory just created.
Additional context
The TLA+ Toolbox does something similar: For a model named Model_1, it creates a timestamped directory Model_1_SnapShot_<TIMESTAMP> for every run but also copies the current one into a directory just named Model_1. I think copying is a waste of resources (and in TLA+'s case probably goes back to the time before Windows supported symlinks) and a symlink would probably be better.
The text was updated successfully, but these errors were encountered:
The problem
Currently,
fizz
will put the output of its latest run into a timestamped directory underout/
, so that as one runs it repeatedly, the directories underout
keep accumulating.At least in my usage, the output directory of the last run is the only one I'm interested in 99% of the time. But something as simple as "show me the latest
graph.dot
in a GraphViz viewer" requires a bit of shell scripting if I want to make it into a repeatable command, e.g. something likexdot "out/$(ls -t1 out/ | head -n 1)/graph.dot"
.Proposal
This could be made a lot easier for myself and others if Fizzbee maintained a symlink, let's call it
out/latest
, which it would update at the end of each run so that it points to the timestamped output directory just created.Additional context
The TLA+ Toolbox does something similar: For a model named
Model_1
, it creates a timestamped directoryModel_1_SnapShot_<TIMESTAMP>
for every run but also copies the current one into a directory just namedModel_1
. I think copying is a waste of resources (and in TLA+'s case probably goes back to the time before Windows supported symlinks) and a symlink would probably be better.The text was updated successfully, but these errors were encountered: