Skip to content
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

test file contribution #27

Open
luctaesch opened this issue Apr 10, 2019 · 2 comments
Open

test file contribution #27

luctaesch opened this issue Apr 10, 2019 · 2 comments

Comments

@luctaesch
Copy link

luctaesch commented Apr 10, 2019

I would like to contribute " unit test file" which is also a demo file.

it is a scrivener file, that once compiles , test the unit features . like bold, italics, links , etc

  • it shows the do and dont when using scrivener ans scrivomatic:
    example : use the strong style , not the alt B native command.
  • it demonstrates the limits of scrivener-scrivomatic, so far
  • it helps with regression testing on unitary basic

it is so far not exhaustive, not fully fixed, however this is stand by for 3 month now, as I have reached a point that is good enough for me, so I prefer to share it in the current status, rather than perfect and ever.

ScrivoTests.scriv.zip

=== ------------------------------------------------------ ===
=== Scrivomatic V1.0.20 Report @ 2019-04-10 15:19:01 +0200 ===
=== ------------------------------------------------------ ===
Running under Ruby 2.3.7
Working directory: /Users/luctaesch/Dropbox/zkn/build_mmd
===------ Input Options: ------===
#<struct Scrivomatic::OPT input="ScrivoTests.md", output=nil, to=nil, yaml="./pandocomatic.yaml", command="pandocomatic", envpath="/Users/luctaesch/bin:/usr/local/bin:/Library/TeX/texbin:/Users/luctaesch/.rbenv/shims", build=false, cleanup=false, verbose=true, dry_run=false, open_log=true>
===------ Final ENV PATH: ------===
/Users/luctaesch/bin:/usr/local/bin:/Library/TeX/texbin:/Users/luctaesch/.rbenv/shims:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/Applications/Scrivener.app/Contents/Resources/MultiMarkdown/bin
===------ TOOL PATHS: ------===
---pandoc: /usr/local/bin/pandoc | V: 2.3.1
---pandocomatic: /Users/luctaesch/.rbenv/shims/pandocomatic | V: Pandocomatic version 0.2.3.0
---ruby: /Users/luctaesch/.rbenv/shims/ruby | V: ruby 2.5.3p105 (2018-10-18 revision 65156) [x86_64-darwin18]
---rbenv: /usr/local/bin/rbenv
---python: /usr/bin/python
---xelatex: /Library/TeX/texbin/xelatex
---latexmk: /Library/TeX/texbin/latexmk

… running pandocomatic, please wait …
===------ COMMAND OUTPUT: ------===
:: Running: /Users/luctaesch/.rbenv/shims/pandocomatic -c ./pandocomatic.yaml --debug ScrivoTests.md
::: pandoc --from=markdown
::: --to=markdown_mmd
::: --bibliography=mybib.bib
::: --wrap=none
::: --filter=/usr/local/bin/pandoc-citeproc
::: --csl=/Users/luctaesch/.pandoc/csl/chicago-fullnote-bibliography-LTA2.csl.xml
::: Pandocomatic needed 0.6 seconds to convert 'ScrivoTests.md'.
:: exit status: pid 33316 exit 0

results in:
ScrivoTests.md.zip

@iandol
Copy link
Owner

iandol commented Apr 12, 2019

Hi, great to see this is working for your workflow. Quite a lot of your project seems specific to your ZKN (zettelkasten?) method and assumes that the user is using Zotero. I wonder if it is not better to publish your Scrivener project as a separate Github page, where you can detail the things specific to ZKN and Zotero etc. I don't use ZKN or Zotero, and scrivomatic instructions try to be more general to how to get flexible and robust compile using general Pandoc functionality. In addition, you have made some breaking changes to pandocomatic.yaml as I cannot compile ScrivoTests.scriv successfully...

But the idea of having a document in the project that more explicitly shows the features of Scrivener > MD is a good one, and I will update the Workflow.scriv project when I get time to have an explicit set of tests that are more clearly documented than at present...

@iandol
Copy link
Owner

iandol commented Apr 16, 2019

I've now added a lot more compiled features to workflow.scriv within the main manuscript text and have also listed these features explicitly in a separate instructions text...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants