Browse Source

Fix link redirections

- Use https instead for http for more links
- Use of github.io instead of github.com where applicable
Kaushal Modi 1 year ago
parent
commit
1dec896872

+ 6 - 6
FIXME/org-people.org

@@ -224,7 +224,7 @@ Over the past decade, I have been studying philosophy, cognitive
 sciences and educational theories.  I'm interested on how to use
 computers for education, and I'm a consultant in this field.
 
-I'm not a programmer but I've been raised in Emacs, so I can read 
+I'm not a programmer but I've been raised in Emacs, so I can read
 some elisp code, fix some bugs and sometimes write a function.
 
 My first Emacs contribution was [[http://directory.fsf.org/project/BHL/][BHL]], a mode to convert plain text to
@@ -467,7 +467,7 @@ In my spare time I play jazz, and even use org-mode to keep lists of
 numbers I would like to try out, contacts for jazz venues, lists of
 forthcoming gigs etc.
 
-A big thank you to Carsten for this superb tool.  
+A big thank you to Carsten for this superb tool.
 
 [[http://www.petephillips.me.uk][Pete Phillips]]
 
@@ -481,8 +481,8 @@ second operating system; the first is [[http://www.debian.org][Debian GNU/Linux]
 is Windows XP (bleah!).
 
 I am a chemist, working in  Bologna, Italy.
-When I am not in the laboratory, I am at the 
-computer writing and reading reports and also the Org-mode 
+When I am not in the laboratory, I am at the
+computer writing and reading reports and also the Org-mode
 mailing list. I pay particular attention to the posts
 concerning Windows.
 
@@ -666,7 +666,7 @@ day :-)
 I was on the holy quest for *the* perfect Personal Information
 Management (PIM) tool for almost decades: primitive Windows and
 GNU/Linux software tools of the 90s, PalmOS (Handspring Deluxe, T3),
-[[http://www.jpilot.org/][J-Pilot]], [[http://en.wikipedia.org/wiki/Sharp_Zaurus][Sharp Zaurus]], Outlook, Desktop-Wikis like [[http://zim-wiki.org/][Zim]] or
+[[http://www.jpilot.org/][J-Pilot]], [[https://en.wikipedia.org/wiki/Sharp_Zaurus][Sharp Zaurus]], Outlook, Desktop-Wikis like [[http://zim-wiki.org/][Zim]] or
 [[http://www.thebrain.com/][Personal Brain]], [[http://freemind.sourceforge.net/wiki/index.php/Main_Page][FreeMind]], and many
 more. Some of them I used pretty intense, some of them I tested only a
 short period of time.
@@ -680,7 +680,7 @@ information should not depend on the storage method/process but rather
 on the re-find/retrieval method/process alone. Tagging seems very
 promising to me.
 
-I am also interested in having something that represents [[http://en.wikipedia.org/wiki/Memex][the old idea
+I am also interested in having something that represents [[https://en.wikipedia.org/wiki/Memex][the old idea
 of a Memex]] which visualizes much of my data in a useful way. Therefore
 I started an extension of Org-mode which is called [[https://github.com/novoid/Memacs][Memacs]]. Please
 visit the project page when you want something easy that integrates

+ 34 - 35
exporters/ox-overview.org

@@ -34,7 +34,7 @@ post]]. This document presents an overview of features, as well as a list of cur
 supported exporter backends. [[https://orgmode.org/manual/Exporting.html#Exporting][Exporting]] and [[https://orgmode.org/manual/Publishing.html#Publishing][publishing]] are also documented in the [[https://orgmode.org/manual/][Org-mode
 manual]]. See [[file:ox-docstrings.org][ox-docstrings]] and [[file:org-element-docstrings.org][org-element-docstrings]] for the extracted
 docstrings from these two core libraries of the new Org-mode exporter, i.e.
-for detailled technical information about the exporter framework. 
+for detailled technical information about the exporter framework.
 
 * List of Org-mode exporters
 
@@ -42,35 +42,35 @@ Please find below a list of current Org-mode exporters, the location of the back
 file (relative to downloaded Org-mode installation directory, =org=) and links Worg and
 Org-mode manual documentation.
 
-| *Name*          | *Exporter location*                | *Worg Tutorial*  | *Org-mode Manual*            |
-|---------------+----------------------------------+----------------+----------------------------|
-| ASCII         | =./lisp/ox-ascii.el=               | ox-ascii       | [[https://orgmode.org/manual/ASCII_002fLatin_002d1_002fUTF_002d8-export.html#ASCII_002fLatin_002d1_002fUTF_002d8-export][ASCII/Latin-1/UTF-8 export]] |
-| [[https://bitbucket.org/rivanvx/beamer/wiki/Home][Beamer]]        | =./lisp/ox-beamer.el=              | [[file:beamer/ox-beamer.org][ox-beamer]]      | [[https://orgmode.org/manual/Beamer-export.html#Beamer-export][Beamer class export]]        |
-| HTML          | =./lisp/ox-html.el=                | ox-html        | [[https://orgmode.org/manual/HTML-export.html#HTML-export][HTML export]]                |
-| [[http://en.wikipedia.org/wiki/ICalendar][iCalendar]]     | =./lisp/ox-icalandar.el=           | ox-icalendar   |                            |
-| [[http://www.latex-project.org/][LaTeX]]         | =./lisp/ox-latex.el=               | ox-latex       | [[https://orgmode.org/manual/LaTeX-and-PDF-export.html#LaTeX-and-PDF-export][LaTeX and PDF export]]       |
-| [[http://manpages.bsd.lv/history.html][Man]]           | =./lisp/ox-man.el=                 | ox-man         |                            |
-| [[http://daringfireball.net/projects/markdown/][Markdown]]      | =./lisp/ox-md.el=                  | ox-md          |                            |
-| [[http://opendocumentformat.org/][ODT]]           | =./lisp/ox-odt.el=                 | ox-odt         | [[https://orgmode.org/manual/OpenDocument-Text-export.html#OpenDocument-Text-export][OpenDocument Text export]]   |
-| [[https://orgmode.org/manual/Publishing.html][Publishing]]    | =./lisp/ox-publish.el=             | ox-publish     | [[https://orgmode.org/manual/Publishing.html#Publishing][Publishing]]                 |
-| [[http://www.gnu.org/software/texinfo/][Texinfo]]       | =./lisp/ox-texinfo.el=             | ox-texinfo     |                            |
-|---------------+----------------------------------+----------------+----------------------------|
-| [[http://www.atlassian.com/software/confluence/overview/team-collaboration-software][Confluence]]    | =./contrib/lisp/ox-confluence.el=  | ox-confluence  |                            |
-| [[http://imakewebthings.com/deck.js/][Deck.js]]       | =./contrib/lisp/ox-deck.el=        | ox-deck        |                            |
-| [[http://freemind.sourceforge.net/wiki/index.php/Main_Page][Freemind]]      | =./contrib/lisp/ox-freemind.el=    | ox-freemind    | [[https://orgmode.org/manual/Freemind-export.html#Freemind-export][Freemind export]]            |
-| [[http://www.gnu.org/software/groff/][Groff]]         | =./contrib/lisp/ox-groff.el=       | ox-groff       |                            |
-| [[http://www.ctan.org/pkg/koma-script][Koma Scrlttr2]] | =./contrib/lisp/ox-koma-letter.el= | ox-koma-letter |                            |
-| [[http://www.rssboard.org/rss-specification][RSS]]           | =./contrib/lisp/ox-rss.el=         | ox-rss         |                            |
-| [[http://meyerweb.com/eric/tools/s5/][S5]]            | =./contrib/lisp/ox-s5.el=          | ox-s5          |                            |
-| [[http://www.taskjuggler.org/][Taskjuggler]]   | =./contrib/lisp/ox-taskjuggler.el= | [[file:taskjuggler/ox-taskjuggler.org][ox-taskjuggler]] | [[https://orgmode.org/manual/TaskJuggler-export.html#TaskJuggler-export][Taskjuggler export]]         |
-|---------------+----------------------------------+----------------+----------------------------|
-| [[http://www.docbook.org/][DocBook]]       | (1)                              | -              | -                          |
+| *Name*        | *Exporter location*                | *Worg Tutorial* | *Org-mode Manual*          |
+|---------------+------------------------------------+-----------------+----------------------------|
+| ASCII         | =./lisp/ox-ascii.el=               | ox-ascii        | [[https://orgmode.org/manual/ASCII_002fLatin_002d1_002fUTF_002d8-export.html#ASCII_002fLatin_002d1_002fUTF_002d8-export][ASCII/Latin-1/UTF-8 export]] |
+| [[https://bitbucket.org/rivanvx/beamer/wiki/Home][Beamer]]        | =./lisp/ox-beamer.el=              | [[file:beamer/ox-beamer.org][ox-beamer]]       | [[https://orgmode.org/manual/Beamer-export.html#Beamer-export][Beamer class export]]        |
+| HTML          | =./lisp/ox-html.el=                | ox-html         | [[https://orgmode.org/manual/HTML-export.html#HTML-export][HTML export]]                |
+| [[https://en.wikipedia.org/wiki/ICalendar][iCalendar]]     | =./lisp/ox-icalandar.el=           | ox-icalendar    |                            |
+| [[http://www.latex-project.org/][LaTeX]]         | =./lisp/ox-latex.el=               | ox-latex        | [[https://orgmode.org/manual/LaTeX-and-PDF-export.html#LaTeX-and-PDF-export][LaTeX and PDF export]]       |
+| [[http://manpages.bsd.lv/history.html][Man]]           | =./lisp/ox-man.el=                 | ox-man          |                            |
+| [[http://daringfireball.net/projects/markdown/][Markdown]]      | =./lisp/ox-md.el=                  | ox-md           |                            |
+| [[http://opendocumentformat.org/][ODT]]           | =./lisp/ox-odt.el=                 | ox-odt          | [[https://orgmode.org/manual/OpenDocument-Text-export.html#OpenDocument-Text-export][OpenDocument Text export]]   |
+| [[https://orgmode.org/manual/Publishing.html][Publishing]]    | =./lisp/ox-publish.el=             | ox-publish      | [[https://orgmode.org/manual/Publishing.html#Publishing][Publishing]]                 |
+| [[http://www.gnu.org/software/texinfo/][Texinfo]]       | =./lisp/ox-texinfo.el=             | ox-texinfo      |                            |
+|---------------+------------------------------------+-----------------+----------------------------|
+| [[http://www.atlassian.com/software/confluence/overview/team-collaboration-software][Confluence]]    | =./contrib/lisp/ox-confluence.el=  | ox-confluence   |                            |
+| [[http://imakewebthings.com/deck.js/][Deck.js]]       | =./contrib/lisp/ox-deck.el=        | ox-deck         |                            |
+| [[http://freemind.sourceforge.net/wiki/index.php/Main_Page][Freemind]]      | =./contrib/lisp/ox-freemind.el=    | ox-freemind     | [[https://orgmode.org/manual/Freemind-export.html#Freemind-export][Freemind export]]            |
+| [[http://www.gnu.org/software/groff/][Groff]]         | =./contrib/lisp/ox-groff.el=       | ox-groff        |                            |
+| [[http://www.ctan.org/pkg/koma-script][Koma Scrlttr2]] | =./contrib/lisp/ox-koma-letter.el= | ox-koma-letter  |                            |
+| [[http://www.rssboard.org/rss-specification][RSS]]           | =./contrib/lisp/ox-rss.el=         | ox-rss          |                            |
+| [[http://meyerweb.com/eric/tools/s5/][S5]]            | =./contrib/lisp/ox-s5.el=          | ox-s5           |                            |
+| [[http://www.taskjuggler.org/][Taskjuggler]]   | =./contrib/lisp/ox-taskjuggler.el= | [[file:taskjuggler/ox-taskjuggler.org][ox-taskjuggler]]  | [[https://orgmode.org/manual/TaskJuggler-export.html#TaskJuggler-export][Taskjuggler export]]         |
+|---------------+------------------------------------+-----------------+----------------------------|
+| [[http://www.docbook.org/][DocBook]]       | (1)                                | -               | -                          |
 
 - (1) DocBook export, available in previous Org-mode versions, has not currently been ported
   to the new exporter, however the new =ox-texinfo= backend can generate DocBook
   format. Once =file.texi= is created via =ox-texinfo=, simply execute:
 
-#+begin_example 
+#+begin_example
 makeinfo --docbook file.texi
 #+end_example
 
@@ -84,7 +84,7 @@ makeinfo --docbook file.texi
 
 Here is the [[http://article.gmane.org/gmane.emacs.orgmode/65574][email text]] to allow for easy reference in this document. The contents of his
 email should end up in this document somehow or another, as this should serve as the
-primary source of information in addition to the manual for the exporter in general. 
+primary source of information in addition to the manual for the exporter in general.
 
 If you migrate some information to this actual document, please delete it so that the quote below serves as a
 body of "todo" text.
@@ -132,11 +132,11 @@ transition.
   and back-ends and “org-e-” becomes “ox-” in files. To sum it up:
 
        ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-                  Old name                      New name         
+                  Old name                      New name
        ───────────────────────────────────────────────────────────
-                   e-latex                       latex           
-                 org-e-latex                    ox-latex         
-        org-export-latex-packages-alist  org-latex-packages-alist 
+                   e-latex                       latex
+                 org-e-latex                    ox-latex
+        org-export-latex-packages-alist  org-latex-packages-alist
        ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
     Be sure to check filters and requires in your configuration files.
@@ -207,14 +207,14 @@ transition.
   │ #+CAPTION: A table
   │ #+NAME: table
   │ | a | b |
-  │ 
+  │
   │ #+CAPTION: Another table
   │ #+NAME: other-table
   │ | c | d |
-  │ 
+  │
   │ 1. <<itm>>item 1
   │ 2. item 2
-  │ 
+  │
   │ Look at item [[itm]]! It happens after table [[other-table]].
   ╰────
 
@@ -392,7 +392,7 @@ transition.
   │ 15             "^" (if utf8p "│ " "| ")
   │ 16             (org-element-normalize-string
   │ 17              (org-export-format-code-default src-block info)))))))))
-  │ 18  
+  │ 18
   │ 19  (org-export-define-derived-backend my-ascii parent
   │ 20    :translate-alist ((src-block . my-ascii-src-block)))
   ╰────
@@ -441,4 +441,3 @@ Footnotes
 [1] Though, it will expect a caption to be properly numbered.
 
 #+end_quote
-

+ 17 - 18
exporters/taskjuggler/ox-taskjuggler.org

@@ -1,7 +1,7 @@
 #+OPTIONS:    H:3 num:nil toc:t \n:nil ::t |:t ^:t -:t f:t *:t tex:t d:(HIDE) tags:not-in-toc
 #+STARTUP:    align fold nodlcheck oddeven lognotestate
 #+SEQ_TODO:   TODO(t) INPROGRESS(i) WAITING(w@) | DONE(d) CANCELED(c@)
-#+TAGS:       Write(w) Update(u) Fix(f) Check(c) 
+#+TAGS:       Write(w) Update(u) Fix(f) Check(c)
 #+TITLE:      Exporting Gantt charts with Taskjuggler v3 (tj3)
 #+AUTHOR:     John Henderson
 #+EMAIL:      jw DOT hendy AT gmail DOT com
@@ -20,7 +20,7 @@ self-described as follows (from the project website):
 #+begin_quote
 TaskJuggler is a modern and powerful, Free and Open Source Software project management
 tool. Its new approach to project planning and tracking is more flexible and superior to
-the commonly used Gantt chart editing tools. 
+the commonly used Gantt chart editing tools.
 #+end_quote
 
 A [[https://orgmode.org/worg/org-tutorials/org-taskjuggler.html][tutorial already exists]] for the use of Org-mode and Taskjuggler v2.4.3, the last release of the
@@ -28,7 +28,7 @@ v2.x.x series. Taskjuggler Version 3 (often referred to as simply "tj3"), was re
 longer features the former [[http://qt-project.org/][Qt]]-based GUI for task/timeline management of a project.
 
 It should also be mentioned that the project is now [[http://www.taskjuggler.org/manual/change_log.html#version_1_0_0][10 years old]], and, as a result, is
-[[http://taskjuggler.org/tj3/manual/toc.html][fantastically documented]]. 
+[[http://taskjuggler.org/tj3/manual/toc.html][fantastically documented]].
 
 The [[https://orgmode.org/manual/TaskJuggler-export.html][Org-mode manual coverage of Taskjuggler]] covers Taskjuggler export to some extent,
 however the defaults assume the use of version 2.x.x. This tutorial will lay out
@@ -56,7 +56,7 @@ route. For example, the Arch Linux User Repository ([[https://aur.archlinux.org/
 
 Once installed, you should check functionality by typing:
 
-#+begin_example 
+#+begin_example
 
 tj3 --version
 
@@ -64,7 +64,7 @@ tj3 --version
 
 If you just can't wait to see what tj3 can do, try compiling their [[http://taskjuggler.org/tj3/examples/Tutorial/tutorial.tjp][sample file]]:
 
-- Copy/paste into a file called =something.tjp=. Alternatively, 
+- Copy/paste into a file called =something.tjp=. Alternatively,
 
 #+begin_example
 
@@ -101,7 +101,7 @@ In addition, here are a list of current variables you can customize:
 - org-taskjuggler-default-project-version
 - ~org-taskjuggler-default-reports~: sets a report file to use. This may be written in
      text format (as in, the variable set to the full report text string), or (perhaps
-     easier) to a [[http://www.taskjuggler.org/tj3/manual/include.properties.html][=.tji= file containing the report definition]]. 
+     easier) to a [[http://www.taskjuggler.org/tj3/manual/include.properties.html][=.tji= file containing the report definition]].
 - org-taskjuggler-extension
 - org-taskjuggler-final-hook
 - org-taskjuggler-keep-project-as-task
@@ -142,9 +142,9 @@ particularly helpful:
   days, length observes definitions of work weeks (so a length of =7d= with a 5-day work
   week specified translates to =9d= calendar time. Effort requires at least one resource
   defined and assigned to the task, and will use his/her available work time/day to figure
-  out how long the task will take. 
+  out how long the task will take.
+
 
-  
 * Mapping of Taskjuggler syntax to Org-mode
 
 If you are familiar with Taskjuggler, it may be helpful to understand how Taskjuggler
@@ -161,7 +161,7 @@ something like this:
 task entry_door "Install entry door" {
   depends buy_door
   effort 4h
-}  
+}
 
 #+end_example
 
@@ -269,7 +269,7 @@ efforts for each task. By using column view this can be done very
 efficiently. It also helps to define the =COLUMNS= and default values
 for the Effort property as shown in the following screen shot:
 
-#+CAPTION: Estimating effort using column view 
+#+CAPTION: Estimating effort using column view
 #+ATTR_HTML: alt="Estimating effort using column view"
 [[file:../images/taskjuggler/effort-estimation.png]]
 
@@ -277,7 +277,7 @@ Your resulting Org mode project file will look somewhat like the
 following:
 
 #+BEGIN_SRC org
-,#+PROPERTY: Effort_ALL 2d 5d 10d 20d 30d 35d 50d 
+,#+PROPERTY: Effort_ALL 2d 5d 10d 20d 30d 35d 50d
 ,#+COLUMNS: %70ITEM(Task) %Effort
 
 ,* Accounting Software
@@ -339,7 +339,7 @@ following:
 This allows you to have other nodes for this project such as an
 introduction or general notes.
 
-To export the project to TaskJuggler you simply type 
+To export the project to TaskJuggler you simply type
 
 : M-x org-export-as-taskjuggler-and-open
 
@@ -423,7 +423,7 @@ Obviously we need to define dependencies between the tasks.
 ** Define dependencies
 There are several ways to define dependencies between tasks. When
 coming from an Org mode background you probably want to define them
-using the facilities provided by Org mode, which are either 
+using the facilities provided by Org mode, which are either
 
   - The =ORDERED= property which allows you to state that the child
     tasks have to be completed in the order they appear (top most
@@ -431,14 +431,14 @@ using the facilities provided by Org mode, which are either
 
   - The =BLOCKER= property which allows you to state that a task
     depends on either
-    - a previous sibling ("previous-sibling") or 
+    - a previous sibling ("previous-sibling") or
     - any other task by stating the ~task_id~ property of the
       predecessor
 
 Again, it is probably easiest to define the dependencies using the
 column view as shown below in the screen shot:
 
-#+CAPTION: Defining dependencies using column view 
+#+CAPTION: Defining dependencies using column view
 #+ATTR_HTML: alt="Defining dependencies using column view"
 [[file:../images/taskjuggler/define-dependencies.png]]
 
@@ -453,7 +453,7 @@ to Customer" which is waiting until the Beta test and the Manual are
 done.
 
 #+BEGIN_SRC org
-,#+PROPERTY: Effort_ALL 2d 5d 10d 20d 30d 35d 50d 
+,#+PROPERTY: Effort_ALL 2d 5d 10d 20d 30d 35d 50d
 ,#+PROPERTY: allocate_ALL dev doc test
 ,#+COLUMNS: %30ITEM(Task) %Effort %allocate %BLOCKER %ORDERED
 
@@ -582,7 +582,7 @@ will be and what they are working on. See below for a screen shot:
 [[file:../images/taskjuggler/resource-graph.png]]
 
 Finally you can generate [[file:../images/taskjuggler/project-plan.pdf][good-looking project plans]] in PDF by printing
-from TaskJuggler. This will make any [[http://en.wikipedia.org/wiki/Pointy-haired_Boss][Pointy-haired Boss]] happy.
+from TaskJuggler. This will make any [[https://en.wikipedia.org/wiki/Pointy-haired_Boss][Pointy-haired Boss]] happy.
 
 ** Export of other properties
 Generally the exporter writes a node property that is known to
@@ -750,4 +750,3 @@ to generate (by default, a ~taskreport~).
 
 For more information and examples see the Org-taskjuggler tutorial at
 https://orgmode.org/worg/org-tutorials/org-taskjuggler.html.
-

+ 1 - 1
index.org

@@ -106,7 +106,7 @@ A collection of generally useful code blocks available as a [[file:library-of-ba
 - [[file:org-blog-articles.org][Blog posts]]              : Read a variety of articles from introductions to
   specific customizations
 - [[file:org-hacks.org][Org-mode Hacks]]          : Copy code snippets from other users
-- [[file:org-contrib/babel/index.org][Org Babel]] : Learn about [[http://en.wikipedia.org/wiki/Literate_programming][Literate programming]] within Org-mode
+- [[file:org-contrib/babel/index.org][Org Babel]] : Learn about [[https://en.wikipedia.org/wiki/Literate_programming][Literate programming]] within Org-mode
 - Tools
   - [[file:org-translators.org][Org-mode conversion tools]]  : Import into and export out of Org-mode
   - [[file:org-tools/index.org][Org-mode parsing libraries]] : Parse and analyze .org files

+ 13 - 13
org-contrib/babel/examples/ascii.org

@@ -1,7 +1,7 @@
 #+OPTIONS:    H:3 num:nil toc:2 \n:nil ::t |:t ^:{} -:t f:t *:t tex:t d:(HIDE) tags:not-in-toc
 #+STARTUP:    align fold nodlcheck hidestars oddeven lognotestate hideblocks
 #+SEQ_TODO:   TODO(t) INPROGRESS(i) WAITING(w@) | DONE(d) CANCELED(c@)
-#+TAGS:       Write(w) Update(u) Fix(f) Check(c) 
+#+TAGS:       Write(w) Update(u) Fix(f) Check(c)
 #+TITLE:      Org-babel: Uses
 #+AUTHOR:     David Hajage
 #+EMAIL:      dhajage at gmail dot com
@@ -14,7 +14,7 @@
  [[http://cran.r-project.org/web/packages/ascii/index.html][=ascii=]] package (available on [[http://cran.r-project.org/][CRAN]]) creates appropriate plain text
  representations of many =R= objects, and features an option to specify
  that the plain text representations should be in Org format (as well
- as [[http://www.methods.co.nz/asciidoc/][asciidoc]], [[http://txt2tags.sourceforge.net/][txt2tags]], [[http://docutils.sourceforge.net/rst.html][restructuredtext]] and [[http://en.wikipedia.org/wiki/Textile_(markup_language)][textile]]). This can be
+ as [[http://www.methods.co.nz/asciidoc/][asciidoc]], [[http://txt2tags.sourceforge.net/][txt2tags]], [[http://docutils.sourceforge.net/rst.html][restructuredtext]] and [[https://en.wikipedia.org/wiki/Textile_(markup_language)][textile]]). This can be
  particularly useful for retrieving non-tabular =R= data structures in
  Org.
 
@@ -43,8 +43,8 @@ Then, use =ascii= function:
 #+end_src
 
 #+results[7a8dbb1c07076d9824022708eb216504d41fd3da]: ascii-example2
-- Number of cases in table: 4 
-- Number of factors: 2 
+- Number of cases in table: 4
+- Number of factors: 2
 - Test for independence of all factors:
   - Chisq = 12, df = 9, p-value = 0.2133
   - Chi-squared approximation may be incorrect
@@ -61,12 +61,12 @@ ascii(glm.D93)
 
 #+results[bd61c121c58d9a7dc9eca128993a430e29db3cdf]: ascii-example3
 |             | Estimate | Std. Error | z value | Pr(> \vert z \vert ) |
-|-------------+----------+------------+---------+----------------------|
-| (Intercept) |     3.04 |       0.17 |   17.81 |                 0.00 |
-| outcome2    |    -0.45 |       0.20 |   -2.25 |                 0.02 |
-| outcome3    |    -0.29 |       0.19 |   -1.52 |                 0.13 |
-| treatment2  |     0.00 |       0.20 |    0.00 |                 1.00 |
-| treatment3  |     0.00 |       0.20 |    0.00 |                 1.00 |
+|-------------+----------+------------+---------+--------------|
+| (Intercept) |     3.04 |       0.17 |   17.81 |         0.00 |
+| outcome2    |    -0.45 |       0.20 |   -2.25 |         0.02 |
+| outcome3    |    -0.29 |       0.19 |   -1.52 |         0.13 |
+| treatment2  |     0.00 |       0.20 |    0.00 |         1.00 |
+| treatment3  |     0.00 |       0.20 |    0.00 |         1.00 |
 #+name: ascii-example4
 #+begin_src R :results output org :session ascii
 ascii(anova(glm.D93))
@@ -90,11 +90,11 @@ ascii(anova(glm.D93))
 - other attached packages :: ascii_0.6-3, proto_0.3-8
 * With =Sweave=
   =ascii= package provides a =[[http://www.stat.uni-muenchen.de/~leisch/Sweave/][Sweave]]= driver for org markup.
-  
+
   When using =Sweave=, just replace =RweaveLatex= driver by =RweaveOrg=:
-  
+
 :  Sweave("yourfile.Rnw", driver = RweaveOrg)
-  
+
 * Bug
 ** Cell spanning
    I am not an Org Mode guru, but as much I can know, Org Mode doesn't

+ 13 - 15
org-contrib/babel/examples/org-babel-gnuplot.org

@@ -44,7 +44,7 @@ alternative to babel. Instructions already exist on Worg for this.[fn:2] The
 .org file used to create the org-plot Worg entry is linked in the
 Introduction on that page and can be very helpful in getting a feel
 for using gnuplot by using the =#+PLOT= header above a table. This
-page, in contrast, is about using gnuplot in its "native" form. 
+page, in contrast, is about using gnuplot in its "native" form.
 
 To do this, babel support for the gnuplot language must be
 enabled. Versions of Org-mode prior to 7.01 required enabling /both/
@@ -170,7 +170,7 @@ set xtics ("Tic 1" -1, "Tic 2" 10, "Tic 3" 1001)
 The gnuplot default is for tics to show up on both sides and the top and
 bottom of the graph. In other words, the tics on the left y-axis and
 bottom x-axis are "mirrored" to the opposing side of the plot
-borders. Stop this (tics only on left/bottom) by using: 
+borders. Stop this (tics only on left/bottom) by using:
 #+begin_example
 set xtics nomirror
 set ytics nomirror
@@ -371,7 +371,7 @@ plot data u 1:2 w p lw 2 title 'x vs. y1', \
 Sometimes it's desireable to have text as the x-values/xtics instead of
 numbers.[fn:8] Gnuplot will plot a column of text entries as the x-values for
 its points by spacing the named values evenly along the axis. Here's
-an example of a running distance log:[fn:6] 
+an example of a running distance log:[fn:6]
 
 #+attr_html: width="800"
 [[https://orgmode.org/worg/images/babel/gnuplot-named-xtics.png]]
@@ -392,7 +392,7 @@ an example of a running distance log:[fn:6]
   reset
 
   set title "Running Stats"
-  
+
   set xlabel "Date"
   set xtics rotate by -45
 
@@ -446,7 +446,7 @@ values should correspond to these x-values. Here is an example:
   set xlabel "Wars in Time"
 
   set title 'War Deaths'
-  
+
   plot data using 2:3:xticlabels(1) w p lw 3 notitle
 #+end_src
 
@@ -457,7 +457,7 @@ For multiple data sets, simply include multiple columns for y-values
 to be plotted and plot each data set with the syntax
 =x:y:xticlabels(col #)=. Most likely, the =col #= will be the same for
 all data sets (the column of names for xtics will probably remain the
-same). Here is an example: 
+same). Here is an example:
 #+begin_example
 plot data u 2:3:xticlabels(1) title 'Set1',\
 data u 2:4:xticlabels(1) title 'Set2', \
@@ -647,7 +647,7 @@ Walking through the code:
     graph for the next two slices
   - =set origin= tells gnuplot to start the plot at the bottom left (0,0)
   - =lmargin= is set for 10 (standard) but =rmargin= is set at 0 in
-    order to let the left edge of the middle slice sit 
+    order to let the left edge of the middle slice sit
     against the right edge of the left-most slice with no gap
   - The =ylabel= is set here, and only once. Each slice is
     treated as a separate graph, and setting it for each slice creates
@@ -701,7 +701,7 @@ previous footnote above presents such case.[fn:11]
 
 ** Broken X-Axis
 Arrows can be used quite cleverly to "break" axes.[fn:13] [fn:14] [fn:15] The method involves drawing 6 arrows to "break" both the top
-and bottom x-axes: 2 diagonal and 1 white per axis to create the illusion of a break. 
+and bottom x-axes: 2 diagonal and 1 white per axis to create the illusion of a break.
 
 While the following is not /really/ to scale, the example of a
 far distant date with a broken line and then some recent dates shows
@@ -783,14 +783,14 @@ Here are some notes on the above:
   gnuplot-tricks blog for how to do this with a continuous function
   (e.g. sin x) and an "offset" variable for the same effect.[fn:14]
 
-In the case above, the x-axis is "cheated" in that it is not only 
+In the case above, the x-axis is "cheated" in that it is not only
 broken, but the scale is artificially manipulated. In the data chart,
 there should have been population values at 10,000 BC, 5,000 BC, and 1
 AD. Instead they occur at 1600, 1650 and 1700 AD. The spacing is proportionate, but scaled by 100x
 (50 years apart vs. 5,000). Compared to the plot from 1750-2005, it's
 obviously not the same x-axis scale. If the actual data points were
 used, the later data points would have been significantly "scrunched."
-While not technically correct, it's perhaps more visually appealing, especially where scale is 
+While not technically correct, it's perhaps more visually appealing, especially where scale is
 not too important. To get the point across, it does the job very well:
 left of break was not much growth, then in a much smaller time scale
 to the right of the break, much population growth occurred. The
@@ -814,7 +814,7 @@ document. The use of =reset= at the beginning of each gnuplot block
 eliminates these issues by clearing any "residual options" from previously generated output.
 
 ** Image Quality
-For many graphs, output to .png (with =:file filename.png= in the header) may be 
+For many graphs, output to .png (with =:file filename.png= in the header) may be
 sufficient. Sometimes, however, the generated image quality is not
 acceptable. The mailing list provided an excellent solution
 for increased gnuplot image quality:[fn:16]
@@ -834,7 +834,7 @@ terminal...= command used. This creates a higher resolution .eps image instead o
 =color= option, the output will default to monochrome (black and
 white). The =solid= option can be used to keep all linestyles as solid
 lines; without it, gnuplot will cycle through various styles of
-dashes/shapes/etc. 
+dashes/shapes/etc.
 
 Once the .eps file is generated, ImageMagick can be used to convert
 it to .png:[fn:17]
@@ -866,7 +866,7 @@ convert -density 300 file.eps file.png
 
 [fn:11] http://t16web.lanl.gov/Kawano/gnuplot/plot6-e.html
 
-[fn:12] Wikipedia: http://en.wikipedia.org/wiki/World_population#Population_by_region_2
+[fn:12] Wikipedia: https://en.wikipedia.org/wiki/World_population#Population_by_region_2
 
 [fn:13] http://gnuplot-tricks.blogspot.com/2009/05/gnuplot-tricks-many-say-that-it-is.html
 
@@ -879,5 +879,3 @@ convert -density 300 file.eps file.png
 [fn:17] http://www.imagemagick.org/script/index.php
 
 [fn:18] http://www.mail-archive.com/emacs-orgmode@gnu.org/msg29903.html
-
-

+ 1 - 1
org-contrib/babel/examples/org-check.org

@@ -174,7 +174,7 @@ Check an Org-mode environment.
     - if =chk-sys-cmd= returns =fail= then you should check to see if
       R is installed on your system
 *** C language configuration
-    - [[http://en.wikipedia.org/wiki/C_%28programming_language%29][C]] is a general-purpose computer programming language
+    - [[https://en.wikipedia.org/wiki/C_%28programming_language%29][C]] is a general-purpose computer programming language
     - if =chk-babel-lang= returns =fail= then you should add this line
       to =.emacs=
 #+begin_src emacs-lisp

+ 7 - 7
org-contrib/babel/index.org

@@ -16,14 +16,14 @@ life as Org-babel, an extension to Org-mode.  It was integrated into
 the Org-mode core at version 7.0. The author of Babel is Eric
 Schulte. The secondary author is Dan Davison.
 
-- [[http://www.jstatsoft.org/v46/i03][A Multi-Language Computing Environment for Literate Programming and
+- [[https://www.jstatsoft.org/article/view/v046i03][A Multi-Language Computing Environment for Literate Programming and
   Reproducible Research]]: a journal paper providing the most up to date
   and complete introduction to using Org-mode and Babel for
   Reproducible research and literate programming.
 - [[file:intro.org][Introductory Tutorial]]: a smaller online set of installation and
   setup instructions, as well as an overview of the main features of
   Babel, with plenty of examples.
-- [[https://orgmode.org/manual/Working-With-Source-Code.html#Working-With-Source-Code][Reference and Documentation]]: is available online and in Chapter 14
+- [[https://orgmode.org/manual/Working-with-source-code.html][Reference and Documentation]]: is available online and in Chapter 14
   of the Org-mode manual. Some more information on using header args
   and result types for Babel code blocks can be found [[file:header-args.org][here]].
 - [[file:languages.org][Languages]]: list of supported languages with information on
@@ -32,19 +32,19 @@ Schulte. The secondary author is Dan Davison.
 - [[file:uses.org][Uses]]: user-submitted examples of Babel work flows -- this is a good
   place to get an idea of what can be done and see how Babel may fit
   into your life.  In addition there is a collection of small code
-  block examples and scraps at [[http://eschulte.github.com/org-scraps/][org-scraps]].
+  block examples and scraps at [[http://eschulte.github.io/org-scraps/][org-scraps]].
 
 ------------------------------------------------------------------------
 
 #+begin_export html
-  <div style="clear: both;"></div> 
+  <div style="clear: both;"></div>
   <div id="logo1" style="float: left; text-align: center; max-width:
                          300px; font-size: 8pt; margin-top: 1em;">
     <p>
       <img src="../../images/babel/tower-of-babel.png"  alt="Tower of Babel"/>
       <div id="attr" style="margin: -0.5em;">
         The Tower of Babel by
-        <a href="http://commons.wikimedia.org/wiki/Pieter_Brueghel_the_Elder" title="">
+        <a href="https://commons.wikimedia.org/wiki/Pieter_Brueghel_the_Elder" title="">
           <b>Pieter Brueghel the Elder</b>
         </a>
       </div>
@@ -63,8 +63,8 @@ Schulte. The secondary author is Dan Davison.
       <p>
         The Babel Fish is small, yellow, and simultaneously translates
         from one spoken language to another.
-      </p> 
-      <p> 
+      </p>
+      <p>
         &ndash; The Hitchhiker's Guide to the Galaxy, Douglas Adams
       </p>
     </p>

+ 2 - 2
org-contrib/babel/intro.org

@@ -906,7 +906,7 @@ other.
  -- Donald Knuth
 #+end_quote
 
-Babel supports [[http://en.wikipedia.org/wiki/Literate_programming][Literate Programming]] (LP) by allowing the act of
+Babel supports [[https://en.wikipedia.org/wiki/Literate_programming][Literate Programming]] (LP) by allowing the act of
 programming to take place inside of Org-mode documents.  The Org-mode
 file can then be exported (*woven* in LP speak) to HTML or LaTeX for
 consumption by a human, and the embedded source code can be extracted
@@ -1123,7 +1123,7 @@ entire document becomes executable.  This makes it possible, and natural, to
 distribute research in a format that encourages readers to recreate
 results and perform their own analyses.
 
-One notable existing RR tool is [[http://en.wikipedia.org/wiki/Sweave][Sweave]], which provides a mechanism for
+One notable existing RR tool is [[https://en.wikipedia.org/wiki/Sweave][Sweave]], which provides a mechanism for
 embedding [[http://www.r-project.org/][R]] code into LaTeX documents.  Sweave is a mature
 and very useful tool, but we believe that Babel has several
 advantages:

+ 13 - 15
org-contrib/babel/languages/ob-doc-gnuplot.org

@@ -41,7 +41,7 @@ will produce matching images in the same directory as the .org file.
 
 * Requirements and Setup
 
-# To get gnuplot up and running, you need... gnuplot. 
+# To get gnuplot up and running, you need... gnuplot.
 
 Babel support for gnuplot requires that [[http://www.gnuplot.info/][gnuplot]] be installed on your
 system, along with [[https://github.com/rudi/gnuplot-el][gnuplot.el]], an =Emacs= major mode for interacting
@@ -192,7 +192,7 @@ set xtics ("Tic 1" -1, "Tic 2" 10, "Tic 3" 1001)
 The gnuplot default is for tics to show up on both sides and the top and
 bottom of the graph. In other words, the tics on the left y-axis and
 bottom x-axis are "mirrored" to the opposing side of the plot
-borders. Stop this (tics only on left/bottom) by using: 
+borders. Stop this (tics only on left/bottom) by using:
 #+begin_example
 set xtics nomirror
 set ytics nomirror
@@ -390,7 +390,7 @@ plot data u 1:2 w p lw 2 title 'x vs. y1', \
 Sometimes it's desireable to have text as the x-values/xtics instead of
 numbers.[fn:8] Gnuplot will plot a column of text entries as the x-values for
 its points by spacing the named values evenly along the axis. Here's
-an example of a running distance log:[fn:6] 
+an example of a running distance log:[fn:6]
 
 #+attr_html: :width 800
 [[https://orgmode.org/worg/org-contrib/babel/images/gnuplot-named-xtics.png]]
@@ -412,7 +412,7 @@ an example of a running distance log:[fn:6]
   reset
 
   set title "Running Stats"
-  
+
   set xlabel "Date"
   set xtics rotate by -45
 
@@ -465,7 +465,7 @@ values should correspond to these x-values. Here is an example:
   set xlabel "Wars in Time"
 
   set title 'War Deaths'
-  
+
   plot data using 2:3:xticlabels(1) w p lw 3 notitle
 #+end_src
 #+end_example
@@ -474,7 +474,7 @@ For multiple data sets, simply include multiple columns for y-values
 to be plotted and plot each data set with the syntax
 =x:y:xticlabels(col #)=. Most likely, the =col #= will be the same for
 all data sets (the column of names for xtics will probably remain the
-same). Here is an example: 
+same). Here is an example:
 #+begin_example
 plot data u 2:3:xticlabels(1) title 'Set1',\
 data u 2:4:xticlabels(1) title 'Set2', \
@@ -661,7 +661,7 @@ Walking through the code:
     graph for the next two slices
   - =set origin= tells gnuplot to start the plot at the bottom left (0,0)
   - =lmargin= is set for 10 (standard) but =rmargin= is set at 0 in
-    order to let the left edge of the middle slice sit 
+    order to let the left edge of the middle slice sit
     against the right edge of the left-most slice with no gap
   - The =ylabel= is set here, and only once. Each slice is
     treated as a separate graph, and setting it for each slice creates
@@ -715,7 +715,7 @@ previous footnote above presents such case.[fn:11]
 
 ** Broken X-Axis
 Arrows can be used quite cleverly to "break" axes.[fn:13] [fn:14] [fn:15] The method involves drawing 6 arrows to "break" both the top
-and bottom x-axes: 2 diagonal and 1 white per axis to create the illusion of a break. 
+and bottom x-axes: 2 diagonal and 1 white per axis to create the illusion of a break.
 
 While the following is not /really/ to scale, the example of a
 far distant date with a broken line and then some recent dates shows
@@ -796,14 +796,14 @@ Here are some notes on the above:
   gnuplot-tricks blog for how to do this with a continuous function
   (e.g. sin x) and an "offset" variable for the same effect.[fn:14]
 
-In the case above, the x-axis is "cheated" in that it is not only 
+In the case above, the x-axis is "cheated" in that it is not only
 broken, but the scale is artificially manipulated. In the data chart,
 there should have been population values at 10,000 BC, 5,000 BC, and 1
 AD. Instead they occur at 1600, 1650 and 1700 AD. The spacing is proportionate, but scaled by 100x
 (50 years apart vs. 5,000). Compared to the plot from 1750-2005, it's
 obviously not the same x-axis scale. If the actual data points were
 used, the later data points would have been significantly "scrunched."
-While not technically correct, it's perhaps more visually appealing, especially where scale is 
+While not technically correct, it's perhaps more visually appealing, especially where scale is
 not too important. To get the point across, it does the job very well:
 left of break was not much growth, then in a much smaller time scale
 to the right of the break, much population growth occurred. The
@@ -831,7 +831,7 @@ block eliminates these issues by clearing any "residual options" from
 previously generated output.
 
 ** Image Quality
-For many graphs, output to .png (with =:file filename.png= in the header) may be 
+For many graphs, output to .png (with =:file filename.png= in the header) may be
 sufficient. Sometimes, however, the generated image quality is not
 acceptable. The mailing list provided an excellent solution
 for increased gnuplot image quality:[fn:16]
@@ -851,7 +851,7 @@ terminal...= command used. This creates a higher resolution .eps image instead o
 =color= option, the output will default to monochrome (black and
 white). The =solid= option can be used to keep all linestyles as solid
 lines; without it, gnuplot will cycle through various styles of
-dashes/shapes/etc. 
+dashes/shapes/etc.
 
 Once the .eps file is generated, ImageMagick can be used to convert
 it to .png:[fn:17]
@@ -883,7 +883,7 @@ convert -density 300 file.eps file.png
 
 [fn:11] http://t16web.lanl.gov/Kawano/gnuplot/plot6-e.html
 
-[fn:12] Wikipedia: http://en.wikipedia.org/wiki/World_population#Population_by_region_2
+[fn:12] Wikipedia: https://en.wikipedia.org/wiki/World_population#Population_by_region_2
 
 [fn:13] http://gnuplot-tricks.blogspot.com/2009/05/gnuplot-tricks-many-say-that-it-is.html
 
@@ -898,5 +898,3 @@ convert -density 300 file.eps file.png
 [fn:18] http://www.mail-archive.com/emacs-orgmode@gnu.org/msg29903.html
 
 [fn:19] http://www.mail-archive.com/emacs-orgmode@gnu.org/msg30080.html
-
-

+ 14 - 15
org-contrib/babel/languages/ob-doc-lilypond.org

@@ -25,8 +25,8 @@
 
 * Introduction
 
-An /Emacs Org Babel language/ - provided to allow [[http://lilypond.org][LilyPond]] Music Score generation, complete 
-with optional auditioning via Midi, whilst leveraging the full power of Org mode, and [[http://en.wikipedia.org/wiki/Literate_programming][Literate Programming]].
+An /Emacs Org Babel language/ - provided to allow [[http://lilypond.org][LilyPond]] Music Score generation, complete
+with optional auditioning via Midi, whilst leveraging the full power of Org mode, and [[https://en.wikipedia.org/wiki/Literate_programming][Literate Programming]].
 
 * Usage
 
@@ -36,15 +36,15 @@ There are two modes available with ob-lilypond
 
   - *arrange-mode*
 
-Which you use depends on what you intend to do. 
+Which you use depends on what you intend to do.
 (A quick way to switch modes is via `M-x ly-toggle-arrange-mode').
 
 * basic-mode
 
-*basic-mode* (the default) allows you to embed LilyPond snippets into an Org-mode file, and 
+*basic-mode* (the default) allows you to embed LilyPond snippets into an Org-mode file, and
 compile and export them using typical Org-mode commands (such as *C-c
-C-e d* for pdf export). This is useful if you want to mix 
-blocks of Lilypond-generated score with text, and perhaps other images for export to Latex, 
+C-e d* for pdf export). This is useful if you want to mix
+blocks of Lilypond-generated score with text, and perhaps other images for export to Latex,
 Docbook, pdf, or HTML. In other words, *basic-mode* could be used as a
 very flexible replacement to *lilypond-book*.
 
@@ -54,12 +54,12 @@ very flexible replacement to *lilypond-book*.
 
 : #+begin_src lilypond :file Mixolydian.png
 :
-:   \relative c’ { 
-:     g a b c d e f g f e d c b a g a b c d e f g f e d c b a g1 
+:   \relative c’ {
+:     g a b c d e f g f e d c b a g a b c d e f g f e d c b a g1
 :  }
 
 The previous block will produce an image file in .png format, which
-would be suitable for exporting to HTML for instance. 
+would be suitable for exporting to HTML for instance.
 
 To generate a nice image for embedding into a pdf or Latex document,
 you might consider using the .eps format as shown in the example
@@ -67,8 +67,8 @@ below.
 
 : #+begin_src lilypond :file Mixolydian.eps
 :
-:   \relative c’ { 
-:     g a b c d e f g f e d c b a g a b c d e f g f e d c b a g1 
+:   \relative c’ {
+:     g a b c d e f g f e d c b a g a b c d e f g f e d c b a g1
 :  }
 
 * Examples
@@ -95,7 +95,7 @@ is initialted with the sequence *C-c C-e* (standard Org-mode export keys).
 organising sections of the piece using typical Org-mode techniques. And because
 you are in Org-mode, you are free to use Literate Programming
 techniques to generate things programatically - store information in
-tables etc. 
+tables etc.
 
 In addition, there are automated features to automatically audition
 the piece (via MIDI) and or display the resultant pdf output.
@@ -163,7 +163,7 @@ file):
 :     (emacs-lisp . t)
 :     (sh t)
 :     (org t)
-:     (lilypond t))) 
+:     (lilypond t)))
 
 Alternatively you may *require* the ob-lilypond babel language directly:
 
@@ -189,8 +189,7 @@ Tests are provided and can be executed by running the following commands...
 (for more help and information on testing see [[file:../../../org-tests/index.html][Testing Org]].
 
 : M-x load-file RET  testing/lisp/test-ob-lilypond.el
-: M-x ert t 
+: M-x ert t
 
 * Issues
 Any issues should be reported to the [[https://orgmode.org][Org-mode Mailing-list]]
-

+ 13 - 14
org-contrib/babel/languages/ob-doc-screen.org

@@ -1,7 +1,7 @@
 #+OPTIONS:    H:3 num:nil toc:2 \n:nil ::t |:t ^:{} -:t f:t *:t tex:t d:(HIDE) tags:not-in-toc
 #+STARTUP:    align fold nodlcheck hidestars oddeven lognotestate hideblocks
 #+SEQ_TODO:   TODO(t) INPROGRESS(i) WAITING(w@) | DONE(d) CANCELED(c@)
-#+TAGS:       Write(w) Update(u) Fix(f) Check(c) 
+#+TAGS:       Write(w) Update(u) Fix(f) Check(c)
 #+TITLE:      org-babel-screen
 #+AUTHOR:     Benjamin Andresen
 #+EMAIL:      b.andresen@gmail.com
@@ -13,7 +13,7 @@
     <p>Org-babel support for interactive terminals</p>
   </div>
 #+end_export
-  
+
 * Introduction
   :PROPERTIES:
   :CUSTOM_ID: introduction
@@ -21,7 +21,7 @@
   org-babel-screen is an extension to [[file:../index.org][Org-babel]] and was inspired by
   [[http://angg.twu.net/][Eduardo Ochs]]'s [[http://angg.twu.net/eev-article.html][eev]].
 
-  org-babel-screen provides the ability to write interactive [[http://en.wikipedia.org/wiki/Make_(software)][Makefiles]]
+  org-babel-screen provides the ability to write interactive [[https://en.wikipedia.org/wiki/Make_(software)][Makefiles]]
   that can be called from inside [[http://www.gnu.org/software/emacs/][Emacs]]. Now before you get your hopes
   up: The whole point of Makefiles is that they should run automatic.
   org-babel-screen doesn't do that! I guess the only thing they have
@@ -52,7 +52,7 @@
   The default headers arguments are a bit more interesting. If you
   don't have [[http://invisible-island.net/xterm/][XTerm]] installed or you don't wish to use it, you need to
   edit the value of /org-babel-default-header-args:screen/.
-  
+
   This is the default:
   #+begin_src emacs-lisp
     (defvar org-babel-default-header-args:screen
@@ -83,7 +83,7 @@
     to do globbing with it.
 
     This example is very verbose, but here it goes:
-    
+
 :    #+begin_src screen :cmd zsh :session create-gif
 :      TMPDIR=/tmp/gif
 :      VIDEOFILE=~/TMP/DubistTerrorist_de_divx_HD.avi
@@ -117,35 +117,35 @@
 :   #+begin_src screen :session create-gif
 :     START=1:00
 :     SECS=10
-:     
+:
 :     mplayer -ao null -vo png $VIDEOFILE -ss $START -endpos $SECS
 :   #+end_src
 
 ** Delete the frames you don't want
    This is the second interactive part.
-   
+
    You delete the frames by pressing 'd' in qiv.
 :   #+begin_src screen :session create-gif
-:     qiv . 
+:     qiv .
 :   #+end_src
 
 ** Resize pictures
    256 x the corresponding aspect ratio is a good size.
 :   #+begin_src screen :session create-gif
 :     SCALE=25%
-:     
+:
 :     mkdir Small/
 :     for img (*.png) { convert -scale $SCALE $img Small/$img }
 :     file Small/*.png([1])
 :   #+end_src
-   
+
 ** Inspect down-scaled size
    If the size isn't alright, redo the previous step with a different SCALE.
-   
+
 :   #+begin_src screen :session create-gif
 :     qiv Small/*.png
 :   #+end_src
-   
+
 ** Generate gif file
    The settings here are for an endless looping gif. If the gif plays
    to fast or too slow, you can just change the command line options
@@ -160,7 +160,7 @@
 :   #+begin_src screen :session create-gif
 :     opera animation.gif
 :   #+end_src
-   
+
 * Example 2: Semi-parallel communication via netcat
   :PROPERTIES:
   :CUSTOM_ID: Example2
@@ -226,4 +226,3 @@ org-screen-babel to /tmp/testfile and reading it back via Emacs. If
 the validation fails, the setup is deemed broken.
 
 [fn:2] The example is taken from Eev as well: [[http://angg.twu.net/eev-current/anim/channels.anim.html][channels.anim]]
-

+ 6 - 6
org-contrib/babel/languages/ob-doc-sql.org

@@ -15,7 +15,7 @@
 #+begin_export html
   <div id="subtitle" style="float: center; text-align: center;">
   <p>
-  Org Mode support for <a href="http://en.wikipedia.org/wiki/SQL">SQL</a>
+  Org Mode support for <a href="https://en.wikipedia.org/wiki/SQL">SQL</a>
   </p>
   </div>
 #+end_export
@@ -93,7 +93,7 @@ There are several SQL-specific header arguments:
   - :dbuser :: the user name;
   - :dbpassword :: the user's password;
   - :database :: the database name;
- 
+
 ** Sessions
 There is currently no support for sessions.
 
@@ -120,7 +120,7 @@ source code block.
     (save-excursion
       (replace-regexp-in-string "\"\"" ""
        (mapconcat
-        (lambda (x) 
+        (lambda (x)
           (org-babel-goto-named-src-block x)
           (format "%S" (cadr  (org-babel-get-src-block-info  t))))
         (split-string blk "," t)
@@ -135,7 +135,7 @@ source code block.
     (save-excursion
       (replace-regexp-in-string "\"\"" ""
        (mapconcat
-        (lambda (x) 
+        (lambda (x)
           (org-babel-goto-named-src-block x)
           (format "%S" (cadr  (org-babel-get-src-block-info  t))))
         (split-string blk "," t)
@@ -173,7 +173,7 @@ reference to =quote-blkes= and the SQL source code block name
 #+begin_src R :colnames yes :noweb yes
   library(RMySQL)
   con <- dbConnect(MySQL(), user="user", password="pwd", dbname="dbname", host="host")
-  q <- 
+  q <-
   <<quote-blks("my-query")>>
   c <- dbGetQuery(con, q)
   dbDisconnect(con)
@@ -188,7 +188,7 @@ expands to this:
 #+begin_src R :colnames yes :noweb yes
   library(RMySQL)
   con <- dbConnect(MySQL(), user="user", password="pwd", dbname="dbname", host="host")
-  q <- 
+  q <-
   <<quote-blks("my-query")>>
   c <- dbGetQuery(con, q)
   dbDisconnect(con)

+ 1 - 1
org-contrib/index.org

@@ -26,7 +26,7 @@ hopefully have some documentation.
      code and comments.  This file (see [[repofile:contrib/scripts/org-docco.org][contrib/scripts/org-docco.org]])
      generates the same type of output from Org-mode documents with code
      embedded in code blocks.  For example org-docco output see
-     http://eschulte.github.com/org-docco/org-docco.html.
+     [[http://eschulte.github.io/org-docco/org-docco.html]].
 
 - /org-annotate-file.el/ -- annotate a file with org syntax ::
   The annotation is in a separate file, with links back to the

+ 2 - 3
org-contrib/org-drill.org

@@ -7,7 +7,7 @@
 * General
 
 
-Org-Drill is an extension for [[https://orgmode.org/][Org mode]]. Org-Drill uses a [[http://en.wikipedia.org/wiki/Spaced_repetition][spaced repetition]]
+Org-Drill is an extension for [[https://orgmode.org/][Org mode]]. Org-Drill uses a [[https://en.wikipedia.org/wiki/Spaced_repetition][spaced repetition]]
 algorithm to conduct interactive "drill sessions", using org files as sources
 of facts to be memorised. Each topic is treated as a "flash card". The material
 to be remembered is presented to the student in random order. The student rates
@@ -850,7 +850,7 @@ browser to:
   contain a timestamp, and a hyperlink back to the webpage where you created
   it.
 
-For example, suppose you are reading the Wikipedia entry on tuberculosis [[http://en.wikipedia.org/wiki/Tuberculosis][here]].
+For example, suppose you are reading the Wikipedia entry on tuberculosis [[https://en.wikipedia.org/wiki/Tuberculosis][here]].
 
 You read the following:
 
@@ -916,4 +916,3 @@ or give it different tags or properties, for example.
 * Author
 
 Org-Drill is written by Paul Sexton.
-

+ 3 - 3
org-contrib/orgtbl-ascii-plot.org

@@ -158,7 +158,7 @@ https://github.com/tbanel/orgtblasciiplot/blob/master/orgtbl-ascii-plot.el
 Here are two examples of different styles.
 
 Unicode block characters are used to give a smooth effect.
-See http://en.wikipedia.org/wiki/Block_Elements.
+See https://en.wikipedia.org/wiki/Block_Elements.
 Use one of those drawing functions:
 - =orgtbl-ascii-draw=   (the default ascii)
 - =orgtbl-uc-draw-grid= (unicode with a grid effect)
@@ -208,7 +208,7 @@ or use ascii plots only for quick and throwable visualization.
 : | # | 31 | -0.78861628 | W:           | ▉▏           | █▎           |
 : #+TBLFM: $3=sin($x/3);R::$5='(orgtbl-uc-draw-grid $3 -0.99895492 0.99540796 12)::$6='(orgtbl-uc-draw-cont $3 -0.99895492 0.99540796 12)::$4='(orgtbl-ascii-draw $3 -0.99895492 0.99540796 12)
 
-* Related work 
+* Related work
 
 Below is a unicode ASCII art solution with Zach Holman's shell script
 package Spark: https://github.com/holman/spark
@@ -223,7 +223,7 @@ package Spark: https://github.com/holman/spark
 : #+TBLFM: $10 = '(org-trim (shell-command-to-string "spark $2..$9")); L
 
 An ongoing discussion [2015-01-08] is taking place on the Org mailing list about
-/sparlines/ (http://en.wikipedia.org/wiki/Sparkline) by Willem Rein
+/sparlines/ (https://en.wikipedia.org/wiki/Sparkline) by Willem Rein
 Oudshoorn and Michael Brand which could end in yet another way of
 plotting Org tables.
 

+ 4 - 4
org-faq.org

@@ -347,7 +347,7 @@ issue with mixed installations.
 
 #+index: Bleeding Edge
 
-   Org-mode is developed in [[http://en.wikipedia.org/wiki/Git_(software)][Git]]. You can keep up-to-date with Org-mode
+   Org-mode is developed in [[https://en.wikipedia.org/wiki/Git_(software)][Git]]. You can keep up-to-date with Org-mode
    developement by cloning the Org-mode repository and refreshing your
    copy with latest changes whenever you wish. You only need to use
    two Git commands (clone and pull.) Here are the steps in brief
@@ -4079,7 +4079,7 @@ tangling the LaTeX preamble and postamble, before
 #+index: XeLaTeX
 #+index: pdfLaTeX
 
-[[http://en.wikipedia.org/wiki/XeTeX][XeLaTeX]] is an alternative to pdfLaTeX for typesetting LaTeX
+[[https://en.wikipedia.org/wiki/XeTeX][XeLaTeX]] is an alternative to pdfLaTeX for typesetting LaTeX
 documents.  XeTeX can use any fonts installed in the operating system
 without configuring TeX font metrics, and can make direct use of advanced
 typographic features of OpenType and other font formats.  By default,
@@ -4308,7 +4308,7 @@ See [[http://permalink.gmane.org/gmane.emacs.orgmode/31168][this thread]] for fu
 
 #+index: Zip
 
-You can either use [[http://en.wikipedia.org/wiki/Info-ZIP][Info-ZIP]] or zip package from Cygwin. Please customize
+You can either use [[https://en.wikipedia.org/wiki/Info-ZIP][Info-ZIP]] or zip package from Cygwin. Please customize
 =exec-path= to include the installation directory.
 
 ** I cannot open an exported =*.odt= file in LibreOffice because it is corrupt.  What do I do?
@@ -4461,7 +4461,7 @@ synchronization of =.org= files with a computer-based installation of
 Org-mode:
 
 - via [[http://www.dropbox.com/][Dropbox.com]] (easier to set up, free accounts available)
-- via a [[http://en.wikipedia.org/wiki/WebDAV][WebDAV]] server of your choice (potentially more data privacy)
+- via a [[https://en.wikipedia.org/wiki/WebDAV][WebDAV]] server of your choice (potentially more data privacy)
 
 ** How does synchronization via WebDAV work?
    :PROPERTIES:

+ 38 - 38
org-glossary.org

@@ -40,7 +40,7 @@ definitions by [[file:worg-about.org][editing Worg]].
 * Agenda
   :PROPERTIES:
   :CUSTOM_ID: agenda
-  :END: 
+  :END:
 
 #+index: Agenda!Definition
 
@@ -67,7 +67,7 @@ Here are brief explanations of the options:
    keywords]] in your agenda files.
 
  - m (Match) :: Allows you to search your agenda files for headlines
-   with particular metadata (tags, properties, or TOD0s). 
+   with particular metadata (tags, properties, or TOD0s).
 
      + The simplest way to query your files is to enter the name of a
        tag, e.g., "@computer".
@@ -121,7 +121,7 @@ fashion.
 
 There are many more possibilities of configuring the agenda with
 [[https://orgmode.org/worg/org-tutorials/org-custom-agenda-commands.php][custom agenda commands]].
-    
+
 * Agenda files
   :PROPERTIES:
   :CUSTOM_ID: agenda-files
@@ -141,7 +141,7 @@ There are different ways to designate these files:
 
   1. Add a file manually with =C-c [= (=M-x
      org-agenda-file-to-front=).
-     
+
      - Remove with =C-c ]= (=M-x org-remove-file=).
 
   2. Type =M-x customize-variable [RET] org-agenda-files= and enter
@@ -266,7 +266,7 @@ Here are a few ideas:
 #+index: Attachment!Definition
 
 ** Definition
-Attachments allow the addition of arbitrary reference material (e.g. binary files, images, audio, etc.) 
+Attachments allow the addition of arbitrary reference material (e.g. binary files, images, audio, etc.)
 to a node in an org file.
 
 ** Details
@@ -302,7 +302,7 @@ daily/weekly agenda view.
 : Day-agenda (W38):
 : Wednesday  16 September 2009
 :   badclient:  Scheduled:  TODO Call angry client to calm him down
-:   appts:      Dinner at Julio's 
+:   appts:      Dinner at Julio's
 
 By default an item's category is the name of the file (minus the
 extension) to which it belongs.
@@ -329,7 +329,7 @@ agenda.
 
 The main purpose of a category is to increase visibility in the
 daily/weekly agenda --- i.e., to allow you to see which "group" an
-item belongs to. 
+item belongs to.
 
 Apart from visibility and compartmentalization, categories do not add
 much additional functionality to an item. It is certainly *not*
@@ -392,7 +392,7 @@ timestamp:
 ** Uses
 
 The obvious use of a deadline is to reminder yourself of tasks that
-need to be completed by a certain date. 
+need to be completed by a certain date.
 
 Deadlines can also be useful as an "advanced notice" system --- e.g.,
 reminding yourself to prepare for an event or project.
@@ -408,7 +408,7 @@ entry.
 #+index: Docstring!Definition
 
 ** Definition
-A [[http://en.wikipedia.org/wiki/Docstring][docstring]] is the documentation written as part of a emacs lisp
+A [[https://en.wikipedia.org/wiki/Docstring][docstring]] is the documentation written as part of a emacs lisp
 variable or a function. It is part of Emacs' wonderful interactive
 help system.
 
@@ -432,18 +432,18 @@ C-x-C-r=). This will provide the following very helpful information:
 
 : org-clock-report is an interactive compiled Lisp function in
 : `org-clock.el'.
-: 
+:
 : It is bound to C-c C-x C-r, <menu-bar> <Org> <Logging work> <Create
 : clock table>.
-: 
+:
 : (org-clock-report &optional arg)
-: 
+:
 : Create a table containing a report about clocked time.
 : If the cursor is inside an existing clocktable block, then the table
 : will be updated.  If not, a new clocktable will be inserted.
 : When called with a prefix argument, move to the first clock table in the
 : buffer and update it.
-: 
+:
 : [back]
 
 If you happened to know the name of the function, you could also
@@ -485,7 +485,7 @@ A drawer looks like this:
 #+end_src
 
 When you cycle the visibility of your outline, the contents of the
-drawer will remain hidden. 
+drawer will remain hidden.
 
 #+begin_src org
   ,* Daily sleep log
@@ -540,20 +540,20 @@ Here is a sample entry with a lot of data:
      :CATEGORY: documentation
      :CUSTOM_ID: an-extra-special-headline
      :END:
-  
+
    And here is the text of an entry. You can put an unlimited amount of
    text in an entry!
-  
+
    You can also add lists:
-  
+
     - First item
-  
+
     - Second item
-  
+
     - Third item
-  
+
    And tables:
-  
+
    | Meal      | Food            | Calories |
    |-----------+-----------------+----------|
    | Breakfast | Eggs            |      500 |
@@ -566,7 +566,7 @@ Here is a sample entry with a lot of data:
 * Headline
   :PROPERTIES:
   :CUSTOM_ID: headline
-  :END: 
+  :END:
 
 #+index: Headline!Definition
 
@@ -574,7 +574,7 @@ Here is a sample entry with a lot of data:
 A headline is the name for an outline heading in an org file.
 
 ** Details
-Headlines begin with one or more asterisks. 
+Headlines begin with one or more asterisks.
 
 #+begin_src org
   ,* A headline
@@ -661,11 +661,11 @@ top level headline:
 #+begin_src org
   ,* Summer reading list                                               :reading:
     DEADLINE: <1965-06-06 Sun>
-  
+
   ,** /To Kill a Mockingbird/
-  
+
   ,** /Catch 22/
-  
+
   ,** /Herzog/
 #+end_src
 
@@ -676,7 +676,7 @@ Some properties, such as [[#category][category]], are also inherited by default.
 
 The most common use of tag inheritance is in agenda views and agenda
 filtering. For instance, if you searched for the tag "reading" in your
-agenda files, all of the headings in the [[tag-inheritance-example][example above]] would appear. 
+agenda files, all of the headings in the [[tag-inheritance-example][example above]] would appear.
 
 As a result it is easy to add a tag and/or category to a whole subtree
 of items simply by adding a single tag to the parent headline.
@@ -733,7 +733,7 @@ is to type =C-c C-x p= or =M-x org-set-property=.
 For new org users, properties can seem a bit puzzling. What exactly
 are they for? Here are some of their uses:
 
-   1. To specify settings for the local org-mode [[#tree][tree]]. 
+   1. To specify settings for the local org-mode [[#tree][tree]].
 
       - For instance, though you may not normally want to be prompted
         for a note when you mark an item as DONE, you might want to
@@ -815,7 +815,7 @@ See [[https://orgmode.org/manual/Setting-tags.html][the manual]] for more detail
 
 ** Uses
 
-One common use of tags is as [[http://en.wikipedia.org/wiki/Getting_Things_Done#GTD_methodology][GTD contexts]]. You might, for instance,
+One common use of tags is as [[https://en.wikipedia.org/wiki/Getting_Things_Done#GTD_methodology][GTD contexts]]. You might, for instance,
 define a list of tags in org-tags-alist that correspond to the various
 contexts in a "next action" can be completed: @computer, @home,
 @errands, @work, and so on. Then you can quickly filter for these tags
@@ -833,11 +833,11 @@ Here's what this would look like:
 
 #+begin_src org
   ,* Tasks around the house                                        :houserepair:
-  
+
   ,** TODO Fix sink
-  
+
   ,** TODO Mow lawn
-  
+
   ,** TODO Tear up carpet
 #+end_src
 
@@ -917,7 +917,7 @@ larger trees.
 ** Definition
 
 A TODO keyword is a small keyword at the beginning of a headline that
-defines the TODO state of the entry. 
+defines the TODO state of the entry.
 
 ** Details
 
@@ -925,8 +925,8 @@ The default TODO keywords in org-mode are TODO and DONE. They are
 automatically given nice colors to make them stand out.
 
 #+begin_src org
-  ,* DONE Check cupboard to see if I'm out of bread 
-    CLOSED: [2009-09-16 Wed 13:14] 
+  ,* DONE Check cupboard to see if I'm out of bread
+    CLOSED: [2009-09-16 Wed 13:14]
   ,* TODO Buy bread at the store
 #+end_src
 
@@ -974,7 +974,7 @@ record of when each event in the sequence happened.
 
 #+index: Agenda filtering!Definition
 
-** CLOCK 
+** CLOCK
 
 #+index: Clock!Definition
 
@@ -1002,7 +1002,7 @@ record of when each event in the sequence happened.
 
 #+index: Note!Definition
 
-** List 
+** List
 
 #+index: List !Definition
 
@@ -1014,7 +1014,7 @@ record of when each event in the sequence happened.
 
 #+index: Logging!Definition
 
-** SCHEDULED 
+** SCHEDULED
 
 #+index: SCHEDULED!Definition
 

+ 1 - 1
org-gtd-etc.org

@@ -20,7 +20,7 @@
 
 Org-mode is flexible enough to implement many different ways of
 organizing your projects.  A frequently discusses scheme is [[http://www.davidco.com/][David
-Allen's]] strategy for [[http://en.wikipedia.org/wiki/GTD][Getting Things Done]].  But it is clearly not the
+Allen's]] strategy for [[https://en.wikipedia.org/wiki/GTD][Getting Things Done]].  But it is clearly not the
 only way to us Org-mode for planning.  Here are a couple of links
 related to this topic.
 

+ 2 - 2
org-hacks.org

@@ -139,7 +139,7 @@ To switch back to the compiled version just reload again with
 :CUSTOM_ID: check-old-link-escapes
 :END:
 #+index: Link!Escape
-Starting with version 7.5 Org uses [[http://en.wikipedia.org/wiki/Percent-encoding][percent escaping]] more consistently
+Starting with version 7.5 Org uses [[https://en.wikipedia.org/wiki/Percent-encoding][percent escaping]] more consistently
 and with a modified algorithm to determine which characters to escape
 and how.
 
@@ -198,7 +198,7 @@ in old Org's list of known percent escapes.
 =org-jump-to-child= in [[file:code/elisp/org-jump.el::(defun%20org-jump-to-child][org-jump.el]] (keybinding suggested there: =C-c o c=) interactively prompts for the title of a child node, i.e. sub-heading, of the current heading and jumps to the child node having that title (in case of ambiguity: the /last/ such node).
 
 In the absence of a readily accessible structural representation of the tree outline, this is ipmlemented by walking over all child nodes and collecting their titles and their positions in the file.
-  
+
 *** Go to a heading by its ID (=CUSTOM_ID= property)
     :PROPERTIES:
     :CUSTOM_ID: org-jump-to-id

+ 3 - 5
org-quotes.org

@@ -141,7 +141,7 @@ Re: Copy/Search Outline \\
 
 I post a howto over my morning coffee at 8:38am. By 11:30am, Florian
 has encapsulated it into a neat function with added goodies. Within 40
-minutes, Carsten reports 
+minutes, Carsten reports
 
 > there is a key (C-c C-x v) and a menu entry,\\
 > and documentation in manual and refcard for it.
@@ -384,7 +384,7 @@ too.  Sorry for this unnecessary rant, but I just love Org.
 * Some 24/7 lectures about Org-mode
 
 The famous 24/7 lectures are part of the ceremony for handing out the
-[[http://en.wikipedia.org/wiki/Ig_Nobel_Prize][Ig Nobel Prizes]].  All speakers have to give a 24/7 lecture on their
+[[https://en.wikipedia.org/wiki/Ig_Nobel_Prize][Ig Nobel Prizes]].  All speakers have to give a 24/7 lecture on their
 subject. This means, they have to give a /complete technical
 description/ of their work in /24 words/ (may be totally cryptic), and
 then a /7 word/ explanation that is more or less /understandable for
@@ -419,7 +419,7 @@ These was only a single entry in the "24" category:
    - Madness? This is org-mode! [[http://www.youtube.com/watch%3Fv%3DUgrsNBu51nU][*Real Spartans use emacs!*]] (/Russell
      Adams[fn:2]/)
 
-   - Plain text with frickin' lasers. [[http://en.wikipedia.org/wiki/Dr._Evil][*pinky to lips*]] (/Russell
+   - Plain text with frickin' lasers. [[https://en.wikipedia.org/wiki/Dr._Evil][*pinky to lips*]] (/Russell
      Adams[fn:2]/)
 
    - It is the text that binds us. [[http://www.urbandictionary.com/define.php%3Fterm%3Dshikaka][*Shekaka!*]] (/Russell Adams[fn:2]/)
@@ -434,5 +434,3 @@ Orgtbl-mode to get the same tables in Muse.
 
 [fn:2] The linked text is from Adam, but the link itself has been added
 by me.
-
-

+ 5 - 5
org-tests/index.org

@@ -20,12 +20,12 @@
 Org-mode has grown into a popular large and feature-rich application,
 on which development often happens at a great pace. Indeed, feature
 requests posted on the [[file:org-mailing-list.org][Org mailing list]] are frequently developed and
-published within hours of the request. 
+published within hours of the request.
 
 The down-side of such rapid development is that on some occasions, one
-of the many patches, features, or [[http://en.wikipedia.org/wiki/Code_refactoring][refactorings]] being applied to the
+of the many patches, features, or [[https://en.wikipedia.org/wiki/Code_refactoring][refactorings]] being applied to the
 code-base may unintentionally cause unexpected behavior within
-Org-mode. This is known as a [[http://en.wikipedia.org/wiki/Software_regression][software regression]]. The larger and more
+Org-mode. This is known as a [[https://en.wikipedia.org/wiki/Software_regression][software regression]]. The larger and more
 complex Org-mode becomes, the more you may expect to see such software
 regressions.
 
@@ -35,7 +35,7 @@ hours, days, or even months before an Org-mode user moves to export an
 important schedule, when "bang" - the regression has reared its ugly
 head.
 
-The solution to avoiding software regressions? [[http://en.wikipedia.org/wiki/Regression_testing][Regression Testing!]]
+The solution to avoiding software regressions? [[https://en.wikipedia.org/wiki/Regression_testing][Regression Testing!]]
 With a regression test suite the developer can run the tests prior to
 committing their change, to ensure their additions do not break the
 regression tests.
@@ -47,7 +47,7 @@ Org-mode users can help.
 * Running the current test suite
 
 So long as you are on an up-to-date release of Org-mode you may run
-the tests on your local setup. To update Org-mode check out the 
+the tests on your local setup. To update Org-mode check out the
 [[https://orgmode.org/worg/org-faq.html][org FAQ page]]. Note, the test suite will run on versions of Emacs back
 to version 22.
 

+ 3 - 4
org-translators.org

@@ -24,12 +24,12 @@ export Org-mode data and import external data into the Org-mode system.
   - From Org-mode to Freemind by Marco Vezzoli, this is available in
     the contrib directory of the distribution.
 
-  - From Org-mode to [[http://en.wikipedia.org/wiki/ICalendar][ICal]]endar applications:
+  - From Org-mode to [[https://en.wikipedia.org/wiki/ICalendar][ICal]]endar applications:
 
     - there are an export tool already implemented in org mode, is
       [[https://orgmode.org/manual/iCalendar-export.html#iCalendar-export][explained at the org manual]].
 
-    - For Google users, read [[file:org-tutorials/org-google-sync.org][this tutorial]]. 
+    - For Google users, read [[file:org-tutorials/org-google-sync.org][this tutorial]].
 
 * Org-mode Import Tools
 
@@ -67,6 +67,5 @@ export Org-mode data and import external data into the Org-mode system.
     - For Google users, see [[file:org-tutorials/org-google-sync.org::*From%20Google%20Calendar%20into%20org%20using%20.ics%20files][this]].
 
 * Bi-directional
-   
+
   - Google Calendar :: There is a method for synching. Read [[file:org-tutorials/org-google-sync.org][this tutorial]].
-  

+ 10 - 14
org-tutorials/non-beamer-presentations.org

@@ -1,15 +1,15 @@
 #+TITLE:     Writing Non-Beamer presentations in org-mode
 #+AUTHOR:    Eric Schulte
 #+DATE:      <2011-06-02 Thu>
-#+DESCRIPTION: 
-#+KEYWORDS: 
+#+DESCRIPTION:
+#+KEYWORDS:
 #+LANGUAGE:  en
 #+OPTIONS:    H:3 num:nil toc:t \n:nil ::t |:t ^:t -:t f:t *:t tex:t d:(HIDE) tags:not-in-toc
 #+INFOJS_OPT: view:nil toc:nil ltoc:t mouse:underline buttons:0 path:https://orgmode.org/org-info.js
 #+SELECT_TAGS: export
 #+EXCLUDE_TAGS: noexport
-#+LINK_UP:   
-#+LINK_HOME: 
+#+LINK_UP:
+#+LINK_HOME:
 
 * Introduction
 
@@ -113,9 +113,9 @@ Two S5 options exist for Org-mode.
     (setq org-s5-theme "i18n")        ; the i18n theme by the author of S5
   #+end_src
 
-- This entire directory is available as a [[https://github.com/eschulte/org-S5/blob/master/org-export-as-s5.el][git repository]]
+- This entire directory is available as a [[https://github.com/eschulte/org-S5/blob/master/org-export-as-s5.el][git repository]].
 
-- For two examples of org-S5 in action see [[http://eschulte.github.com/org-S5/][here]]
+- For two examples of org-S5 in action see [[http://eschulte.github.io/org-S5/][here]].
 
 * org-tree-slide
   :PROPERTIES:
@@ -123,7 +123,7 @@ Two S5 options exist for Org-mode.
   :END:
 
 org-tree-slide is an Emacs minor mode for org-mode. Once you toggle
-=M-x org-tree-slie-mode=, just type =<left>= and =<right>= to move between 
+=M-x org-tree-slie-mode=, just type =<left>= and =<right>= to move between
 slides. To show CONTENT, type =C-x s c=. When you exit this minor mode,
 the slideshow will be finished.
 
@@ -145,7 +145,7 @@ Preset profiles are defined in org-tree-slide.
 2. =M-x org-tree-slide-presentation-profile=      ; Presentation use
 3. =M-x org-tree-slide-narrowing-control-profile= ; TODO Pursuit with narrowing
 These functions set user variables for each using scenario.
-You can find more detail in [[https://github.com/takaxp/org-tree-slide/blob/master/README.org][README.org]]. 
+You can find more detail in [[https://github.com/takaxp/org-tree-slide/blob/master/README.org][README.org]].
 * orgmode-slideshow
 
 Sander Boer created orgmode-slideshow -- see his message:
@@ -154,11 +154,11 @@ I hacked together a javascript and a css that transforms the default html
 export of my org file to a slide show:
 
 - http://www.mauc.nl/presentations/test.html
-  
+
 Here's the org-file:
 
 - http://www.mauc.nl/presentations/test.org
-  
+
 Here's the rest (depends on jQuery)
 
 - http://www.mauc.nl/assets/css/orgmode-slideshow.css
@@ -198,7 +198,3 @@ Here's the rest (depends on jQuery)
    Though you can read it online, it is recommended to download the
    projects and read it in your Emacs, so that you can try exporting
    it to Reveal.js presentation while reading.
-
-
-
-  

+ 6 - 6
org-tutorials/org-jekyll.org

@@ -46,7 +46,7 @@ easily embed html content in your org pages using the =+BEGIN_HTML= tag.
 
 * Install Jekyll
 
-Installation is described at the [[http://github.com/mojombo/jekyll][Jekyll]] web site. 
+Installation is described at the [[http://github.com/mojombo/jekyll][Jekyll]] web site.
 
 * Project Directory Structure
 Jekyll expects a certain directory structure. In the example below my
@@ -74,7 +74,7 @@ to hold different non blog parts of your site.
 '|      `-- post.html
 '|   -- _posts
 '|      |-- 2009-11-26-my-first-post.html
-'|      
+'|
 '|   -- |_site
 '|   -- |_includes
 `    -- index.html
@@ -95,7 +95,7 @@ default org produces complete web pages. However, as I am using Jekyll
 I am only really interested in the section of the page between the
 =<body>= tags, as Jekyll produces the rest. Most things in org are
 configurable and it's possible to tell org to export only the bits of
-the page between the =<body>= tags. Here is the relevant section of my 
+the page between the =<body>= tags. Here is the relevant section of my
 =.emacs= file:
 
 #+BEGIN_SRC emacs-lisp
@@ -111,7 +111,7 @@ the page between the =<body>= tags. Here is the relevant section of my
           :publishing-directory "~/devel/ianbarton/jekyll/"
           :recursive t
           :publishing-function org-publish-org-to-html
-          :headline-levels 4 
+          :headline-levels 4
           :html-extension "html"
           :body-only t ;; Only export section between <body> </body>
     )
@@ -386,7 +386,7 @@ The on-line documentation for [[file:../org-contrib/babel/index.org][Org-babel]]
 [[http://github.com][github]] which uses jekyll.  The following code is used to publish one
 blog post for every subheading of the first to top-level headings of a
 org file which tracks Org-babel development.  The results can be seen
-[[http://eschulte.github.com/babel-dev/][here]], and the code used to create this site is available [[http://github.com/eschulte/babel-dev/][here]].
+[[http://eschulte.github.io/babel-dev/][here]], and the code used to create this site is available [[http://github.com/eschulte/babel-dev/][here]].
 
 #+begin_src emacs-lisp
   (save-excursion
@@ -435,7 +435,7 @@ org file which tracks Org-babel development.  The results can be seen
                       (insert "---\n\n"))
                     (insert html))
                   (get-buffer org-buffer)))))))
-       '(1 2))))  
+       '(1 2))))
 #+end_src
 
 * Other Blog Solutions for org

+ 93 - 95
org-tutorials/org-latex-export.org

@@ -3,16 +3,16 @@
 #+AUTHOR:    Tom Dye
 #+EMAIL:     tsd@tsdye2.com
 #+DATE:      2010-04-24 Sat
-#+DESCRIPTION: 
-#+KEYWORDS: 
+#+DESCRIPTION:
+#+KEYWORDS:
 #+LANGUAGE:  en
 #+OPTIONS:    H:3 num:t toc:t \n:nil ::t |:t ^:t -:t f:t *:t tex:t d:(HIDE) tags:not-in-toc
 #+OPTIONS:   <:t d:nil todo:t pri:nil tags:not-in-toc
 #+INFOJS_OPT: view:nil toc:nil ltoc:t mouse:underline buttons:0 path:https://orgmode.org/org-info.js
 #+SELECT_TAGS: export
 #+EXCLUDE_TAGS: noexport
-#+LINK_UP:   
-#+LINK_HOME: 
+#+LINK_UP:
+#+LINK_HOME:
 
 * Start up
 Org-mode LaTeX export is easy.  Place the following code in your
@@ -25,7 +25,7 @@ Org-mode LaTeX export is easy.  Place the following code in your
   (add-to-list 'org-latex-classes
                '("article"
                  "\\documentclass{article}"
-                 ("\\section{%s}" . "\\section*{%s}")))  
+                 ("\\section{%s}" . "\\section*{%s}")))
 #+end_src
 
 This tells the Org-mode LaTeX exporter to use the standard LaTeX
@@ -123,12 +123,12 @@ Here is a standard setup for export to a LaTeX book class:
 Then, in the Org file with a book-full of notes, add this line:
 
 #+begin_src org
-  #+LaTeX_CLASS: book 
+  #+LaTeX_CLASS: book
 #+end_src
 
 <<koma-script>>
 A useful set of alternatives is the [[http://www.komascript.de/][KOMA script]] classes.  These have a
-somewhat more modern design than the standard LaTeX classes.  
+somewhat more modern design than the standard LaTeX classes.
 
 For example, the KOMA script article class can be configured in =.emacs=:
 
@@ -161,7 +161,7 @@ You can pass options to the LaTeX =\documentclass= macro by putting a
 line like this in your Org-mode file:
 
 #+begin_src org :exports code
-  #+LaTeX_CLASS_OPTIONS: [a4paper,twoside,twocolumn] 
+  #+LaTeX_CLASS_OPTIONS: [a4paper,twoside,twocolumn]
 #+end_src
 
 A useful option with the [[koma-script][KOMA script]] classes typesets table captions
@@ -170,7 +170,7 @@ exported by Org-mode above the table.  The following option to the
 [[koma-script][KOMA script]] classes accomplishes this.
 
 #+begin_src org
-  #+LaTeX_CLASS_OPTIONS: [captions=tableheading] 
+  #+LaTeX_CLASS_OPTIONS: [captions=tableheading]
 #+end_src
 
 * Using Custom Classes
@@ -178,12 +178,12 @@ If the user has custom LaTeX document classes that conflict with the
 default packages or that only require a few of the default packages to
 support all features of the LaTeX exporter, then this can be handled
 in =.emacs= using [DEFAULT-PACKAGES], [NO-DEFAULT-PACKAGES],
-[PACKAGES], [NO-PACKAGES], [EXTRA], [NO-EXTRA].    
+[PACKAGES], [NO-PACKAGES], [EXTRA], [NO-EXTRA].
 
 Here is a simple example that uses an experimental [[https://orgmode.org/worg/org-contrib/babel/examples/article-class.html][LaTeX class]][fn:3] that
 supports the Org-mode requirements and leaves open the possibility of
 adding file specific packages:
-  
+
 #+begin_src emacs-lisp
   (add-to-list 'org-latex-classes
         '("org-article"
@@ -224,7 +224,7 @@ perhaps the most flexible way to set up LaTeX export.  Since the
 example only calls it if it would add a LaTeX class that isn't
 already on the =org-latex-classes= list:
 
-#+begin_example 
+#+begin_example
   #+name: setup
   #+begin_src emacs-lisp :results silent :exports none
  (unless (find "per-file-class" org-latex-classes :key 'car
@@ -281,7 +281,7 @@ might look like this in =.emacs=:
   (add-to-list 'org-latex-classes
                '("per-file-class"
                  "\\documentclass{scrartcl}
-                   \\usepackage{graphicx} 
+                   \\usepackage{graphicx}
               [NO-DEFAULT-PACKAGES]
               [NO-PACKAGES]"
                  ("\\section{%s}" . "\\section*{%s}")
@@ -339,15 +339,15 @@ If you use a different TeX typesetting engine or would like to
 customize how Org-mode produces the pdf file, then you will want to
 modify the variable =org-latex-to-pdf-process=.  This is a list of
 strings, each of which contains a call to one of the TeX typesetting
-engines or to an auxiliary program, such as BibTeX, makeindex, etc.  
+engines or to an auxiliary program, such as BibTeX, makeindex, etc.
 
 For example, the shell script =texi2dvi= will run =pdflatex= as many
 times as needed to build a pdf file successfully.  The following code
 in =.emacs= will instruct Org-mode to use =texi2dvi= when making a pdf
 file.  Note that you should check that =texi2dvi= is installed on your
 system and that it works correctly before adding this code to your
-=.emacs=. 
- 
+=.emacs=.
+
 #+name: texi2dvi
 #+begin_src emacs-lisp :exports code
 (setq org-latex-to-pdf-process '("texi2dvi --pdf --clean --verbose --batch %f"))
@@ -355,9 +355,9 @@ system and that it works correctly before adding this code to your
 
 Note that =makeindex= and =bibtex= require a bit more effort to work
 in this way because of path name issues.  Nick Dokos suggested
-this fix, which specifies a path to one or more BibTeX =.bib= files: 
+this fix, which specifies a path to one or more BibTeX =.bib= files:
 
-#+begin_example 
+#+begin_example
   ,#+begin_src sh :exports none
     BIBINPUTS=/path/to/bib/:$BIBINPUTS
     export BIBINPUTS
@@ -382,7 +382,7 @@ material that shouldn't appear in the export; tags distinguish the
 export parts from the non-export parts.  This is the single
 export case.  It is also possible to use tags to specify multiple
 export targets in a single Org-mode buffer.  In the multiple export
-case, tags are resolved by a [[https://orgmode.org/org.html#Publishing][publishing management system]].  
+case, tags are resolved by a [[https://orgmode.org/org.html#Publishing][publishing management system]].
 
 ** The Single Export Case
 The tags used for the single export case are held in
@@ -417,7 +417,7 @@ entire buffer.
 Once the scope of the tag's effect is grasped, the primary rule of using
 select and exclude tags is obvious: only one type of tag may be used
 for the trees of a buffer.  If both types of tags are used for trees,
-how can Org-mode decide what to do with the unmarked trees?  
+how can Org-mode decide what to do with the unmarked trees?
 
 A corollary of this rule is that the other type of tag can only be
 used in a subtree of the tagged tree in order to reverse the effect of
@@ -529,7 +529,7 @@ package [[file:../org-contrib/org-special-blocks.org][org-special-blocks]], whic
 inside the block. For example, you can wrap an abstract in
 
 : #+BEGIN_ABSTRACT
-: This is an *abstract* with ordinary =Org-mode= /markup/. 
+: This is an *abstract* with ordinary =Org-mode= /markup/.
 : #+END_ABSTRACT
 
 For more complex cases, where you need to pass parameters or process
@@ -583,21 +583,21 @@ abbreviated versions, typically less than a line long, in the List of
 Figures.  In addition, many styles require that figure captions end
 with a period; the caption passed to the List of Figures should not
 end in a period.
- 
+
 The Org-mode =#+CAPTION:= macro handles an optional argument.
 
 This construct:
 
 : #+CAPTION[Short caption]: Long caption.
 
-exports: 
+exports:
 
 : \caption[Short caption]{Long caption.}
 
 * Styling the Frontmatter
 The Org-mode LaTeX exporter requires configuration to gain full access
 to the LaTeX frontmatter formatting capacity.
- 
+
 ** Abstract, contents, and lists of figures and tables
 In the default configuration, the Org-mode LaTeX exporter includes a
 function that sandwiches the LaTeX =\tableofcontents= command between
@@ -621,7 +621,7 @@ possible for the user to alter this behavior relatively easily.
 
 #+name: format-no-toc
 #+begin_src emacs-lisp :exports code
-(defun org-export-latex-no-toc (depth)  
+(defun org-export-latex-no-toc (depth)
     (when depth
       (format "%% Org-mode is exporting headings to %s levels.\n"
               depth)))
@@ -648,10 +648,10 @@ do this was posted to the Org-mode list by Nick Dokos:
 
 #+begin_example
 #+LATEX_HEADER: \input{mytitle}
- 
+
  * Foo
  foo
- 
+
  * Bar
  bar
 #+end_example
@@ -673,7 +673,7 @@ FOO
   mode, then one approach is to use =#+begin_latex ... #+end_latex=
   and write the pseudo-code directly in LaTeX.  This depends on the
   LaTeX [[http://www.ctan.org/tex-archive/macros/latex/contrib/listings/][listings package]], which is one of the default packages used by
-  Org-mode. 
+  Org-mode.
 
   Dan Davison provided this example on the Org-mode list:
 
@@ -699,7 +699,7 @@ fontify source code.  This package appears to be actively maintained.
 Both packages are included in the TeXLive and MacTeX LaTeX
 distributions.  If your distribution lacks one or the other, then
 you'll need to check the documentation for instructions how to install
-them. 
+them.
 
 The two packages are structured somewhat differently, but it is
 possible to configure Org-mode so that these differences are mostly
@@ -721,7 +721,7 @@ In this example, the minted package is specified in the
 =#+LaTeX_HEADER:=.  This is followed by a command to use the minted
 style =emacs=, which colors source code in a way familiar to emacs
 users.  The final =#+LaTeX_HEADER:= line uses the =newminted= macro to
-set the font size for code blocks of =common-lisp=. 
+set the font size for code blocks of =common-lisp=.
 
 The source code block =setup-minted= includes emacs-lisp code that
 might typically appear in .emacs, but can be useful in a source code
@@ -751,7 +751,7 @@ A Python source code block at the end illustrates how the default
 emacs-style code differs from the specially formatted emacs-lisp
 source code.
 
-#+begin_example 
+#+begin_example
 , #+LATEX_CLASS: article
 , #+LaTeX_HEADER: \usepackage{minted}
 , #+LaTeX_HEADER: \usemintedstyle{emacs}
@@ -779,7 +779,7 @@ source code.
    x = str(y)
 , #+end_src
 #+end_example
- 
+
 When this example is exported (=C-c C-e d=) the resulting pdf file
 contains two source code blocks nicely typeset and colored in a way
 common to many emacs setups.
@@ -815,7 +815,7 @@ the options specified for =emacs-lisp= source code blocks.  Finally,
 the =latex= link type is used to call the new =python= command to
 typeset an inline code snippet.
 
-#+begin_example 
+#+begin_example
 , #+LATEX_CLASS: article
 , #+LaTeX_HEADER: \usepackage{listings}
 , #+LaTeX_HEADER: \lstnewenvironment{common-lispcode}
@@ -868,7 +868,7 @@ caption and a label:
 
 This has the great advantage of exporting cleanly to HTML, ASCII, and
 other backends, but the amount of control over the results is somewhat
-limited. 
+limited.
 
 At the other extreme, you can create an arbitrarily complex LaTeX
 table and wrap it in =#+BEGIN_LATEX:= ... =#+END_LATEX:=.  This will
@@ -910,7 +910,7 @@ Note that the LaTeX environments responsible for handling the
 information specified by =#+CAPTION:= and =#+LABEL:= are =table=,
 =table*=, and =longtable=.  If =tabular=, =tabularx=, and =tabulary=
 are used by themselves, then they won't support captions and
-cross-references. 
+cross-references.
 
 ** Table Rules
 The tables in many high-quality publications use rules of different
@@ -948,7 +948,7 @@ Finally, create a LaTeX source block something like this:
 :   \footnotesize
 :   \caption{A table to test booktabs}
 :   \label{tab:test-table}
-:   <<booktabs(table=test-table,align="lrX",env="tabularx",width="\\textwidth")>>  
+:   <<booktabs(table=test-table,align="lrX",env="tabularx",width="\\textwidth")>>
 :   \end{table}
 :  #+end_src
 
@@ -981,7 +981,7 @@ Library of Babel.
 :     \footnotesize
 :     \caption{The table caption without Org-mode markup}
 :     \label{tab:dates}
-:     <<booktabs-notes(table=dates,notes=dates-fn,lspace=t,align="rcr",env="tabular")>>  
+:     <<booktabs-notes(table=dates,notes=dates-fn,lspace=t,align="rcr",env="tabular")>>
 :   \end{table}
 : #+end_src
 
@@ -990,7 +990,7 @@ except it accepts a second Org-mode table that contains the table
 notes.  Remember that both of these Org-mode tables are sent to
 =orgtbl-to-generic= so Org-mode markup within them won't give the
 results you might expect.  Instead, the table entries use LaTeX
-markup. 
+markup.
 
 : #+tblname: dates
 : | One\fn{1} | Two\fn{2} | Three\fn{3} |
@@ -1064,7 +1064,7 @@ compact =paralist= equivalents:
 
 : #+LaTeX_HEADER: \let\itemize\compactitem
 : #+LaTeX_HEADER: \let\description\compactdesc
-: #+LaTeX_HEADER: \let\enumerate\compactenum  
+: #+LaTeX_HEADER: \let\enumerate\compactenum
 
 With these settings, all the lists in the Org-mode document will be
 exported in compact form.
@@ -1127,40 +1127,40 @@ to match fonts in each set.
 
 Bera is the LaTeX version of the Bitstream's Vera family of fonts.
 The family includes serif, sans-serif, and monospace fonts designed to
-work well with one another. 
+work well with one another.
 
-: #+LaTeX_HEADER: \usepackage[T1]{fontenc} 
+: #+LaTeX_HEADER: \usepackage[T1]{fontenc}
 : #+LaTeX_HEADER: \usepackage[scaled]{beraserif}
-: #+LaTeX_HEADER: \usepackage[scaled]{berasans} 
+: #+LaTeX_HEADER: \usepackage[scaled]{berasans}
 : #+LaTeX_HEADER: \usepackage[scaled]{beramono}
 
 ** Charter
 <<charter-font>>
 
-[[http://en.wikipedia.org/wiki/Bitstream_Charter][Charter]] was designed to reproduce well on low-resolution 300 dpi
+[[https://en.wikipedia.org/wiki/Bitstream_Charter][Charter]] was designed to reproduce well on low-resolution 300 dpi
 printers.  It is paired here with Helvetica and Courier, like [[times-font][Times]],
 for which it is an alternative.  Helvetica is set a bit smaller to
 match the shape of the Charter font.  These fonts conflict with the
 =amssymb== package.
 
-: #+LaTeX_HEADER: \usepackage[T1]{fontenc} 
+: #+LaTeX_HEADER: \usepackage[T1]{fontenc}
 : #+LaTeX_HEADER: \usepackage[bitstream-charter]{mathdesign}
-: #+LaTeX_HEADER: \usepackage[scaled=.9]{helvet} 
+: #+LaTeX_HEADER: \usepackage[scaled=.9]{helvet}
 : #+LaTeX_HEADER: \usepackage{courier} % tt
 
 ** Garamond
 <<garamond-font>>
 
-[[http://en.wikipedia.org/wiki/Garamond][Garamond]] refers to a group of old-style serif typefaces and is named
+[[https://en.wikipedia.org/wiki/Garamond][Garamond]] refers to a group of old-style serif typefaces and is named
 after the sixteenth-century type designer, Claude Garamond.  It is an
 elegant typeface.  Garamond requires a bit more leading than normal.
 The sans-serif font is Latin Modern and the typewriter font is
 Courier.  Both were chosen to match the shape and stroke weight of
 Garamond.
 
-: #+LaTeX_HEADER: \usepackage[T1]{fontenc} 
+: #+LaTeX_HEADER: \usepackage[T1]{fontenc}
 : #+LaTeX_HEADER: \usepackage[urw-garamond]{mathdesign}
-: #+LaTeX_HEADER: \usepackage{lmodern} 
+: #+LaTeX_HEADER: \usepackage{lmodern}
 : #+LaTeX_HEADER: \usepackage{courier}
 : #+LaTeX_HEADER: \linespread{1.0609}
 
@@ -1170,7 +1170,7 @@ Garamond.
 The [[http://tug.ctan.org/pkg/kpfonts][KP font family]] is produced by Christophe Caignaert for the
 Johannes Kepler project.  The family supports math.
 
-: #+LaTeX_HEADER: \usepackage[T1]{fontenc} 
+: #+LaTeX_HEADER: \usepackage[T1]{fontenc}
 : #+LaTeX_HEADER: \usepackage{kpfonts}
 
 ** Libertine
@@ -1181,11 +1181,11 @@ replacement for Times New Roman and includes a companion sans-serif
 font.  It was used to typeset the Wikipedia logo.  The monospace
 typewriter font is Latin Modern.
 
-: #+LaTeX_HEADER: \usepackage[T1]{fontenc} 
+: #+LaTeX_HEADER: \usepackage[T1]{fontenc}
 : #+LaTeX_HEADER: \usepackage{libertine}
 : #+LaTeX_HEADER: \renewcommand*\oldstylenums[1]{{\fontfamily{fxlj}\selectfont #1}}
 : #+LaTeX_HEADER: \usepackage{lmodern}
-** Nimbus                                                     
+** Nimbus
 <<nimbus-font>>
 
 The Nimbus font set uses fonts from the [[http://www.gust.org.pl/projects/e-foundry/tex-gyre/][Tex-Gyre]] distribution, which
@@ -1203,7 +1203,7 @@ Cursor, which is a Courier replacement.
 ** Palatino
 <<palatino-font>>
 
-The beautiful, old-style serif font, [[http://en.wikipedia.org/wiki/Palatino][Palatino]], was designed by [[http://en.wikipedia.org/wiki/Herman_Zapf][Herman
+The beautiful, old-style serif font, [[https://en.wikipedia.org/wiki/Palatino][Palatino]], was designed by [[https://en.wikipedia.org/wiki/Herman_Zapf][Herman
 Zapf]].  It is somewhat heavier and easier to read than [[garamond-font][Garamond]].
 Palatino gets a bit more leading than normal.  It is paired here with
 Helvetica and Courier, as is [[times-font][Times]], for which it is an alternative.
@@ -1222,31 +1222,31 @@ font, URW Nimbus Sans, a Helvetica clone, for the sans-serif font,
 and URW Nimbus Mono, a Courier clone, for the typewriter font.  This
 is a standard set of common typefaces typically used in scientific
 publications.  All of the fonts should be included in a typical LaTeX
-distribution. 
+distribution.
 
-[[http://en.wikipedia.org/wiki/Times_Roman][Times New Roman]] was designed by [[http://en.wikipedia.org/wiki/Stanley_Morison][Stanley Morison]] for /The Times/ of
+[[https://en.wikipedia.org/wiki/Times_Roman][Times New Roman]] was designed by [[https://en.wikipedia.org/wiki/Stanley_Morison][Stanley Morison]] for /The Times/ of
 London during a redesign of the newspaper prompted, in part, by
-Morison's criticism of its typography in 1929.  [[http://en.wikipedia.org/wiki/Helvetica][Helvetica]] was
-developed in 1957 by [[http://en.wikipedia.org/wiki/Max_Miedinger][Max Miedinger]].  Helvetica looks better with Times
-if it is set slightly smaller than the serif font.  [[http://en.wikipedia.org/wiki/Courier_(typeface)][Courier]] was
+Morison's criticism of its typography in 1929.  [[https://en.wikipedia.org/wiki/Helvetica][Helvetica]] was
+developed in 1957 by [[https://en.wikipedia.org/wiki/Max_Miedinger][Max Miedinger]].  Helvetica looks better with Times
+if it is set slightly smaller than the serif font.  [[https://en.wikipedia.org/wiki/Courier_(typeface)][Courier]] was
 designed by Howard Kettler in 1955 for use in IBM typewriters.
 
 : #+LaTeX_HEADER: \usepackage[T1]{fontenc}
-: #+LaTeX_HEADER: \usepackage{mathptmx} 
-: #+LaTeX_HEADER: \usepackage[scaled=.90]{helvet} 
+: #+LaTeX_HEADER: \usepackage{mathptmx}
+: #+LaTeX_HEADER: \usepackage[scaled=.90]{helvet}
 : #+LaTeX_HEADER: \usepackage{courier}
 
 ** Utopia
 <<utopia-font>>
 
-[[http://en.wikipedia.org/wiki/Utopia_(typeface)][Utopia]] is a transitional serif font designed by [[http://en.wikipedia.org/wiki/Robert_Slimbach][Robert Slimbach]] for
+[[https://en.wikipedia.org/wiki/Utopia_(typeface)][Utopia]] is a transitional serif font designed by [[https://en.wikipedia.org/wiki/Robert_Slimbach][Robert Slimbach]] for
 Adobe in 1989.  It became free software in 2006.  It is paired here
 with the Bera sans serif and monospaced fonts.  Note that the Utopia
 font clashes with the =amssymb= package.
 
-: #+LaTeX_HEADER: \usepackage[T1]{fontenc} 
+: #+LaTeX_HEADER: \usepackage[T1]{fontenc}
 : #+LaTeX_HEADER: \usepackage[adobe-utopia]{mathdesign}
-: #+LaTeX_HEADER: \usepackage[scaled]{berasans} 
+: #+LaTeX_HEADER: \usepackage[scaled]{berasans}
 : #+LaTeX_HEADER: \usepackage[scaled]{beramono}
 
 * Cross-references
@@ -1396,7 +1396,7 @@ includes a description.
 
 #+name: define-citep-link
 #+begin_src emacs-lisp :results silent
-  (org-add-link-type 
+  (org-add-link-type
    "citep" 'ebib
    (lambda (path desc format)
      (cond
@@ -1409,7 +1409,7 @@ includes a description.
 
 #+name: define-citet-link
 #+begin_src emacs-lisp :results silent
-  (org-add-link-type 
+  (org-add-link-type
    "citet" 'ebib
    (lambda (path desc format)
      (cond
@@ -1422,7 +1422,7 @@ includes a description.
 
 #+name: define-citealt-link
 #+begin_src emacs-lisp :results silent
-  (org-add-link-type 
+  (org-add-link-type
    "citealt" 'ebib
    (lambda (path desc format)
      (cond
@@ -1434,8 +1434,8 @@ includes a description.
 #+end_src
 
 #+name: define-citealp-link
-#+begin_src emacs-lisp 
-  (org-add-link-type 
+#+begin_src emacs-lisp
+  (org-add-link-type
    "citealp" 'ebib
    (lambda (path desc format)
      (cond
@@ -1447,8 +1447,8 @@ includes a description.
 #+end_src
 
 #+name: define-citealtstar-link
-#+begin_src emacs-lisp 
-  (org-add-link-type 
+#+begin_src emacs-lisp
+  (org-add-link-type
    "citealt*" 'ebib
    (lambda (path desc format)
      (cond
@@ -1460,8 +1460,8 @@ includes a description.
 #+end_src
 
 #+name: define-citealpstar-link
-#+begin_src emacs-lisp 
-  (org-add-link-type 
+#+begin_src emacs-lisp
+  (org-add-link-type
    "citealp*" 'ebib
    (lambda (path desc format)
      (cond
@@ -1473,8 +1473,8 @@ includes a description.
 #+end_src
 
 #+name: define-citepstar-link
-#+begin_src emacs-lisp 
-  (org-add-link-type 
+#+begin_src emacs-lisp
+  (org-add-link-type
    "citep*" 'ebib
    (lambda (path desc format)
      (cond
@@ -1486,8 +1486,8 @@ includes a description.
 #+end_src
 
 #+name: define-citetstar-link
-#+begin_src emacs-lisp 
-  (org-add-link-type 
+#+begin_src emacs-lisp
+  (org-add-link-type
    "citet*" 'ebib
    (lambda (path desc format)
      (cond
@@ -1501,15 +1501,15 @@ includes a description.
 
 *** Standard biblatex citation commands
 
-The standard biblatex citation commands have the following syntax: 
+The standard biblatex citation commands have the following syntax:
 \command[⟨prenote⟩][⟨postnote⟩]{⟨keys⟩}
 
 They have been implemented by parsing the description part of the link
 on a semicolon, so that, e.g.,
 =[[cite:foo][postnote;prenote]]= becomes
 =\cite[prenote][postnote]{foo}=.  Note that =[[cite:foo]]= and
-=[[cite:foo][;]]= are functionally equivalent.  
- 
+=[[cite:foo][;]]= are functionally equivalent.
+
 #+name: define-standard-biblatex-commands
 #+begin_src emacs-lisp :noweb yes :results silent :exports code
   <<define-biblatex-cite-link>>
@@ -1523,7 +1523,7 @@ on a semicolon, so that, e.g.,
 
 #+name: define-biblatex-cite-link
 #+begin_src emacs-lisp :results silent :exports code
-  (org-add-link-type 
+  (org-add-link-type
    "cite" 'ebib
    (lambda (path desc format)
      (cond
@@ -1539,7 +1539,7 @@ on a semicolon, so that, e.g.,
 
 #+name: define-biblatex-cap-cite-link
 #+begin_src emacs-lisp :results silent :exports code
-  (org-add-link-type 
+  (org-add-link-type
    "Cite" 'ebib
    (lambda (path desc format)
      (cond
@@ -1555,7 +1555,7 @@ on a semicolon, so that, e.g.,
 
 #+name: define-biblatex-parencite-link
 #+begin_src emacs-lisp :results silent :exports code
-  (org-add-link-type 
+  (org-add-link-type
    "parencite" 'ebib
    (lambda (path desc format)
      (cond
@@ -1571,7 +1571,7 @@ on a semicolon, so that, e.g.,
 
 #+name: define-biblatex-cap-parencite-link
 #+begin_src emacs-lisp :results silent :exports code
-  (org-add-link-type 
+  (org-add-link-type
    "Parencite" 'ebib
    (lambda (path desc format)
      (cond
@@ -1587,7 +1587,7 @@ on a semicolon, so that, e.g.,
 
 #+name: define-biblatex-footcite-link
 #+begin_src emacs-lisp :results silent :exports code
-  (org-add-link-type 
+  (org-add-link-type
    "footcite" 'ebib
    (lambda (path desc format)
      (cond
@@ -1603,7 +1603,7 @@ on a semicolon, so that, e.g.,
 
 #+name: define-biblatex-footcitetext-link
 #+begin_src emacs-lisp :results silent :exports code
-  (org-add-link-type 
+  (org-add-link-type
    "footcitetext" 'ebib
    (lambda (path desc format)
      (cond
@@ -1635,7 +1635,7 @@ ship with biblatex.
 
 #+name: define-biblatex-textcite-link
 #+begin_src emacs-lisp :results silent :exports code
-  (org-add-link-type 
+  (org-add-link-type
    "textcite" 'ebib
    (lambda (path desc format)
      (cond
@@ -1651,7 +1651,7 @@ ship with biblatex.
 
 #+name: define-biblatex-cap-textcite-link
 #+begin_src emacs-lisp :results silent :exports code
-  (org-add-link-type 
+  (org-add-link-type
    "Textcite" 'ebib
    (lambda (path desc format)
      (cond
@@ -1667,7 +1667,7 @@ ship with biblatex.
 
 #+name: define-biblatex-smartcite-link
 #+begin_src emacs-lisp :results silent :exports code
-  (org-add-link-type 
+  (org-add-link-type
    "smartcite" 'ebib
    (lambda (path desc format)
      (cond
@@ -1683,7 +1683,7 @@ ship with biblatex.
 
 #+name: define-biblatex-cap-smartcite-link
 #+begin_src emacs-lisp :results silent :exports code
-  (org-add-link-type 
+  (org-add-link-type
    "Smartcite" 'ebib
    (lambda (path desc format)
      (cond
@@ -1699,7 +1699,7 @@ ship with biblatex.
 
 #+name: define-biblatex-citestar-link
 #+begin_src emacs-lisp :results silent :exports code
-  (org-add-link-type 
+  (org-add-link-type
    "cite*" 'ebib
    (lambda (path desc format)
      (cond
@@ -1715,7 +1715,7 @@ ship with biblatex.
 
 #+name: define-biblatex-parencitestar-link
 #+begin_src emacs-lisp :results silent :exports code
-  (org-add-link-type 
+  (org-add-link-type
    "parencite*" 'ebib
    (lambda (path desc format)
      (cond
@@ -1731,7 +1731,7 @@ ship with biblatex.
 
 #+name: define-biblatex-supercite-link
 #+begin_src emacs-lisp :results silent :exports code
-  (org-add-link-type 
+  (org-add-link-type
    "supercite" 'ebib
    (lambda (path desc format)
      (cond
@@ -1750,10 +1750,8 @@ problem implementing the publishing project.
 Org-mode mailing list under the heading =text color + highlight= (!).
 There was a lively discussion there, to which the ideas of
 Samuel Wales, Christian Moe and Eric Schulte contributed directly to
-this implementation.    
+this implementation.
 [fn:3] The results of this experiment are now included in this
-document.  
+document.
 [fn:4] The =xcolor= manual is an education in color management and is
 highly recommended reading.
-
-

+ 6 - 7
org-tutorials/org-taskjuggler-scr.org

@@ -1,7 +1,7 @@
 #+OPTIONS:    H:3 num:nil toc:t \n:nil ::t |:t ^:t -:t f:t *:t tex:t d:(HIDE) tags:not-in-toc
 #+STARTUP:    align fold nodlcheck oddeven lognotestate
 #+SEQ_TODO:   TODO(t) INPROGRESS(i) WAITING(w@) | DONE(d) CANCELED(c@)
-#+TAGS:       Write(w) Update(u) Fix(f) Check(c) 
+#+TAGS:       Write(w) Update(u) Fix(f) Check(c)
 #+TITLE:      Кreiranje Gantt grafikona izvozom do TaskJuggler
 #+AUTHOR:     Jovana Milutinovich
 #+EMAIL:      jovanam AT webhostinggeeks DOT com
@@ -23,8 +23,8 @@ dodelićemo resurse zadacima, zatim napraviti raspored zadataka i kreirati
 odgovarajući gantt grafikon za ovaj projekat.
 
 Koristićemo [[http://www.taskjuggler.org/][TaskJuggler]] da bi rukovodili sa rasporedom zadataka,
-nivelisanjem izvora i kreiranjem bezbroj grafikona (kao [[http://en.wikipedia.org/wiki/Gantt_chart][Gantt grafikoni]]) za
-vašu mušteriju na vašem [[http://en.wikipedia.org/wiki/Pointy-haired_Boss][Pointy-haired Boss]].
+nivelisanjem izvora i kreiranjem bezbroj grafikona (kao [[https://en.wikipedia.org/wiki/Gantt_chart][Gantt grafikoni]]) za
+vašu mušteriju na vašem [[https://en.wikipedia.org/wiki/Pointy-haired_Boss][Pointy-haired Boss]].
 
 * Planirajte svoj projekat
 
@@ -69,7 +69,7 @@ vrednosti za “Effort property” kao što je pokazano na sledećoj slici:
 Rezultat vašeg projekta Org moda će izgledati nešto slično kao sledeće:
 
 #+BEGIN_SRC org
-  ,#+PROPERTY: Effort_ALL 2d 5d 10d 20d 30d 35d 50d 
+  ,#+PROPERTY: Effort_ALL 2d 5d 10d 20d 30d 35d 50d
   ,#+COLUMNS: %70ITEM(Task) %Effort
   ,
   ,* Accounting Software
@@ -244,7 +244,7 @@ primer je prekretnica “Ship Product to Customer” koji čeka dok se ne završ
 Beta i Ručni test.
 
 #+BEGIN_SRC org
-  ,#+PROPERTY: Effort_ALL 2d 5d 10d 20d 30d 35d 50d 
+  ,#+PROPERTY: Effort_ALL 2d 5d 10d 20d 30d 35d 50d
   ,#+PROPERTY: allocate_ALL dev doc test
   ,#+COLUMNS: %30ITEM(Task) %Effort %allocate %BLOCKER %ORDERED
   ,
@@ -373,7 +373,7 @@ Takođe TaskJuggler će vam dati pregled koliko će uposleni biti resursi i na
 [[file:../images/taskjuggler/resource-graph.png]]
 
 Na posletku, možete generisati [[file:../images/taskjuggler/project-plan.pdf][good-lookin project plans]] u PDF fajlove
-štampanjem iz TaskJuggler-a.Ovo će usrećiti svakog [[http://en.wikipedia.org/wiki/Pointy-haired_Boss][pointy-haired Boss]].
+štampanjem iz TaskJuggler-a.Ovo će usrećiti svakog [[https://en.wikipedia.org/wiki/Pointy-haired_Boss][pointy-haired Boss]].
 
 * Export of other properties
 
@@ -398,4 +398,3 @@ prve reči kao da je jedinstvena.
 [fn:4] U TaskJuggler-u dodeljivanja su kumulativna, izvoznik međutim,
 dodaje neke kodove tako da su nasleđena dodeljivanja ignorisana kada se
 eksplicitno dodeljuju resursu.
-

+ 11 - 12
org-tutorials/org-taskjuggler.org

@@ -1,7 +1,7 @@
 #+OPTIONS:    H:3 num:nil toc:t \n:nil ::t |:t ^:t -:t f:t *:t tex:t d:(HIDE) tags:not-in-toc
 #+STARTUP:    align fold nodlcheck oddeven lognotestate
 #+SEQ_TODO:   TODO(t) INPROGRESS(i) WAITING(w@) | DONE(d) CANCELED(c@)
-#+TAGS:       Write(w) Update(u) Fix(f) Check(c) 
+#+TAGS:       Write(w) Update(u) Fix(f) Check(c)
 #+TITLE:      Creating Gantt charts by Exporting to TaskJuggler
 #+AUTHOR:     Christian Egli
 #+EMAIL:      christian DOT egli AT sbs DOT ch
@@ -21,8 +21,8 @@ further, assign resources to the tasks, schedule the tasks and create
 the corresponding gantt chart for this project.
 
 We will be using [[http://www.taskjuggler.org/][TaskJuggler]] to handle the task scheduling, resource
-leveling and creation of a myriad of charts (such as [[http://en.wikipedia.org/wiki/Gantt_chart][Gantt chart]]) for
-your customer or your [[http://en.wikipedia.org/wiki/Pointy-haired_Boss][Pointy-haired Boss]].
+leveling and creation of a myriad of charts (such as [[https://en.wikipedia.org/wiki/Gantt_chart][Gantt chart]]) for
+your customer or your [[https://en.wikipedia.org/wiki/Pointy-haired_Boss][Pointy-haired Boss]].
 
 * Plan your project
 You start out as you normally would by breaking down the project into
@@ -58,7 +58,7 @@ efforts for each task. By using column view this can be done very
 efficiently. It also helps to define the =COLUMNS= and default values
 for the Effort property as shown in the following screen shot:
 
-#+CAPTION: Estimating effort using column view 
+#+CAPTION: Estimating effort using column view
 #+ATTR_HTML: alt="Estimating effort using column view"
 [[file:../images/taskjuggler/effort-estimation.png]]
 
@@ -66,7 +66,7 @@ Your resulting Org mode project file will look somewhat like the
 following:
 
 #+BEGIN_SRC org
-,#+PROPERTY: Effort_ALL 2d 5d 10d 20d 30d 35d 50d 
+,#+PROPERTY: Effort_ALL 2d 5d 10d 20d 30d 35d 50d
 ,#+COLUMNS: %70ITEM(Task) %Effort
 
 ,* Accounting Software
@@ -128,7 +128,7 @@ following:
 This allows you to have other nodes for this project such as an
 introduction or general notes.
 
-To export the project to TaskJuggler you simply type 
+To export the project to TaskJuggler you simply type
 
 : M-x org-export-as-taskjuggler-and-open
 
@@ -212,7 +212,7 @@ Obviously we need to define dependencies between the tasks.
 * Define dependencies
 There are several ways to define dependencies between tasks. When
 coming from an Org mode background you probably want to define them
-using the facilities provided by Org mode, which are either 
+using the facilities provided by Org mode, which are either
 
   - The =ORDERED= property which allows you to state that the child
     tasks have to be completed in the order they appear (top most
@@ -220,14 +220,14 @@ using the facilities provided by Org mode, which are either
 
   - The =BLOCKER= property which allows you to state that a task
     depends on either
-    - a previous sibling ("previous-sibling") or 
+    - a previous sibling ("previous-sibling") or
     - any other task by stating the ~task_id~ property of the
       predecessor
 
 Again, it is probably easiest to define the dependencies using the
 column view as shown below in the screen shot:
 
-#+CAPTION: Defining dependencies using column view 
+#+CAPTION: Defining dependencies using column view
 #+ATTR_HTML: alt="Defining dependencies using column view"
 [[file:../images/taskjuggler/define-dependencies.png]]
 
@@ -242,7 +242,7 @@ to Customer" which is waiting until the Beta test and the Manual are
 done.
 
 #+BEGIN_SRC org
-,#+PROPERTY: Effort_ALL 2d 5d 10d 20d 30d 35d 50d 
+,#+PROPERTY: Effort_ALL 2d 5d 10d 20d 30d 35d 50d
 ,#+PROPERTY: allocate_ALL dev doc test
 ,#+COLUMNS: %30ITEM(Task) %Effort %allocate %BLOCKER %ORDERED
 
@@ -371,7 +371,7 @@ will be and what they are working on. See below for a screen shot:
 [[file:../images/taskjuggler/resource-graph.png]]
 
 Finally you can generate [[file:../images/taskjuggler/project-plan.pdf][good-looking project plans]] in PDF by printing
-from TaskJuggler. This will make any [[http://en.wikipedia.org/wiki/Pointy-haired_Boss][Pointy-haired Boss]] happy.
+from TaskJuggler. This will make any [[https://en.wikipedia.org/wiki/Pointy-haired_Boss][Pointy-haired Boss]] happy.
 
 * Export of other properties
 Generally the exporter writes a node property that is known to
@@ -398,4 +398,3 @@ task will be determined through its priority cookie.
 [fn:4] In TaskJuggler the allocations are cumulative, the exporter
 however adds some code so that inherited allocation are ignored when
 explicitly assigning a resource.
-