User Tools

Site Tools


wiki:software:ccdt

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
wiki:software:ccdt [2019/07/05 09:09]
dizwell [5.4 Quitting]
wiki:software:ccdt [2019/07/05 12:21] (current)
dizwell [5.4 Quitting]
Line 237: Line 237:
 Without "<​nowiki>​--nostore</​nowiki>",​ the CCDT run at Step 3 remembers "​blank"​ for all metadata //except// the composer name. So the new CCDT session at Step 4 can offer you nothing by way of defaults to accept. Without "<​nowiki>​--nostore</​nowiki>",​ the CCDT run at Step 3 remembers "​blank"​ for all metadata //except// the composer name. So the new CCDT session at Step 4 can offer you nothing by way of defaults to accept.
  
-But **with** "<​nowiki>​--nostore</​nowiki>",​ the CCDT run at Step 3 doesn'​t remember that you supplied almost no metadata, so the new run at Step 4 can offer you as defaults the stuff you typed in at Step 1.+But **with** "<​nowiki>​--nostore</​nowiki>",​ the CCDT run at Step 3 doesn'​t remember that you supplied almost no metadata, so the new run at Step 4 can offer you as defaults the stuff you typed in at Step 1 (including the mis-spelled composer name: so make sure to correct it on the second run through!)
    
 In short: You will run "​ccdt"​ most often, but "<​nowiki>​ccdt --nostore</​nowiki>"​ is handy on the rare occasions when you want to correct a minor error in just one piece of metadata, without the non-provision of other metadata during that run being '​remembered'​ as the defaults for the next run. In short: You will run "​ccdt"​ most often, but "<​nowiki>​ccdt --nostore</​nowiki>"​ is handy on the rare occasions when you want to correct a minor error in just one piece of metadata, without the non-provision of other metadata during that run being '​remembered'​ as the defaults for the next run.
wiki/software/ccdt.txt ยท Last modified: 2019/07/05 12:21 by dizwell