Documentation: More credits.

This commit is contained in:
Carsten Dominik 2008-12-31 18:22:46 +01:00
parent cd92610d1a
commit ffd89f5752
2 changed files with 12 additions and 8 deletions

View File

@ -21,8 +21,9 @@ Org-mode now supports the creation of footnotes. In contrast to the
larger document, not only for one-off documents like emails. The basic larger document, not only for one-off documents like emails. The basic
syntax is similar to the one used by `footnote.el', i.e. a footnote is syntax is similar to the one used by `footnote.el', i.e. a footnote is
defined in a paragraph that is started by a footnote marker in square defined in a paragraph that is started by a footnote marker in square
brackets in column 0. The footnote reference is simply the marker in brackets in column 0, no indentation allowed. The footnote
square brackets inside text. For example: reference is simply the marker in square brackets inside text.
For example:
#+begin_src org #+begin_src org
The Org homepage[1] now looks a lot better than it used to. The Org homepage[1] now looks a lot better than it used to.
@ -54,7 +55,7 @@ The following command handles footnotes:
- C-c C-x f :: - C-c C-x f ::
The footnote action command. When the cursor is on a footnote The footnote action command. When the cursor is on a footnote
reference, jump to the definition. When it is at a definition, reference, jump to the definition. When it is at a definition,
jump to the reference. Otherwise, create a new footnote. jump to the (first) reference. Otherwise, create a new footnote.
Depending on the variable `org-footnote-define-inline' (with Depending on the variable `org-footnote-define-inline' (with
associated #+STARTUP options fninline and nofninline), the associated #+STARTUP options fninline and nofninline), the
definitions will be placed locally, or into the nearest outline definitions will be placed locally, or into the nearest outline

View File

@ -1375,8 +1375,8 @@ Org-mode supports the creation of footnotes. In contrast to the
larger document, not only for one-off documents like emails. The basic larger document, not only for one-off documents like emails. The basic
syntax is similar to the one used by @file{footnote.el}, i.e. a footnote is syntax is similar to the one used by @file{footnote.el}, i.e. a footnote is
defined in a paragraph that is started by a footnote marker in square defined in a paragraph that is started by a footnote marker in square
brackets in column 0. The footnote reference is simply the marker in square brackets in column 0, no indentation allowed. The footnote reference is
brackets inside text. For example: simply the marker in square brackets, inside text. For example:
@example @example
The Org homepage[1] now looks a lot better than it used to. The Org homepage[1] now looks a lot better than it used to.
@ -1408,8 +1408,8 @@ Since Org allows multiple references to the same note, you can then use use
@kindex C-c C-x f @kindex C-c C-x f
@item C-c C-x f @item C-c C-x f
The footnote action command. When the cursor is on a footnote reference, The footnote action command. When the cursor is on a footnote reference,
jump to the definition. When it is at a definition, jump to the reference. jump to the definition. When it is at a definition, jump to the (first)
Otherwise, create a new footnote. Depending on the variable reference. Otherwise, create a new footnote. Depending on the variable
@code{org-footnote-define-inline}@footnote{The corresponding in-buffer @code{org-footnote-define-inline}@footnote{The corresponding in-buffer
setting is: @code{#+STARTUP: fninline} or @code{#+STARTUP: nofninline}}, the setting is: @code{#+STARTUP: fninline} or @code{#+STARTUP: nofninline}}, the
definitions will be placed locally, or into the nearest outline section with definitions will be placed locally, or into the nearest outline section with
@ -10158,6 +10158,9 @@ folded entries, and column view for properties.
@i{Shidai Liu} ("Leo") asked for embedded La@TeX{} and tested it. He also @i{Shidai Liu} ("Leo") asked for embedded La@TeX{} and tested it. He also
provided frequent feedback and some patches. provided frequent feedback and some patches.
@item @item
@i{Matt Lundin} has proposed last-row references for table formulas and named
invisible anchors. He has also worked a lot on the FAQ.
@item
@i{Jason F. McBrayer} suggested agenda export to CSV format. @i{Jason F. McBrayer} suggested agenda export to CSV format.
@item @item
@i{Max Mikhanosha} came up with the idea of refiling. @i{Max Mikhanosha} came up with the idea of refiling.
@ -10218,7 +10221,7 @@ Linking to VM/BBDB/Gnus was first inspired by @i{Tom Shannon}'s
@file{organizer-mode.el}. @file{organizer-mode.el}.
@item @item
@i{Ilya Shlyakhter} proposed the Archive Sibling, line numbering in literal @i{Ilya Shlyakhter} proposed the Archive Sibling, line numbering in literal
examples, adn remote highlighting for referenced code lines. examples, and remote highlighting for referenced code lines.
@item @item
@i{Stathis Sideris} wrote the @file{ditaa.jar} ASCII to PNG converter that is @i{Stathis Sideris} wrote the @file{ditaa.jar} ASCII to PNG converter that is
now packaged into Org's @file{contrib} directory. now packaged into Org's @file{contrib} directory.