Skip to content

Commit 00e37f8

Browse files
committed
Added list format suggested by Kathy....almost
1 parent d6afa99 commit 00e37f8

File tree

2 files changed

+10
-10
lines changed

2 files changed

+10
-10
lines changed

.travis.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ install:
77
- sudo apt-get install -y texlive-fonts-recommended
88

99
script:
10-
"pandoc --metadata-file=./pandoc_latex.yml Readme.md -o Readme.pdf"
10+
"pandoc -f markdown+fancy_lists --metadata-file=./pandoc_latex.yml Readme.md -o NAG_kdb.pdf"
1111

1212
deploy:
1313
provider: pages

Readme.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -192,16 +192,16 @@ With our problem now fully defined, we invoke the NAG routine to compute our sol
192192

193193
NAG recently published the technical report [Using the NAG Library with Kdb+ in a Pure Q Environment](https://www.nag.com/doc/techrep/pdf/tr1_18.pdf) discussing how to call the NAG Library using the new [Foreign Function Interface (FFI)](https://code.kx.com/q/interfaces/ffi/) from Kx. Additionally, the NAG Blog titled [Calling the NAG C Library from Kdb+](http://blog.nag.com/2013/05/calling-nag-c-library-from-kdb.html) details how to incorporate the NAG Library with kdb+ within a C++ program. We speculate that among our shared clients, a mixture of these methods will be employed.
194194

195-
If your desired usage case happens to fall outside of those described within our current publications, please contact NAG support at [email protected] for assistance with your application.
195+
If your desired usage case happens to fall outside of those described within our current publications, please contact NAG support at [[email protected]](mailto:[email protected]) for assistance with your application.
196196

197197
## 5 References / Bibliography
198198

199-
1. Calling the NAG C Library from Kdb+ [http://blog.nag.com/2013/05/calling-nag-c-library-from-kdb.html](http://blog.nag.com/2013/05/calling-nag-c-library-from-kdb.html)
200-
1. Get Going with Kdb+ [https://code.kx.com/v2/](https://code.kx.com/v2/)
201-
1. Kdb+ and Python: embedPy and PyQ [https://kx.com/blog/kdb-python-embedpy-pyq/](https://kx.com/blog/kdb-python-embedpy-pyq/)
202-
1. NAG GitHub Organisation [https://github.com/numericalalgorithmsgroup/](https://github.com/numericalalgorithmsgroup/)
203-
1. NAG Library for *Python* Manual [https://www.nag.com/numeric/py/nagdoc_latest/index.html](https://www.nag.com/numeric/py/nagdoc_latest/index.html)
204-
1. Using Foreign Functions with Kdb+ (FFI) [https://code.kx.com/q/interfaces/ffi/](https://code.kx.com/q/interfaces/ffi/)
205-
1. Using Python with kdb+ (PyQ) [https://code.kx.com/q/interfaces/pyq/](https://code.kx.com/q/interfaces/pyq/)
206-
1. Using the NAG Library with Kdb+ in a Pure Q Environment [https://www.nag.com/doc/techrep/pdf/tr1_18.pdf](https://www.nag.com/doc/techrep/pdf/tr1_18.pdf)
199+
(#) Calling the NAG C Library from Kdb+ [http://blog.nag.com/2013/05/calling-nag-c-library-from-kdb.html](http://blog.nag.com/2013/05/calling-nag-c-library-from-kdb.html)
200+
(#) Get Going with Kdb+ [https://code.kx.com/v2/](https://code.kx.com/v2/)
201+
(#) Kdb+ and Python: embedPy and PyQ [https://kx.com/blog/kdb-python-embedpy-pyq/](https://kx.com/blog/kdb-python-embedpy-pyq/)
202+
(#) NAG GitHub Organisation [https://github.com/numericalalgorithmsgroup/](https://github.com/numericalalgorithmsgroup/)
203+
(#) NAG Library for *Python* Manual [https://www.nag.com/numeric/py/nagdoc_latest/index.html](https://www.nag.com/numeric/py/nagdoc_latest/index.html)
204+
(#) Using Foreign Functions with Kdb+ (FFI) [https://code.kx.com/q/interfaces/ffi/](https://code.kx.com/q/interfaces/ffi/)
205+
(#) Using Python with kdb+ (PyQ) [https://code.kx.com/q/interfaces/pyq/](https://code.kx.com/q/interfaces/pyq/)
206+
(#) Using the NAG Library with Kdb+ in a Pure Q Environment [https://www.nag.com/doc/techrep/pdf/tr1_18.pdf](https://www.nag.com/doc/techrep/pdf/tr1_18.pdf)
207207

0 commit comments

Comments
 (0)