Browse Source

Major fix

Fix broken links and resurrect files that can now be exported
correctly.
Bastien 1 year ago
parent
commit
0faff8ed94

+ 14 - 14
doc.org

@@ -8,24 +8,24 @@
 
 This page lists *all hooks, commands and options* of Org 9.0.9.
 
-- *Hooks* :: are options containing functions to be run before or after a
-             function.  For example, =org-mode-hook= can contain a list of
-             functions to be called after org-mode is turned on.
+- *Hooks* :: are options containing functions to be run before or after
+     a function.  For example, =org-mode-hook= can contain a list of
+     functions to be called after org-mode is turned on.
 
 - *Commands* :: are interactive functions that the user can run with =M-x
-                command RET=.  Most commands have an associated keybinding,
-                indicated here. Users can bind command to his preferred
-                keybinding.
+     command RET=.  Most commands have an associated keybinding,
+     indicated here. Users can bind command to his preferred
+     keybinding.
 
 - *Options* :: are variables that the user can set through the =customize=
-               interface. Calling =M-x customize-variable RET= then
-               completing over availables options will open the custom
-               interface, which makes it easy to set an option.
-
-These are the main "internals" that the uesr may want to know about, and we
-list them here for further reference.  E.g. You can safely create links to
-=https://orgmode.org/worg/doc.html#org-agenda= to refer to the documentation
-of the =org-agenda= command.
+     interface. Calling =M-x customize-variable RET= then completing
+     over availables options will open the custom interface, which
+     makes it easy to set an option.
+
+These are the main "internals" that the uesr may want to know about,
+and we list them here for further reference.  E.g. You can safely
+create links to =https://orgmode.org/worg/doc.html#org-agenda= to refer
+to the documentation of the =org-agenda= command.
 
 On top of these symbols, there are other non-interactive /functions/ and
 /variables/.  You can get more documentation about them with =C-h f org-

+ 50 - 47
exporters/taskjuggler/ox-taskjuggler.org

@@ -1,16 +1,15 @@
+#+TITLE:      Exporting Gantt charts with Taskjuggler v3 (tj3)
+#+AUTHOR:     John Henderson
+#+EMAIL:      jw DOT hendy AT gmail DOT com
 #+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)
-#+TITLE:      Exporting Gantt charts with Taskjuggler v3 (tj3)
-#+AUTHOR:     John Henderson
-#+EMAIL:      jw DOT hendy AT gmail DOT com
 #+LANGUAGE:   en
 #+PRIORITIES: A C B
 #+CATEGORY:   worg
 
-[[file:index.org][{Back to Worg's index}]]
-
+[[https://orgmode.org/worg/][{Back to Worg's index}]]
 
 * Introduction
 
@@ -30,9 +29,9 @@ longer features the former [[http://qt-project.org/][Qt]]-based GUI for task/tim
 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]].
 
-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
-the changes required to successfully export with tj3.
+The manual used to cover Taskjuggler export to some extent, however
+the defaults assume the use of version 2.x.x. This tutorial will lay
+out the changes required to successfully export with tj3.
 
 * Installation and Setup
 
@@ -100,8 +99,8 @@ In addition, here are a list of current variables you can customize:
 - org-taskjuggler-default-project-duration
 - 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]].
+  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]].
 - org-taskjuggler-extension
 - org-taskjuggler-final-hook
 - org-taskjuggler-keep-project-as-task
@@ -111,7 +110,7 @@ In addition, here are a list of current variables you can customize:
 - org-taskjuggler-reports-directory
 - org-taskjuggler-resource-tag
 - ~org-taskjuggler-target-version~: should be set to the output of the command =tj3
-     --version=, e.g. =(setq org-taskjuggler-target-version 3.4)=
+  --version=, e.g. =(setq org-taskjuggler-target-version 3.4)=
 - org-taskjuggler-valid-report-attributes
 - org-taskjuggler-valid-resource-attributes
 - org-taskjuggler-valid-task-attributes
@@ -144,7 +143,6 @@ particularly helpful:
   defined and assigned to the task, and will use his/her available work time/day to figure
   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
@@ -219,23 +217,28 @@ file, =home-renovation.org= and create a top level headline to contain our tasks
 #+END_SRC
 
 * References
+
 - [[http://www.taskjuggler.org/tj3/manual/toc.html][Taskjuggler (tj3) user manual]]
-- [[https://orgmode.org/manual/TaskJuggler-export.html][Taskjuggler in the Org-mode manual]]
-- [[https://orgmode.org/worg/org-tutorials/org-taskjuggler.html][Taskjuggler (v2) guide on Worg]] (though some functionality is out of date for using tj3,
-  most of the specifications still work, and the guide is excellent overall for getting a
-  feel for using Org-mode with Taskjuggler.
 
+- [[https://orgmode.org/worg/org-tutorials/org-taskjuggler.html][Taskjuggler (v2) guide on Worg]] (though some functionality is out of
+  date for using tj3, most of the specifications still work, and the
+  guide is excellent overall for getting a feel for using Org-mode
+  with Taskjuggler.
 
 * Footnotes
 
-[fn:1] You may run into compilation issues due to special characters in that file on
-lines 37 (a copyright symbol), 79, and 83 (two accented characters in resource names). If
-this happens, just replace those three characters with something else, or delete them,
-and the file should compile. [[https://github.com/taskjuggler/TaskJuggler/issues/105][An issue has been filed]] inquiring about whether or not this
-is a system setup issue and, if not, suggesting that the characters be replaced.
+[fn:1] You may run into compilation issues due to special characters
+in that file on lines 37 (a copyright symbol), 79, and 83 (two
+accented characters in resource names). If this happens, just replace
+those three characters with something else, or delete them, and the
+file should compile. [[https://github.com/taskjuggler/TaskJuggler/issues/105][An issue has been filed]] inquiring about whether
+or not this is a system setup issue and, if not, suggesting that the
+characters be replaced.
 
 * TODO Fill in the details!					   :noexport:
+
 ** Plan your project
+
 You start out as you normally would by breaking down the project into
 tasks. Let's take the following example where you have a project to
 create an accounting software:
@@ -425,15 +428,15 @@ 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
 
-  - The =ORDERED= property which allows you to state that the child
-    tasks have to be completed in the order they appear (top most
-    first).
+- The =ORDERED= property which allows you to state that the child
+  tasks have to be completed in the order they appear (top most
+  first).
 
-  - The =BLOCKER= property which allows you to state that a task
-    depends on either
-    - a previous sibling ("previous-sibling") or
-    - any other task by stating the ~task_id~ property of the
-      predecessor
+- The =BLOCKER= property which allows you to state that a task
+  depends on either
+  - 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:
@@ -706,28 +709,28 @@ by simply appending it.  The following examples should illustrate this:
 
 #+BEGIN_EXAMPLE:
 ** Preparation
-   :PROPERTIES:
-   :task_id:  preparation
-   :ORDERED:  t
-   :END:
+:PROPERTIES:
+:task_id:  preparation
+:ORDERED:  t
+:END:
 ** Training material
-   :PROPERTIES:
-   :task_id:  training_material
-   :ORDERED:  t
-   :END:
+:PROPERTIES:
+:task_id:  training_material
+:ORDERED:  t
+:END:
 *** Markup Guidelines
-    :PROPERTIES:
-    :Effort:   2d
-    :END:
+:PROPERTIES:
+:Effort:   2d
+:END:
 *** Workflow Guidelines
-    :PROPERTIES:
-    :Effort:   2d
-    :END:
+:PROPERTIES:
+:Effort:   2d
+:END:
 ** Presentation
-  :PROPERTIES:
-  :Effort:   2d
-  :BLOCKER:  training_material @{ gapduration 1d @} preparation
-  :END:
+:PROPERTIES:
+:Effort:   2d
+:BLOCKER:  training_material @{ gapduration 1d @} preparation
+:END:
 #+END_EXAMPLE:
 
 #+index: org-export-taskjuggler-default-reports

FIXME/org-customization-survey.org → org-configs/org-customization-survey.org


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

@@ -55,7 +55,7 @@ This document contains
     there. 
   - The tools shown here support either approach.
 
-- Some introductory tips at [[file:languages/ob-doc-R.org][ob-doc-R]] show how to enable full editing
+- Some introductory tips at [[file:../languages/ob-doc-R.org][ob-doc-R]] show how to enable full editing
   support for R code with ESS (http://ess.r-project.org/).
 
 - This document is to be put in the top level source directory of an R

+ 68 - 56
org-contrib/babel/examples/data-collection-analysis.org

@@ -1,62 +1,71 @@
+#+TITLE:      Org Mode: Data Collection and Analysis
+#+AUTHOR:     Eric Schulte
 #+OPTIONS:    H:3 num:nil toc:1 \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) 
-#+TITLE:      Org Mode: Data Collection and Analysis
-#+AUTHOR:     Eric Schulte
 #+EMAIL:      
 #+LANGUAGE:   en
 #+HTML_HEAD:      <style type="text/css">#outline-container-introduction{ clear:both; }</style>
 
-[[file:index.org][{Back to Babel's index}]]
+[[file:../index.org][{Back to Babel's index}]]
 
 * Data Collection and Analysis
-  This example uses Org-babel to automate a repeated data-collection
-  and analysis task.  A Ruby code block is used to scrape data from
-  the output of a computational experiment.  This data is then written
-  to an Org-mode table.  A block of R code reads from this table and
-  calculates lines of fit.  Finally a block of gnuplot code is used to
-  graph the results of both the raw data and the R analysis.  By
-  performing all of these steps within an Org-mode document working
-  notes, discussion, and TODOs can be naturally interspersed with the
-  code, and the results can easily be published to HTML or PDF for
-  distribution.
+
+This example uses Org-babel to automate a repeated data-collection and
+analysis task.  A Ruby code block is used to scrape data from the
+output of a computational experiment.  This data is then written to an
+Org-mode table.  A block of R code reads from this table and
+calculates lines of fit.  Finally a block of gnuplot code is used to
+graph the results of both the raw data and the R analysis.  By
+performing all of these steps within an Org-mode document working
+notes, discussion, and TODOs can be naturally interspersed with the
+code, and the results can easily be published to HTML or PDF for
+distribution.
 
 ** Requirement
-   - A working [[http://www.ruby-lang.org/en/][Ruby]] installation
-   - A working [[http://www.r-project.org/][R]] installation
-   - A working [[http://www.gnuplot.info/][gnuplot]] installation
+
+- A working [[http://www.ruby-lang.org/en/][Ruby]] installation
+- A working [[http://www.r-project.org/][R]] installation
+- A working [[http://www.gnuplot.info/][gnuplot]] installation
 
 ** Advantages
-   - Org-babel handles passing the data between different programming
-     languages
-   - Raw data persists in tables in the Org-mode file
-   - Working notes can be collocated with the code/results to which
-     they refer
-   - Tasks can be saved and updated from within the same file in which
-     the work is being performed
-   - Org-mode exporting facilities can be used to export the results
-     to HTML or PDF for distribution
+
+- Org-babel handles passing the data between different programming
+  languages.
+
+- Raw data persists in tables in the Org-mode file.
+
+- Working notes can be collocated with the code/results to which they
+  refer.
+
+- Tasks can be saved and updated from within the same file in which
+  the work is being performed.
+
+- Org-mode exporting facilities can be used to export the results to
+  HTML or PDF for distribution.
 
 ** Disadvantages
-   - This approach can allow the experimenter to use whatever language
-     is most comfortable for each sub-task, sometimes resulting in an
-     overly complicated work flow.  For example, in the example below I
-     did not have to learn how to calculate the mean and standard
-     deviation in R since it was easier for me to do so in Ruby even
-     though a full R solution would have been more efficient.
+
+- This approach can allow the experimenter to use whatever language is
+  most comfortable for each sub-task, sometimes resulting in an overly
+  complicated work flow.  For example, in the example below I did not
+  have to learn how to calculate the mean and standard deviation in R
+  since it was easier for me to do so in Ruby even though a full R
+  solution would have been more efficient.
 
 ** Example
 
 *** Code for running experiment and collecting the results
 
-    This portion will not be repeatable as it would require the
-    entire experimental setup.  It is provided for demonstration.
+This portion will not be repeatable as it would require the entire
+experimental setup.  It is provided for demonstration.
+
+*Ruby* run-timer-test: Runs the actual experiment.  This is tangled to
+an external file and run on the command line -- since these runs can
+take several days, I prefer to run them outside of Emacs (normally
+using [[http://www.gnu.org/software/screen/][screen]]).
 
-    *Ruby* run-timer-test: Runs the actual experiment.  This is
-    tangled to an external file and run on the command line -- since
-    these runs can take several days, I prefer to run them 
-    outside of Emacs (normally using [[http://www.gnu.org/software/screen/][screen]]).
 #+name: run-timer-test
 #+begin_src ruby :results silent :tangle timer :exports code
   DEFAULT_CMDLINE = "--swap 0 --del 0 --mut 0.1 example.c "
@@ -83,11 +92,11 @@
   end
 #+end_src
 
-    *Ruby* parse-output: The execution of =run-timer-test= leaves
-    results distributed across many text log files.  The following
-    Ruby source code block is
-    used to collect results from these files and dump them into an
-    Org-mode file as a table.
+*Ruby* parse-output: The execution of =run-timer-test= leaves results
+distributed across many text log files.  The following Ruby source
+code block is used to collect results from these files and dump them
+into an Org-mode file as a table.
+
 #+name: parse-output
 #+begin_src ruby :results output raw :exports code
   def look(path)
@@ -115,8 +124,9 @@
 #+end_src
 
 *** Data
-    Here is fake example output from the =parse-output= Ruby source
-    code block above.
+
+Here is fake example output from the =parse-output= Ruby source code
+block above.
 
 #+tblname: example-data
 | normal_0  | 1 | 150.264 | 150.631066 | 163.0 | 1 |
@@ -136,10 +146,12 @@
 | pll_3_6   | 3 |   1.433 |   2.018572 |   1.0 | 1 |
 
 *** Analysis
-    The code blocks in this section will be repeatable as they rely on
-    the fake data given above.
 
-    *Ruby* calculate mean and standard deviation over the second column
+The code blocks in this section will be repeatable as they rely on the
+fake data given above.
+
+*Ruby* calculate mean and standard deviation over the second column
+
 #+name: stddev
 #+begin_src ruby :var raw=example-data :results raw output :exports code
   by_procs = {}
@@ -161,7 +173,7 @@
 | 3 |       17.6483815 | 14.9070317402304 |
 | 4 | 43.0102596666667 | 42.1863032424348 |
 
-    *R* find the curve that best fits these data
+*R* find the curve that best fits these data
 #+begin_src R :session R :exports code :var data=example-stddev :results output
   procs <- data$V1
   times <- data$V2
@@ -185,8 +197,9 @@ Number of iterations to convergence: 1
 Achieved convergence tolerance: 3.924e-08
 #+end_example
 
-    *gnuplot* plot the raw data, along with the error bars and the best
-    fit curve
+*gnuplot* plot the raw data, along with the error bars and the best fit
+curve.
+
 #+begin_src gnuplot :var data=example-data :var mydata=example-stddev :exports code
   set xrange [0.5:5]
   set yrange [0:]
@@ -197,12 +210,11 @@ Achieved convergence tolerance: 3.924e-08
   replot 11.12 + 45.70/x title 'fit'
 #+end_src
 
-    Which produces the following [[file:../../../images/babel/example-graph.png]]
+Which produces the following [[file:../../../images/babel/example-graph.png]]
 
 *** Distribution
-    Using Org-mode's exporting capabilities it is easy to publish the
-    entire working file including source-code and raw data, to share
-    sections using `org-narrow-to-subtree', or even to share
-    individual tables or graphs.
-
 
+Using Org-mode's exporting capabilities it is easy to publish the
+entire working file including source-code and raw data, to share
+sections using `org-narrow-to-subtree', or even to share individual
+tables or graphs.

+ 1 - 1
org-contrib/babel/examples/latex-form.org

@@ -8,7 +8,7 @@
 #+LANGUAGE:   en
 #+HTML_HEAD:      <style type="text/css">#outline-container-introduction{ clear:both; }</style>
 
-[[file:index.org][{Back to Babel's index}]]
+[[file:~/install/git/worg/org-contrib/babel/index.org][{Back to Babel's index}]]
 
 * A LaTeX Form
   This example uses Org-babel as a user interface for a LaTeX form

+ 63 - 62
org-contrib/babel/examples/short-report.org

@@ -1,69 +1,70 @@
+#+TITLE:      Org-babel: Uses
+#+AUTHOR:     Thomas S. Dye
+#+EMAIL:      tsd at tsdye dot com
 #+OPTIONS:    H:3 num:nil toc:1 \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) 
-#+TITLE:      Org-babel: Uses
-#+AUTHOR:     Thomas S. Dye
-#+EMAIL:      tsd at tsdye dot com
 #+LANGUAGE:   en
 #+HTML_HEAD:      <style type="text/css">#outline-container-introduction{ clear:both; }</style>
 
-[[file:index.org][{Back to Babel's index}]]
+[[file:~/install/git/worg/org-contrib/babel/index.org][{Back to Babel's index}]]
 
 * A Standardized Short Report
-  This example is similar to the previous one, but here the users are
-  expected to write substantial content.  This type of workflow might
-  be used by a small organization whose employees regularly produce
-  standard documents and where the writing tasks for any one document
-  are divided among the authors.  
-
-  The HTML export facility of Org-mode is used to produce a guide to
-  writing the standardized short report.  This HTML file can be used
-  to train new authors.  The Org-mode content also supplies
-  substantial direction to experienced authors as they write.
-  Org-mode keywords and tags are used to keep track of writing
-  assignments and progress.  Org-babel's literate programming facility
-  makes it possible to present writing tasks to the authors in an order
-  different from which they appear in the report.
+
+This example is similar to the previous one, but here the users are
+expected to write substantial content.  This type of workflow might
+be used by a small organization whose employees regularly produce
+standard documents and where the writing tasks for any one document
+are divided among the authors.
+
+The HTML export facility of Org-mode is used to produce a guide to
+writing the standardized short report.  This HTML file can be used
+to train new authors.  The Org-mode content also supplies
+substantial direction to experienced authors as they write.
+Org-mode keywords and tags are used to keep track of writing
+assignments and progress.  Org-babel's literate programming facility
+makes it possible to present writing tasks to the authors in an order
+different from which they appear in the report.
 
 ** Requirement
-   - A working LaTeX installation.
+- A working LaTeX installation.
 
 ** Advantages
-   - The integration of training material with in-file instruction can
-     be quite effective.
-   - Many authors find it easy to work from the bottom up, or from the
-     particular to the general, rather than the usual sequence of
-     general-particular-general found in reports.
+- The integration of training material with in-file instruction can
+  be quite effective.
+- Many authors find it easy to work from the bottom up, or from the
+  particular to the general, rather than the usual sequence of
+  general-particular-general found in reports.
 
 ** Disadvantages
-   - Some features of reftex are not yet integrated into the source
-     code block editor, so writing and editing are sometimes less
-     convenient than writing to the LaTeX document directly.
+- Some features of reftex are not yet integrated into the source
+  code block editor, so writing and editing are sometimes less
+  convenient than writing to the LaTeX document directly.
 
 ** Example
-   - This report must satisfy the requirements set out in [[http://hawaii.gov/dlnr/hpd/pdfs/revproc_har/275_284/pdfs/278.pdf][the Historic
-     Preservation Division rule]].
-   - Complete each of the TODO items.
-   - Mark each item DONE when you have completed it.
-   - =C-c a t= will make an agenda of items left to do in this
-     document.
-   - =C-c a m= YOURNAME will make an agenda of writing tasks assigned
-     to you.
-   
+- This report must satisfy the requirements set out in [[http://hawaii.gov/dlnr/hpd/pdfs/revproc_har/275_284/pdfs/278.pdf][the Historic
+  Preservation Division rule]].
+- Complete each of the TODO items.
+- Mark each item DONE when you have completed it.
+- =C-c a t= will make an agenda of items left to do in this
+  document.
+- =C-c a m= YOURNAME will make an agenda of writing tasks assigned
+  to you.
+
 *** TODO Field Methods
 **** TODO Include the following information: [1/7]
-      - [X] When the fieldwork was carried out.
-      - [ ] Who directed the fieldwork.
-      - [ ] The names and qualifications of crew members.
-      - [ ] Establishment of site datum and grid.
-      - [ ] Excavation tools.
-      - [ ] Assignment of contexts.
-      - [ ] Bag list.
+- [X] When the fieldwork was carried out.
+- [ ] Who directed the fieldwork.
+- [ ] The names and qualifications of crew members.
+- [ ] Establishment of site datum and grid.
+- [ ] Excavation tools.
+- [ ] Assignment of contexts.
+- [ ] Bag list.
 **** DONE Include a citation to the project plan.
-     :LOGBOOK:
-     - State "DONE"       from "TODO"       [2009-11-25 Wed 09:53]
-     :END:
+:LOGBOOK:
+- State "DONE"       from "TODO"       [2009-11-25 Wed 09:53]
+:END:
 
 #+name: field-methods
 #+begin_src latex
@@ -77,19 +78,19 @@
 #+end_src   
 
 *** TODO Results
-    - Note the use of Org-mode tags to assign sections to authors Veronica and Eric.
-    - Discuss the artifacts and midden recovered during excavation.
+- Note the use of Org-mode tags to assign sections to authors Veronica and Eric.
+- Discuss the artifacts and midden recovered during excavation.
 
 
 **** TODO Artifacts						   :Veronica:
-     :LOGBOOK:
-     - State "TODO"       from "DONE"       [2009-11-25 Wed 09:44]
-     - State "DONE"       from "TODO"       [2009-11-25 Wed 09:44]
-     :END:
-     - Use Sinoto's classification of one-piece fishhooks.
-     - Cite Anell when describing two-piece fishhooks.
-     - Use Emory's classification of adzes when describing
-       cross-section.
+:LOGBOOK:
+- State "TODO"       from "DONE"       [2009-11-25 Wed 09:44]
+- State "DONE"       from "TODO"       [2009-11-25 Wed 09:44]
+:END:
+- Use Sinoto's classification of one-piece fishhooks.
+- Cite Anell when describing two-piece fishhooks.
+- Use Emory's classification of adzes when describing
+  cross-section.
 #+name: artifacts
 #+begin_src latex
   \subsection{Description of Artifacts}
@@ -99,8 +100,8 @@
 #+end_src
 
 **** TODO Midden						       :Eric:
-     - Use Kay for identifying and naming marine shells
-     - Cite Ziegler for information on fish habitats
+- Use Kay for identifying and naming marine shells
+- Cite Ziegler for information on fish habitats
 #+name: midden
 #+begin_src latex
   \subsection{Midden}
@@ -125,7 +126,7 @@
 
 
 *** TODO Introduction
-    - Give the reader a brief overview of the project and its results.
+- Give the reader a brief overview of the project and its results.
 
 #+name: intro
 #+begin_src latex
@@ -135,9 +136,9 @@
   % Text below this line
 #+end_src
 *** No data entry beyond this line
-    - The LaTeX code here sets up the environment and inserts the
-      defined source code blocks in their report order.
-    - A call to =org-babel-tangle= produces the LaTeX report document.
+- The LaTeX code here sets up the environment and inserts the
+  defined source code blocks in their report order.
+- A call to =org-babel-tangle= produces the LaTeX report document.
 
 #+begin_src latex :noweb :tangle report.tex
   \documentclass{article}

FIXME/header-args.org → org-contrib/babel/header-args.org


FIXME/how-to-use-Org-Babel-for-R.org → org-contrib/babel/how-to-use-Org-Babel-for-R.org


+ 25 - 24
org-contrib/babel/languages/ob-doc-stan.org

@@ -1,47 +1,48 @@
+#+TITLE:      Stan Source Code Blocks in Org Mode
 #+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) noexport(n)
-#+TITLE:      Stan Source Code Blocks in Org Mode
 #+AUTHOR:     Kyle Meyer
 #+EMAIL:      kyle[at]kyleam[dot]com
 #+LANGUAGE:   en
-#+HTML_HEAD:      <style type="text/css">#outline-container-introduction{ clear:both; }</style>
+#+HTML_HEAD:  <style type="text/css">#outline-container-introduction{ clear:both; }</style>
 #+LINK_UP:    ../languages.html
 #+LINK_HOME:  https://orgmode.org/worg/
 #+EXCLUDE_TAGS: noexport
 
 #+name: banner
 #+begin_export html
-  <div id="subtitle" style="float: center; text-align: center;">
+<div id="subtitle" style="float: center; text-align: center;">
   <p>
-  Org Mode support for <a href="http://mc-stan.org/">Stan</a>
+    Org Mode support for <a href="http://mc-stan.org/">Stan</a>
   </p>
   <p>
-  <a href="http://mc-stan.org/">
-  <img src="http://mc-stan.org/images/stan_logo.png"/>
-  </a>
+    <a href="http://mc-stan.org/">
+      <img src="http://mc-stan.org/images/stan_logo.png"/>
+    </a>
   </p>
-  </div>
+</div>
 #+end_export
 
 * Template Checklist [11/12] 					   :noexport:
-  - [X] Revise #+TITLE:
-  - [X] Indicate #+AUTHOR:
-  - [X] Add #+EMAIL:
-  - [X] Revise banner source block [3/3]
-    - [X] Add link to a useful language web site
-    - [X] Replace "Language" with language name
-    - [X] Find a suitable graphic and use it to link to the language
-      web site
-  - [X] Write an [[Introduction]]
-  - [X] Describe [[Requirements%20and%20Setup][Requirements and Setup]]
-  - [X] Replace "Language" with language name in [[Org%20Mode%20Features%20for%20Language%20Source%20Code%20Blocks][Org Mode Features for Language Source Code Blocks]]
-  - [X] Describe [[Header%20Arguments][Header Arguments]]
-  - [X] Describe support for [[Sessions]]
-  - [X] Describe [[Result%20Types][Result Types]]
-  - [ ] Describe [[Other]] differences from supported languages
-  - [X] Provide brief [[Examples%20of%20Use][Examples of Use]]
+
+- [X] Revise #+TITLE:
+- [X] Indicate #+AUTHOR:
+- [X] Add #+EMAIL:
+- [X] Revise banner source block [3/3]
+  - [X] Add link to a useful language web site
+  - [X] Replace "Language" with language name
+  - [X] Find a suitable graphic and use it to link to the language web
+    site
+- [X] Write an [[Introduction]]
+- [X] Describe [[Requirements%20and%20Setup][Requirements and Setup]]
+- [X] Replace "Language" with language name in [[Org%20Mode%20Features%20for%20Language%20Source%20Code%20Blocks][Org Mode Features for Language Source Code Blocks]]
+- [X] Describe [[Header%20Arguments][Header Arguments]]
+- [X] Describe support for [[Sessions]]
+- [X] Describe [[Result%20Types][Result Types]]
+- [ ] Describe [[Other]] differences from supported languages
+- [X] Provide brief [[Examples%20of%20Use][Examples of Use]]
 
 * Introduction
 

+ 1 - 1
FIXME/test-for-how-to-use-Org-Babel-for-R.org

@@ -1,4 +1,4 @@
-#+TITLE:Test 
+#+TITLE: Test
 #+AUTHOR: Your Name
 #+EMAIL: your-email@server.com
 #+PROPERTY: session *R* 

+ 60 - 41
org-contrib/gsoc2012/student-projects/git-merge-tool/manual.org

@@ -1,6 +1,7 @@
--*- mode:org -*-
 #+Title: Org Merge Driver
+
 * Introduction
+
 This is Org Merge Driver, a program for merging changes to Org mode
 files.
 
@@ -11,79 +12,87 @@ This project is currently being developed under Google Summer of Code
 - The homepage of Org-mode is [[https://orgmode.org][here]].
 
 * Obtaining the source code
-** TODO Fix the repo link
+
 The source code may be obtained from the GIT repository hosted at
 Orgmode.org.
 
 #+begin_src sh
-  git clone git://orgmode.org/org-merge-driver.git
+git clone https://code.orgmode.org/bzg/org-merge-driver
 #+end_src
 
 * Compiling
+
 Compiling this program requires that you have autotools installed. To
 compile this program, you should only have to run:
 
 #+begin_src sh
-  autoreconf --install && ./configure && make
+autoreconf --install && ./configure && make
 #+end_src
 
 If this fails because of missing dependencies, please see [[Dependencies][dependencies]]
 below.
 
 * Quick Start
+
 ** Using and Installation
+
 ** Git users:
+
 1. Add to your git configuration located in either
    ${GIT_DIR}/.git/config (for repository local configuration) or
    ~/.gitconfig (for global configuration) the following lines:
 
-#+begin_src sh
+   #+begin_src sh
   [merge "merge-orgmode"]
-  name = Org Mode merge driver
-  driver = /usr/local/bin/org-merge-driver -- %O %A %B %A
-#+end_src
+     name = Org Mode merge driver
+     driver = /usr/local/bin/org-merge-driver -- %O %A %B %A
+   #+end_src
 
 2. In every work tree you wish to you the org-merge-driver, make a
    .gitattributes file or .git/info/attributes if you don't want to have
    the file committed with the project.  Add the following line to this
    file:
 
-#+begin_example
-*.org merge=merge-orgmode
-#+end_example
-
-(See "man 5 gitattributes" for more info.)
+   #+begin_example
+   *.org merge=merge-orgmode
+   #+end_example
+   
+   (See "man 5 gitattributes" for more info.)
 
 ** Bazaar users:
+
 1. Install the [[http://doc.bazaar.canonical.com/plugins/en/index.html][extmerge bzr plug-in]]
+
 2. Add to your ~/.bazaar/bazaar.conf the line
 
-#+begin_src sh
-  external_merge = org-merge-driver -- %b %T %o %T
-#+end_src
+   #+begin_src sh
+   external_merge = org-merge-driver -- %b %T %o %T
+   #+end_src
 
 3. Then, to merge a conflict in a ChangeLog file, use
 
 #+begin_src sh
-  bzr extmerge --all --verbose
+bzr extmerge --all --verbose
 #+end_src
 
 ** Mercurial users:
+
 1. Add to your $HOME/.hgrc the lines
 
 #+begin_src sh
-  [merge-patterns]
-  ,**.org = org-merge-driver
+[merge-patterns]
+,**.org = org-merge-driver
 
-  [merge-tools]
-  org-merge-driver.executable = /usr/local/bin/org-merge-driver
-  org-merge-driver.args = -- $base $local $other $local
+[merge-tools]
+org-merge-driver.executable = /usr/local/bin/org-merge-driver
+org-merge-driver.args = -- $base $local $other $local
 #+end_src
 
 See [[http://www.selenic.com/mercurial/hgrc.5.html][Configuration files for Mercurial]], section merge-tools for
 reference.
 
 * Options
+
 This program currently supports the following options:
 
 | Short | Long                | Description                         |
@@ -99,6 +108,7 @@ This program currently supports the following options:
 | -V,   | --version           | Print program version               |
 
 ** "TODO" States
+
 If you have defined TODO states, you can describe them with this
 command. The defaults are set to "TODO" and "DONE". Declaring a single
 todo state causes the default set of todo states to be
@@ -107,10 +117,11 @@ discarded. Because of this, you must declare all TODO states used.
 At this time, Todo states can only be configured on the command line.
 
 #+begin_example
-  org-merge-driver -tDONE --todo=TODO
+org-merge-driver -tDONE --todo=TODO
 #+end_example
 
 ** Priority Cookies
+
 If you have defined more priority states system-wide, you can describe
 them with this command. The defaults are set to 'A', 'B', and 'C'. You
 must declare all priority states used (all defaults are immediately
@@ -118,64 +129,72 @@ overridden). Currently, priority cookies may only be a single ASCII
 character.
 
 #+begin_example
-  org-merge-driver -pA -pB --priority=C
+org-merge-driver -pA -pB --priority=C
 #+end_example
 
 ** Right Margin
+
 Org-merge-driver will attempt to minimize reformatting, but it is
 sometimes necessary for org-merge-driver to realign text on the right
 margin of the text. This can happen after merging lists of heading
 TAGS.
 
 You can set the preferred right margin value (in spaces) with the
-=--rmargin== command. If the margin is not large enough to fit a line
-of text, it will extend past the margin. The default margin value is
-77 spaces.
+=--rmargin== command. If the margin is not large enough to fit a line of
+text, it will extend past the margin. The default margin value is 77
+spaces.
 
 #+begin_example
-  org-merge-driver -m77
+org-merge-driver -m77
 #+end_example
 
 ** Specify Input and Out Files
+
 To perform a merge, org-merge-driver requires three files -- your copy
 of a file, a remotely updated file, and a common ancestor file. These
 are given to org-merge-driver in the order ancestor, local, remote.
 
 To ensure that the file names are not confused with command line
-options, you can seperate them from the rest of the arguments with
-=--=.
+options, you can seperate them from the rest of the arguments with =--=.
 
 By default, org-merge-driver prints the merged file to stdout.  To
 have the output printed to a file, specify a fourth file on the
 command line.
 
 #+begin_example
-  org-merge-driver -- ancestor.org local-update.org remote-update.org output.org
+org-merge-driver -- ancestor.org local-update.org remote-update.org output.org
 #+end_example
 
 * Dependencies
+
 To compile org-merge-driver, you may need: [[http://www.gnu.org/software/gnulib/][Gnulib]], [[http://flex.sourceforge.net/][Flex]] (not lex) and
-GNU Autotools installed.  Install Flex and autotools using your desired
-package manager.  To obtain gnulib follow the instructions below.
+GNU Autotools installed.  Install Flex and autotools using your
+desired package manager.  To obtain gnulib follow the instructions
+below.
 
 ** To obtain Gnulib:
+
 You must obtain Gnulib by it's source code, there is no binary
 distribution.  Through git or cvs:
+
 #+begin_src sh
-  git clone git://git.savannah.gnu.org/gnulib.git
-  # or
-  cvs -d :pserver:anonymous@pserver.git.sv.gnu.org:/gnulib.git co -d gnulib HEAD
+git clone git://git.savannah.gnu.org/gnulib.git
+# or
+cvs -d :pserver:anonymous@pserver.git.sv.gnu.org:/gnulib.git co -d gnulib HEAD
 #+end_src
 
 ** Reimporting gnulib-tool dependencies
+
 #+begin_src sh
-  cd $(top_srcdir)
-  /PATH/TO/GNULIB/gnulib-tool --add-import
+cd $(top_srcdir)
+/PATH/TO/GNULIB/gnulib-tool --add-import
 #+end_src
 
 ** Compiling
-To compile,  run:
+
+To compile, run:
+
 #+begin_src sh
-  autoreconf -i
-  ./configure && make
+autoreconf -i
+./configure && make
 #+end_src

+ 74 - 115
FIXME/org-people.org

@@ -385,12 +385,12 @@ http://twitter.com/andrewhyatt.
 
 {{{person(Shidai Liu\, aka Leo,https://orgmode.org/img/people/leo.jpg)}}}
 
-=Planner= got me started on =Emacs= in late 2005 after seeing some of
-it's cool features.  One year later (October 2006) I moved to =Org=,
+=Planner= got me started on =Emacs= in late 2005 after seeing some of it's
+cool features.  One year later (October 2006) I moved to =Org=,
 realising how much more powerful it was, plus the vibrant community it
-has.  From then on =Org= has been the focal point of my pure
-emacs-based personal information manager (=Org=, =Gnus=, =BBDB=,
-=Calendar=, =Diary=, etc.).  Here is a list of things I use Emacs for:
+has.  From then on =Org= has been the focal point of my pure emacs-based
+personal information manager (=Org=, =Gnus=, =BBDB=, =Calendar=, =Diary=, etc.).
+Here is a list of things I use Emacs for:
 
 |-------------------------+-------------------|
 | TASKS                   | EMACS SOLUTION    |
@@ -424,6 +424,7 @@ focus in the future. But whatever I do I will use Emacs + Org!
 # Pete Phillips -------------------------------------------------------------
 
 {{{person(Pete Phillips,http://www.petephillips.me.uk/images/pete-karen-italy2009_medsize.jpg)}}}
+
 (I'm the one on the left btw.)
 
 I started using org-mode in Aug 2005.  Before that I had used 3
@@ -480,32 +481,31 @@ I started using Emacs just to use Org-mode. Then Emacs began to be my
 second operating system; the first is [[http://www.debian.org][Debian GNU/Linux]], and the last
 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
-mailing list. I pay particular attention to the posts
+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 mailing list. I pay particular attention to the posts
 concerning Windows.
 
 I am also active in my LUG: [[http://erlug.linux.it/main/][Emilia-Romagna LUG]], since I think that
 when spreading free software /the more the merrier/.
 
-I love reading. The books I have just finished
-are [[http://www.wumingfoundation.com/english/about_our_books.htm][Q]] and [[http://www.enricobrizzi.it/inattesapiega/index.htm][L'inattesa piega degli eventi]].
+I love reading. The books I have just finished are [[http://www.wumingfoundation.com/english/about_our_books.htm][Q]] and [[http://www.enricobrizzi.it/inattesapiega/index.htm][L'inattesa
+piega degli eventi]].
 
 # T.V. Raman ------------------------------------------------------------------
 
 {{{person(T.V. Raman,http://lh4.ggpht.com/_3FmCG50jehg/R2l7StSQVII/AAAAAAAAA44/tLI0crQJaG4/s512/%20009.JPG)}}}
 
-I am a Computer Scientist with over 11 years of industry
-experience in advanced technology development. During this time, I
-have authored 3 books and filed over 25 patents; my work on auditory
-interfaces was profied in the September 1996 issue of Scientific
-American. I have leading edge expertise in Web standards, auditory
-interfaces and scripting languages. I participate in numerous W3C
-working groups and authored Aural CSS (ACSS); in 1996 I wrote the
-first ACSS implementation. I have led the definition of XML
-specifications for the next generation WWW including XForms, XML
-Events, and Compound Document Formats such as X+V.
+I am a Computer Scientist with over 11 years of industry experience in
+advanced technology development. During this time, I have authored 3
+books and filed over 25 patents; my work on auditory interfaces was
+profied in the September 1996 issue of Scientific American. I have
+leading edge expertise in Web standards, auditory interfaces and
+scripting languages. I participate in numerous W3C working groups and
+authored Aural CSS (ACSS); in 1996 I wrote the first ACSS
+implementation. I have led the definition of XML specifications for
+the next generation WWW including XForms, XML Events, and Compound
+Document Formats such as X+V.
 
 T.V. Raman is blind and uses Emacs for much of his interaction with
 his computer system, because he has taught Emacs to [[http://emacspeak.sourceforge.net/raman/][speak]].  I
@@ -517,69 +517,31 @@ picture shows him with his dog /Bubbles/.
 
 {{{person150(Andreas Roehler,https://orgmode.org/img/org-mode-unicorn.png)}}}
 
-Studying economics in former GDR until 1975, my diploma
-thesis has been rejected as I proposed a cure employing
-free speech, free press, independent unions etc.
-
-Turned towards literature later, wrote plays, prose and
-poetry.  Former Bertolt Brecht Theater Berliner
-Ensemble staged 1993 my adaption of Aischylos "The
-Persians".
-
-Crossed the Berlin Wall in 1984 and proceeded - next
-turn of life came with lecture of a book by french
-sociologist Serge Thion: Historical Truth or Political
-Truth.
-
-Translated the book with the help of friend and
-finally, as no one would do it in Germany, published it
-in 1994. A lot of things stirred up, we started a
-journal too.  Refusing the common power play we
-invited people with quite different ideas, religions
-etc., published articles from right-wing settlers as
-from muslim activists, published Norman Podhoretz and
-Noam Chomsky likewise.
-
-Things got hot, service took action, the computers and
-all the equipment being seized again and again; seizures,
-which have been forbidden by german press law beside.
-
-Detected GNU Linux at this occasion - not to pay
-licenses repeatedly. Detected Emacs - free software is
-a kind of free speech.
-
-
-Literatur- und Kunstpreisträger im Karin Fischer Verlag ...
-, Andreas Röhler (W.-Hasenclever-Preis) ...
-[[http://www.karin-fischer-verlag.de/sites/preistraeger.html]]
-
-Theaterverlag Desch
-Aischylos. DIE ORESTIE Schauspiel 5 D 7 H Stand: 27.03.01 ·
-DIE PERSER (Ü: Andreas Röhler) Schauspiel 1 D 3 H Stand:
-27.03.01.
-[[http://www.theater-verlag-desch.de/autoren/showAuthor?autor=Aischylos]]
-
-Gedichte. Grafik von Thuur Camps Röhler, Andreas Berlin,
-Mariannepresse. 1986. Gedichte. (Graz) 1943. 136 S., 2 Taf.
-23 cm. OPp Goll, Ernst Verlag: Leykam. ...
-[[http://ade.bookmaps.org/g/e/ged_69.html]]
-
-Teilnehmer seit 1980
-... Dirk Kurbjuweit, Katja Lange-Müller, Harry Mulisch,
-Albert Ostermaier ... Peter Piwitt, Hans Pleschinski,
-Andreas Röhler, Dieter Schmidt, Eva ...
-[[http://www.poetenfest-erlangen.de/archiv/teilnehmerliste.htm]]
-
-Magisterarbeit
-eingereicht von Andreas Kölling. Wissenschaftliche Betreuung:
-Professor Stephan .... Christa Moog, Hans (Chaim) Noll,
-Andreas Röhler, Karl Hermann Röhricht, ...
-[[http://www.textbatzen-andreas.de/magister/magister.html]]
-
-Bis 2003 Herausgeber der
-Zeitschrift für Kultur Geschichte und Politik, Sleipnir
-[[http://www.sleipnir.netfirms.com]]
+Studying economics in former GDR until 1975, my diploma thesis has
+been rejected as I proposed a cure employing free speech, free press,
+independent unions etc.
+
+Turned towards literature later, wrote plays, prose and poetry.
+Former Bertolt Brecht Theater Berliner Ensemble staged 1993 my
+adaption of Aischylos "The Persians".
+
+Crossed the Berlin Wall in 1984 and proceeded - next turn of life came
+with lecture of a book by french sociologist Serge Thion: Historical
+Truth or Political Truth.
+
+Translated the book with the help of friend and finally, as no one
+would do it in Germany, published it in 1994. A lot of things stirred
+up, we started a journal too.  Refusing the common power play we
+invited people with quite different ideas, religions etc., published
+articles from right-wing settlers as from muslim activists, published
+Norman Podhoretz and Noam Chomsky likewise.
 
+Things got hot, service took action, the computers and all the
+equipment being seized again and again; seizures, which have been
+forbidden by german press law beside.
+
+Detected GNU Linux at this occasion - not to pay licenses
+repeatedly. Detected Emacs - free software is a kind of free speech.
 
 # Eric Schulte ----------------------------------------------------------------
 
@@ -623,7 +585,6 @@ looking around until I found Org-mode around August 2007 and that was
 the end of my journey. It was like finding out who you are going to
 spend the rest of your life with. :)
 
-
 I initially thought Org was awesome and could not be improved further
 but I had underestimated Carsten, various contributors and the amazing
 community of users who keep pushing the envelope of what is possible
@@ -640,11 +601,11 @@ or use full power of Org.
 {{{person(David O'Toole,https://orgmode.org/img/people/dto.jpg)}}}
 
 David O'Toole is a Lisp programmer living in Massachusetts, USA.
-Interests include GNU Emacs, Ubuntu, and independent games development.
+Interests include GNU Emacs, Ubuntu, and independent games
+development.
 
 His website is http://dto.github.com/notebook
 
-
 # Karl Voit --------------------------------------------------------------
 
 {{{person200(Karl Voit,http://karl-voit.at/images/2012-01-05-orgmode-userphoto.jpg)}}}
@@ -666,10 +627,9 @@ 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]], [[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.
+[[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.
 
 From 2009--2012 I was writing [[http://tagstore.org/en/papers][my PhD thesis]] in the field of PIM and
 Information Architecture. You probably have heard of [[http://tagstore.org][tagstore]] which is
@@ -709,33 +669,32 @@ blog]].
 I started using Emacs on large Unix systems when I was still a physics
 student, but I confess to have strayed from the Path in later years,
 as I had been disappointed with its lack of integration into the other
-platforms I needed to use for my [[http://www.nf.mpg.de/cv/stefan-vollmar.html][work]] at the
-[[http://www.nf.mpg.de/index.php?L%3D1][Max Planck Institute for Neurological Research Cologne]].
-
-This has changed with [[http://aquamacs.org/][Aquamacs Emacs]] and
-newer versions of Emacs in general. Org-mode is a very (very) good
-reason on its own to re-consider Emacs - in my case, it was "love on
-first sight" with Org-mode's conceptual beauty, even before I found out about
-the astonishing Org community and the torrent of continuous
-improvements.
-
-Org-mode was instrumental for planning our
-[[http://www.nf.mpg.de/kinderuni/kinderuni_en.html][Looking into Brains]] project,
-also for generating its [[http://www.nf.mpg.de/kinderuni][HTML]] documentation. We have started to use
-Org-mode for the software documentation of my group's
-platform-independent [[http://www.nf.mpg.de/vhist][VHIST]] and
-[[http://www.nf.mpg.de/vinci3][VINCI]] projects and are working on an
+platforms I needed to use for my [[http://www.nf.mpg.de/cv/stefan-vollmar.html][work]] at the [[http://www.nf.mpg.de/index.php?L%3D1][Max Planck Institute for
+Neurological Research Cologne]].
+
+This has changed with [[http://aquamacs.org/][Aquamacs Emacs]] and newer versions of Emacs in
+general. Org-mode is a very (very) good reason on its own to
+re-consider Emacs - in my case, it was "love on first sight" with
+Org-mode's conceptual beauty, even before I found out about the
+astonishing Org community and the torrent of continuous improvements.
+
+Org-mode was instrumental for planning our [[http://www.nf.mpg.de/kinderuni/kinderuni_en.html][Looking into Brains]]
+project, also for generating its [[http://www.nf.mpg.de/kinderuni][HTML]] documentation. We have started
+to use Org-mode for the software documentation of my group's
+platform-independent [[http://www.nf.mpg.de/vhist][VHIST]] and [[http://www.nf.mpg.de/vinci3][VINCI]] projects and are working on an
 integration with their [[http://qt.nokia.com/][Qt]]-based frameworks.
 
-Staff members of our instiute may have a personal page for CV-related information. We found that
-Org-mode works very well for this purpose when a suitable template is provided - instructions and all
-template files are [[http://www.nf.mpg.de/cv-howto/cv-en.html][online]].
+Staff members of our instiute may have a personal page for CV-related
+information. We found that Org-mode works very well for this purpose
+when a suitable template is provided - instructions and all template
+files are [[http://www.nf.mpg.de/cv-howto/cv-en.html][online]].
 
-Carsten Dominik gave a guest talk at our institute about [[http://www.nf.mpg.de/orgmode/guest-talk-dominik.html][Organizing a Scientist's Life and Work]] - very convincing.
+Carsten Dominik gave a guest talk at our institute about [[http://www.nf.mpg.de/orgmode/guest-talk-dominik.html][Organizing a
+Scientist's Life and Work]] - very convincing.
 
-My only remaining problem with Org-mode is to communicate properly
-my very own list of favorite features: it just takes too long to
-list them all...
+My only remaining problem with Org-mode is to communicate properly my
+very own list of favorite features: it just takes too long to list
+them all...
 
 # Andrew Young ----------------------------------------------------------------
 
@@ -753,8 +712,8 @@ I became involved with org-mode development and the community through
 Google Summer of Code during 2012, where I created a specialized [[https://orgmode.org/worg/org-contrib/gsoc2012/student-projects/git-merge-tool/index.html][merge
 driver]].
 
-I am really excited about org-mode, and can't wait to see what the future
-brings.
+I am really excited about org-mode, and can't wait to see what the
+future brings.
 
 # Keep the following line at the end of the buffer
 @@html:<br style="clear:both;" />@@