Details are inline, here is a summary from 2021-10-14 - todo

• [X] use my own css
  • [X] but get better fonts
• [X] where in org2jekyll is the front matter created? can this be changed? - yes, see org2jekyll.el
• [ ] figure out how to export functional index - probably export from org and check result, reconcile with jekyll.

This source:

#+BEGIN_SRC sh :exports both
ls -1
#+END_SRC

Results in this:

ls -1

Both the code content and the result do show because we set :exports both

Created an empty file with Org front matter like this:

#+STARTUP: showall
#+STARTUP: hidestars
#+OPTIONS: H:2 num:nil tags:nil toc:nil timestamps:t
#+LAYOUT: post
#+AUTHOR: mzimmerm
#+DATE: 2017-04-08 Sat 17:23
#+TITLE: a-test-blog 
#+DESCRIPTION: Testing org2jekyll-create-draft
#+TAGS: org_mode org2jekyll
#+CATEGORIES: categories_required

The file name is a-test-blog.org so this is concatenated from title, with no date.

• This is a literal (verbatim) text with link [[a link][http://some.html]] (surrounded by = ) in text.
• This is a literal code section text with link [[a link][http://some.html]] (surrounded by ~ ) in text.
  • So the above, by default, shows that verbatim and code have same font after conversion to html.

• Example 1 - exports code:
  • text: src_sh[:exports code]{echo "hello"} plugged in text, inline.
  • result: echo "hello" plugged in text, inline.
• Example 2 - exports both
  • text: src_sh[:exports both]{echo "hello"} plugged in text, inline.
  • result: echo "hello" hello plugged in text, inline.
• Example 3: - exports results. This is likely the most common use of inline code blocks
  • text: src_sh[:exports results]{echo "hello"} plugged in text, inline.
  • result: hello plugged in text, inline.
• Example 4 - exports results. As above, showing exports results is default in src_
  • text: src_sh{echo "hello"} plugged in text, inline
  • result: hello plugged in text, inline.
• Example 5: This shows the inside literally as code, so does not call the code
  • text: src_sh[:exports code]{ls -l} allsurrounded by ~ in text:
  • result: src_sh[:exports code]{ls -l} - ls -l refuses to work, result with newline is not allowed in inline calls
• Example 6: Defining function add-in-shell in BEGIN_ SRC

  • text:

    #+name: add-in-shell
    #+BEGIN_SRC sh :var arg1=1 :var arg2=2
    echo arg1 plus arg2 = $(($arg1 + $arg2))
    #+END_SRC
    

  • result: - this displays code, correctly fontified:

    echo arg1 plus arg2 = $(($arg1 + $arg2))
    

• Example 7:
  • text: The following files are in home dir src_sh{ls -1}
  • result: The following files are in home dir src_sh{ls -1} - ls -l refuses to work, result with newline is not allowed in inline calls. Message: *list results cannot be used*
• Example 8: Calling add-in-shell:
  • text: call_add-in-shell(arg1=3, arg2=4)
  • result: arg1 plus arg2 = 7

There are 3 types of lists in org. This is how they convert to html:

1. Ordered List = Numbered List: Shopping list
   1. The Attack of the Clones
   2. Drones
      • Blue
      • Red
   3. Coffee
2. Unordered List = Bulleted List: Favourite Movies, no particular order:
   • Krakatit.
   • The Avatar.
3. Description List: No order. Has :: between key and value. Key is highlighted. Does not indent items.

   Karel Capek

   Povetron

   Karel Capek

   Valka s Mloky. The description list also wraps very nicely after the : : .

   Abrakah Dabra

   Is cool.

Needed htmlize to work.

Sh code:

AVAR="something 1"
OTHER="soma else"

echo "Variable AVAR is set to ${AVAR}"
if [ $AVAR = "something" ]; then
    echo "AVAR was as expected"
else
    echo "UNEXPECTED AVAR"
fi

echo "In shell, :results output is default; can add ~raw~ to not use TABLES IN RESULTS"

Python code equivalent:

AVAR   = "something"
OTHER  = "soma else"

print ("Variable AVAR is set to ") + AVAR
if AVAR == "something":
    print( "AVAR was as expected")
else:
    print ("UNEXPECTED AVAR")

return "In python, :results value is default, as python returns"

A property is a key-value pair associated with an entry. Here, "entry" is:

• the whole document
• tree started with heading

Properties can be set so they are associated with a single entry, with every entry in a tree, or with every entry in an Org mode file.

Properties are like tags, but with a value.

Where can property be defined:

• Either anywhere in file (but do it always on top) as

  #+PROPERTY: property-name-string property-value-string
  

• Or in a drawer just below a heading as

  :PROPERTIES:
  :property-name-string: property-value-string
  :END:
  

Note the syntactic difference on how the key is defined

• in the PROPERTY section, key is NOT surrounded with :
• in the :PROPERTIES: drawer, key IS surrounded with :

But the key name is in both cases property-name-string

For someone using org-babel a lot, I have really only encountered use of properties in defining the overwhelmingly complex property called header-args.

For the longest time, I was confused in how properties are used TODO - finish this

Are labels for context (context = category)

:COLUMNS: %30ITEM %9Approved(Approved?){X} %Owner %11Status %10Time_Estimate{:} %CLOCKSUM %CLOCKSUM_T :Owner_ALL: John Peter Paul :Status_ALL: "In progress" "Not started yet" "Finished" "" :Approved_ALL: "[ ]" "[X]"

so this is column view?

dfadsfadsf adfadsfasdf

MathJax can be passed options to configure it to display various formats:

Allows math to be specified in TeX, LaTeX, MathML, or AsciiMath notation, with the AMSmath and AMSsymbols packages included, producing output using MathML if the browser supports it sufficiently, and HTML-with-CSS otherwise.

See http://docs.mathjax.org/en/latest/

The two sections below describe some nuances for displaying Latex and ASCIIMath in Org2Jekyll and Jekyll.

First, delete the following from the org file if present after org2jekyll-create-draft:

OPTIONS: tex:t HTML_MATHJAX: path:"http://cdn.mathjax.org/mathjax/latest/MathJax.js" HTML_MATHJAX: align: left indent: 5em tagside: left font: Neo-Euler

The Javascript that MathJax will use, must be configured directly in Jekyll, in ./_includes/mathjax-stuff-new.html. Also, see the ./_includes/mathjax-stuff.html which I found somewhere - maybe it's Jekyll default.

There are 3 ways to put Latex in org text:

1. Start with \begin .. \end{equation}, surround by empty lines. Example:

   \begin{equation} x=\sqrt{b} \end{equation}

2. Display mode: Start with double dollar on lines above and below Latex: \[..latex here..\] or $$..latex here..$$. Examples:

   \[ x = \sqrt{b} + c^4 \]

   \[ y = \sqrt{c} + d^3 \]

3. Inline mode: Put \(..latex here..\) or $..latex here..$ around latex. But this may clash on export with dollars etc. This is some latex inline, e.g. \(x = \sqrt{b} + c^4\) or \(y = \sqrt{c} + d^3\) which is nice. Prefer using ~\(etc\)
4. Try org-preview-latex-fragment (bound to C-c C-x C-l). s C-c C-x C-l here (or C-u C-c C-x C-l to preview everything in the subtree, or C-u C-u C-c C-x C-l to preview everything in the buffer)

An important prerequisit to get this working in org export, is to customize org-export-with-sub-superscripts to 'do not interpret'. This can also be set per file using option # + OPTIONS: ^:nil

1. Sum: `sum_(i=1)^n i^3=((n(n+1))/2)^2`
2. Prescripts: `{::}_(\92)^238U` or `{::}_92^238U` ? Both work, so use the second which is simple.
3. Separate the < sign with spaces so `x < y` displays nicely
4. Integrals: `int_0^oo e^(-x^2) dx = sqrt(pi) / 2`

Just a test of tools.