Skip to content
[Jenkins]Jenkins
log in

Changes

#13 (Mar 9, 2021, 11:13:30 PM)

  1. Try one case of TeX inline code syntax highlighting — Tidefelt Henrik / githubweb

#13 (Mar 9, 2021, 11:13:30 PM)

  1. Try one case of TeX inline code syntax highlighting — Tidefelt Henrik / githubweb

#12 (Mar 9, 2021, 11:05:20 PM)

  1. Enable 'tex' syntax highlighting of code blocks — Tidefelt Henrik / githubweb

#12 (Mar 9, 2021, 11:05:20 PM)

  1. Enable 'tex' syntax highlighting of code blocks — Tidefelt Henrik / githubweb

#10 (Mar 7, 2021, 10:32:16 PM)

  1. Apply suggestion for "is is" — noreply / githubweb

#10 (Mar 7, 2021, 10:32:16 PM)

  1. Apply suggestion for "is is" — noreply / githubweb

#9 (Mar 7, 2021, 10:23:16 PM)

  1. Say "Use hard line breaks..." in separate sentence — Tidefelt Henrik / githubweb
  2. Add the 'is' in "of 2 spaces is used" — Tidefelt Henrik / githubweb
  3. Rules for trailing spaces and empty lines — Tidefelt Henrik / githubweb
  4. Also mention impact for merge conflict resolution — Tidefelt Henrik / githubweb

#9 (Mar 7, 2021, 10:23:16 PM)

  1. Say "Use hard line breaks..." in separate sentence — Tidefelt Henrik / githubweb
  2. Add the 'is' in "of 2 spaces is used" — Tidefelt Henrik / githubweb
  3. Rules for trailing spaces and empty lines — Tidefelt Henrik / githubweb
  4. Also mention impact for merge conflict resolution — Tidefelt Henrik / githubweb

#8 (Mar 7, 2021, 9:41:01 PM)

  1. Clarify \willintroduce as suggested — noreply / githubweb

#8 (Mar 7, 2021, 9:41:01 PM)

  1. Clarify \willintroduce as suggested — noreply / githubweb

#7 (Mar 7, 2021, 9:26:31 PM)

  1. Mention where to find our LaTeX macros and environments — Tidefelt Henrik / githubweb

#7 (Mar 7, 2021, 9:26:31 PM)

  1. Mention where to find our LaTeX macros and environments — Tidefelt Henrik / githubweb

#6 (Mar 7, 2021, 9:09:06 PM)

  1. Say that \firstuse should generally be used together with \index — Tidefelt Henrik / githubweb

#6 (Mar 7, 2021, 9:09:06 PM)

  1. Say that \firstuse should generally be used together with \index — Tidefelt Henrik / githubweb

#5 (Mar 7, 2021, 8:48:41 PM)

  1. Add comments with TODOs after LaTeXML issue is fixed — Tidefelt Henrik / githubweb
  2. Work around LaTeXML/MathJax issue with \emph in mathescape — Tidefelt Henrik / githubweb
  3. Expect MathJax to become obsolete rather than workaround in LaTeXML — Tidefelt Henrik / githubweb
  4. Say "colon" before (:) (that is, a colon inside parentheses) — Tidefelt Henrik / githubweb
  5. Add comma before "it is illegal" — noreply / githubweb

#5 (Mar 7, 2021, 8:48:41 PM)

  1. Add comments with TODOs after LaTeXML issue is fixed — Tidefelt Henrik / githubweb
  2. Work around LaTeXML/MathJax issue with \emph in mathescape — Tidefelt Henrik / githubweb
  3. Expect MathJax to become obsolete rather than workaround in LaTeXML — Tidefelt Henrik / githubweb
  4. Say "colon" before (:) (that is, a colon inside parentheses) — Tidefelt Henrik / githubweb
  5. Add comma before "it is illegal" — noreply / githubweb

#4 (Mar 5, 2021, 9:00:34 AM)

  1. Add rules related to "expression" and "call" — Tidefelt Henrik / githubweb

#3 (Mar 5, 2021, 8:37:38 AM)

  1. Add and apply rule for "reduction expression", and add to document index — Tidefelt Henrik / githubweb

#2 (Mar 4, 2021, 11:58:03 PM)

  1. Say "the 'each' keyword" without hyphen — Tidefelt Henrik / githubweb
  2. Remove unused command \glossaryitem — Tidefelt Henrik / githubweb
  3. Add missing \lstinline and say "prefix" instead of "keyword" — Tidefelt Henrik / githubweb
  4. Remove hyphen in "'each'-prefix" — Tidefelt Henrik / githubweb
  5. Add more rules to style guide — Tidefelt Henrik / githubweb