[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Emacs-diffs] Changes to emacs/man/org.texi
|
From: |
Carsten Dominik |
|
Subject: |
[Emacs-diffs] Changes to emacs/man/org.texi |
|
Date: |
Fri, 15 Apr 2005 02:55:09 -0400 |
Index: emacs/man/org.texi
diff -c emacs/man/org.texi:1.6 emacs/man/org.texi:1.7
*** emacs/man/org.texi:1.6 Wed Mar 30 12:42:09 2005
--- emacs/man/org.texi Fri Apr 15 06:55:07 2005
***************
*** 3,9 ****
@setfilename ../info/org
@settitle Org Mode Manual
! @set VERSION 3.05
@set DATE April 2005
@dircategory Emacs
--- 3,9 ----
@setfilename ../info/org
@settitle Org Mode Manual
! @set VERSION 3.06
@set DATE April 2005
@dircategory Emacs
***************
*** 92,98 ****
Introduction
* Summary:: Brief summary of what Org-mode does
! * Installation:: How to install Org-mode
Document Structure
--- 92,98 ----
Introduction
* Summary:: Brief summary of what Org-mode does
! * Installation and Activation:: How to install Org-mode
Document Structure
***************
*** 106,113 ****
TODO items
* TODO basics:: Marking and displaying TODO entries
- * Priorities:: Some things are more important than others
* TODO extensions:: Workflow and assignments
Extended use of TODO keywords
--- 106,113 ----
TODO items
* TODO basics:: Marking and displaying TODO entries
* TODO extensions:: Workflow and assignments
+ * Priorities:: Some things are more important than others
Extended use of TODO keywords
***************
*** 133,140 ****
Timeline and Agenda
! * Timeline (single file):: Time-sorted view for single file
! * Agenda (multiple files):: Your weekly planner
* Agenda commands:: Remote editing of org trees
* Calendar/Diary integration:: Integrating Anniversaries and more
--- 133,140 ----
Timeline and Agenda
! * Timeline:: Time-sorted view for single file
! * Agenda:: Your weekly planner
* Agenda commands:: Remote editing of org trees
* Calendar/Diary integration:: Integrating Anniversaries and more
***************
*** 168,177 ****
@menu
* Summary:: Brief summary of what Org-mode does
! * Installation:: How to install Org-mode
@end menu
! @node Summary, Installation, Introduction, Introduction
@section Summary
@cindex summary
--- 168,177 ----
@menu
* Summary:: Brief summary of what Org-mode does
! * Installation and Activation:: How to install Org-mode
@end menu
! @node Summary, Installation and Activation, Introduction, Introduction
@section Summary
@cindex summary
***************
*** 214,221 ****
@page
! @node Installation, , Summary, Introduction
! @section Installation
@cindex installation
@cindex autoload
@cindex global keybindings
--- 214,221 ----
@page
! @node Installation and Activation, , Summary, Introduction
! @section Installation and Activation
@cindex installation
@cindex autoload
@cindex global keybindings
***************
*** 236,247 ****
--- 236,250 ----
and @command{org-agenda} - please choose suitable keys yourself.
@lisp
+ ;; These lines only if org-mode is not part of the X/Emacs distribution.
(autoload 'org-mode "org" "Org mode" t)
(autoload 'org-diary "org" "Diary entries from Org mode")
(autoload 'org-agenda "org" "Multi-file agenda from Org mode" t)
(autoload 'org-store-link "org" "Store a link to the current location" t)
(autoload 'orgtbl-mode "org" "Org tables as a minor mode" t)
(autoload 'turn-on-orgtbl "org" "Org tables as a minor mode")
+
+ ;; The following lines are always needed. Choose your own keys.
(add-to-list 'auto-mode-alist '("\\.org$" . org-mode))
(define-key global-map "\C-cl" 'org-store-link)
(define-key global-map "\C-ca" 'org-agenda)
***************
*** 257,263 ****
@end example
@noindent which will select Org-mode for this buffer no matter what
! the file's name is.
@node Document Structure, TODO items, Introduction, Top
@chapter Document Structure
--- 260,267 ----
@end example
@noindent which will select Org-mode for this buffer no matter what
! the file's name is. See also the variable
! @code{org-insert-mode-line-in-empty-file'}.
@node Document Structure, TODO items, Introduction, Top
@chapter Document Structure
***************
*** 361,369 ****
@example
#+STARTUP: fold
#+STARTUP: nofold
@end example
-
@node Motion, Structure editing, Visibility cycling, Document Structure
@section Motion
@cindex motion, between headlines
--- 365,373 ----
@example
#+STARTUP: fold
#+STARTUP: nofold
+ #+STARTUP: content
@end example
@node Motion, Structure editing, Visibility cycling, Document Structure
@section Motion
@cindex motion, between headlines
***************
*** 411,416 ****
--- 415,423 ----
@kindex address@hidden
@item address@hidden
Insert new heading with same level as current
+ @kindex address@hidden
+ @item address@hidden
+ Insert new TODO entry with same level as current heading.
@kindex address@hidden
@item address@hidden
Promote current heading by one level
***************
*** 437,443 ****
Copy subtree to kill ring.
@kindex C-c C-h C-y
@item C-c C-h C-y
! Yank subtree from kill ring. This does modify the level of subtree to
make sure the tree fits in nicely at the yank position. The yank
level can also be specified with a prefix arg, or by yanking after a
headline marker like @samp{****}.
--- 444,450 ----
Copy subtree to kill ring.
@kindex C-c C-h C-y
@item C-c C-h C-y
! Yank subtree from kill ring. This does modify the level of the subtree to
make sure the tree fits in nicely at the yank position. The yank
level can also be specified with a prefix arg, or by yanking after a
headline marker like @samp{****}.
***************
*** 513,523 ****
@menu
* TODO basics:: Marking and displaying TODO entries
- * Priorities:: Some things are more important than others
* TODO extensions:: Workflow and assignments
@end menu
! @node TODO basics, Priorities, TODO items, TODO items
@section Basic TODO functionality
Any headline can become a TODO item by starting it with the word TODO,
--- 520,530 ----
@menu
* TODO basics:: Marking and displaying TODO entries
* TODO extensions:: Workflow and assignments
+ * Priorities:: Some things are more important than others
@end menu
! @node TODO basics, TODO extensions, TODO items, TODO items
@section Basic TODO functionality
Any headline can become a TODO item by starting it with the word TODO,
***************
*** 538,586 ****
,-> (unmarked) -> TODO -> DONE --.
'--------------------------------'
@end example
@kindex C-c C-v
@cindex sparse tree, for TODO
@item C-c C-v
View TODO items in a @emph{sparse tree} (@pxref{Sparse trees}). Folds
the entire buffer, but shows all TODO items and the headings hierarchy
above them. With prefix arg, show also the DONE entries.
@end table
! @node Priorities, TODO extensions, TODO basics, TODO items
! @section Priorities
! @cindex priorities
!
! If you use Org-mode extensively to organize your work, you may end up
! with a number of TODO entries so large that you'd like to prioritize
! them. You can do this by placing a @emph{priority cookie} into the
! headline, like this
!
! @example
! *** TODO [#A] Write letter to Sam Fortune
! @end example
!
! @noindent
! With its standard setup, Org-mode supports priorities @samp{A},
! @samp{B}, and @samp{C}. @samp{A} is the highest priority. An entry
! without a cookie is treated as priority @samp{B}. Priorities make a
! difference only in the multi-file agenda (@pxref{Agenda (multiple files)}).
!
! @table @kbd
! @kindex @kbd{C-c ,}
! @item @kbd{C-c ,}
! Set the priority of the current item. The command prompts for a
! priority character @samp{A}, @samp{B} or @samp{C}. When you press
! @key{SPC} instead, the priority cookie is removed from the headline.
! @kindex address@hidden
! @kindex address@hidden
! @item address@hidden
! @itemx address@hidden
! Increase/decrease priority of current item. Note that these keys are
! also used to modify time stamps (@pxref{Creating timestamps}).
! @end table
!
!
! @node TODO extensions, , Priorities, TODO items
@section Extended use of TODO keywords
@cindex extended TODO keywords
--- 545,564 ----
,-> (unmarked) -> TODO -> DONE --.
'--------------------------------'
@end example
+ The same rotation can also be done ``remotely'' from the timeline and
+ agenda buffers with the @kbd{t} command key (@pxref{Agenda commands}).
@kindex C-c C-v
@cindex sparse tree, for TODO
@item C-c C-v
View TODO items in a @emph{sparse tree} (@pxref{Sparse trees}). Folds
the entire buffer, but shows all TODO items and the headings hierarchy
above them. With prefix arg, show also the DONE entries.
+ @item C-u C-c a
+ A @kbd{C-u} argument to the @code{org-agenda command} (@pxref{Agenda})
+ collects all unfinished TODO items into a single place.
@end table
! @node TODO extensions, Priorities, TODO basics, TODO items
@section Extended use of TODO keywords
@cindex extended TODO keywords
***************
*** 624,632 ****
@cindex types as TODO keywords
The second possibility is to use TODO keywords to indicate different
! types of action items. For example, when you work with several people
! on a single project, you might want to assign action items to
! persons.
@lisp
(setq org-todo-keywords '("Fred" "Sara" "Lucy" "Mike" "DONE")
--- 602,612 ----
@cindex types as TODO keywords
The second possibility is to use TODO keywords to indicate different
! types of action items. For example, you might want to indicate that
! items are for ``work'' or ``home''. Or, when you work with several
! people on a single project, you might want to assign action items
! directly to persons, by using their names as TODO keywords. This
! would be set up like this:
@lisp
(setq org-todo-keywords '("Fred" "Sara" "Lucy" "Mike" "DONE")
***************
*** 634,645 ****
@end lisp
In this case, different keywords do not indicate a sequence, but
! rather different types. This changes the behavior of the command
! @kbd{C-c C-t} slightly. When used several times in succession, it
! will still cycle through all names. But when when you return to the
! item after some time and execute @kbd{C-c C-t} again, it will switch
! from each name directly to DONE. Use prefix arguments or completion
! to quickly select a specific name.
@node Per file keywords, , TODO types, TODO extensions
@subsection Setting up TODO keywords for individual files
--- 614,628 ----
@end lisp
In this case, different keywords do not indicate a sequence, but
! rather different types. So it is normally not useful to change from
! one type to another. Therefore, in this case the the behavior of the
! command @kbd{C-c C-t} is changed address@hidden is also true
! for the @kbd{t} command in the timeline and agenda buffers}. When
! used several times in succession, it will still cycle through all
! names. But when when you return to the item after some time and
! execute @kbd{C-c C-t} again, it will switch from each name directly to
! DONE. Use prefix arguments or completion to quickly select a specific
! name.
@node Per file keywords, , TODO types, TODO extensions
@subsection Setting up TODO keywords for individual files
***************
*** 647,657 ****
@cindex per file keywords
It can be very useful to use different aspects of the TODO mechanism
! in different files. For this you need to add special lines to the
! file which set the keywords and interpretation for that file only.
! For example, to set one of the two examples discussed above, you
! need one of the following lines, starting in column zero anywhere in
! the file:
@example
#+SEQ_TODO: TODO FEEDBACK VERIFY DONE
--- 630,641 ----
@cindex per file keywords
It can be very useful to use different aspects of the TODO mechanism
! in different files, which is not possible with the global settings
! described above. For file-local settings, you need to add special
! lines to the file which set the keywords and interpretation for that
! file only. For example, to set one of the two examples discussed
! above, you need one of the following lines, starting in column zero
! anywhere in the file:
@example
#+SEQ_TODO: TODO FEEDBACK VERIFY DONE
***************
*** 664,674 ****
@samp{#+} into the buffer and then use @address@hidden completion.
@cindex DONE, final TODO keyword
! Remember that the last keyword must always mean that the
! item is DONE (you may use a different word, though). After changing
! these lines, use @kbd{M-x normal-mode} to make the changes known to
! Org-mode. Also note that in each file, only one of the two aspects
! of TODO keywords can be used.
If you want to use very many keywords, for example when working with a
large group of people, you may split the names over several lines:
--- 648,662 ----
@samp{#+} into the buffer and then use @address@hidden completion.
@cindex DONE, final TODO keyword
! Remember that the last keyword must always mean that the item is DONE
! (you may use a different word, though). Also note that in each file,
! only one of the two aspects of TODO keywords can be used. After
! changing one of these lines, use @kbd{C-c C-c} with the cursor still
! in the line to make the changes known to address@hidden
! parses these lines only when Org-mode is activated after visiting a
! file. @kbd{C-c C-c} with the cursor in a line starting with @samp{#-}
! is simply restarting Org-mode, making sure that these changes will be
! respected.}.
If you want to use very many keywords, for example when working with a
large group of people, you may split the names over several lines:
***************
*** 680,685 ****
--- 668,710 ----
#+TYP_TODO: DONE
@end example
+ @node Priorities, , TODO extensions, TODO items
+ @section Priorities
+ @cindex priorities
+
+ If you use Org-mode extensively to organize your work, you may end up
+ with a number of TODO entries so large that you'd like to prioritize
+ them. This can be done by placing a @emph{priority cookie} into the
+ headline, like this
+
+ @example
+ *** TODO [#A] Write letter to Sam Fortune
+ @end example
+
+ @noindent
+ With its standard setup, Org-mode supports priorities @samp{A},
+ @samp{B}, and @samp{C}. @samp{A} is the highest priority. An entry
+ without a cookie is treated as priority @samp{B}. Priorities make a
+ difference only in the agenda (@pxref{Agenda}).
+
+ @table @kbd
+ @kindex @kbd{C-c ,}
+ @item @kbd{C-c ,}
+ Set the priority of the current item. The command prompts for a
+ priority character @samp{A}, @samp{B} or @samp{C}. When you press
+ @key{SPC} instead, the priority cookie is removed from the headline.
+ The priorities can also be changed ``remotely'' from the timeline and
+ agenda buffer with the @kbd{,} command (@pxref{Agenda commands}).
+
+ @kindex address@hidden
+ @kindex address@hidden
+ @item address@hidden
+ @itemx address@hidden
+ Increase/decrease priority of current item. Note that these keys are
+ also used to modify time stamps (@pxref{Creating timestamps}).
+ @end table
+
+
@node Tables, Hyperlinks, TODO items, Top
@chapter Tables
@cindex tables
***************
*** 995,1001 ****
current article/entry. For W3 and W3M buffer, the link goes to the
current URL. For any other files, the link will just point to the file.
The key binding @kbd{C-c l} is only a suggestion - see
! @ref{Installation}.
@kindex C-c C-l
@item C-c C-l
--- 1020,1026 ----
current article/entry. For W3 and W3M buffer, the link goes to the
current URL. For any other files, the link will just point to the file.
The key binding @kbd{C-c l} is only a suggestion - see
! @ref{Installation and Activation}.
@kindex C-c C-l
@item C-c C-l
***************
*** 1048,1054 ****
following customization will tell @emph{Remember} to use org files as
target, and to create annotations compatible with Org-mode links.
-
@c FIXME: The autoload will not be necessary when Org-mode is part of Emacs
@example
(autoload 'org-remember-annotation "org")
--- 1073,1078 ----
***************
*** 1113,1119 ****
special format, either @samp{<2003-09-16 Tue>} or @samp{<2003-09-16
Tue 09:39>}. A time stamp can appear anywhere in the headline or body
of an org-tree entry. Its presence allows to show entries on specific
! dates in the agenda (@pxref{Agenda (multiple files)}). We distinguish:
@table @var
@cindex timestamp
--- 1137,1143 ----
special format, either @samp{<2003-09-16 Tue>} or @samp{<2003-09-16
Tue 09:39>}. A time stamp can appear anywhere in the headline or body
of an org-tree entry. Its presence allows to show entries on specific
! dates in the agenda (@pxref{Agenda}). We distinguish:
@table @var
@cindex timestamp
***************
*** 1192,1198 ****
@kindex C-c C-o
@item C-c C-o
Access the agenda for the date given by the time stamp at point
! (@pxref{Agenda (multiple files)}).
@kindex C-c C-d
@item C-c C-d
--- 1216,1222 ----
@kindex C-c C-o
@item C-c C-o
Access the agenda for the date given by the time stamp at point
! (@pxref{Agenda}).
@kindex C-c C-d
@item C-c C-d
***************
*** 1303,1315 ****
appointments.
@menu
! * Timeline (single file):: Time-sorted view for single file
! * Agenda (multiple files):: Your weekly planner
* Agenda commands:: Remote editing of org trees
* Calendar/Diary integration:: Integrating Anniversaries and more
@end menu
! @node Timeline (single file), Agenda (multiple files), Timeline and Agenda,
Timeline and Agenda
@section Timeline for a single file
@cindex single file summary
@cindex agenda, for single file
--- 1327,1339 ----
appointments.
@menu
! * Timeline:: Time-sorted view for single file
! * Agenda:: Your weekly planner
* Agenda commands:: Remote editing of org trees
* Calendar/Diary integration:: Integrating Anniversaries and more
@end menu
! @node Timeline, Agenda, Timeline and Agenda, Timeline and Agenda
@section Timeline for a single file
@cindex single file summary
@cindex agenda, for single file
***************
*** 1335,1343 ****
commands available in the Agenda buffer are listed in @ref{Agenda
commands}.
! @node Agenda (multiple files), Agenda commands, Timeline (single file),
Timeline and Agenda
! @section Agenda from multiple files
! @cindex agenda, from multiple files
An agenda can be compiled from one or more org files. The main
purpose of this command is to act like a planner, in order to show you
--- 1359,1367 ----
commands available in the Agenda buffer are listed in @ref{Agenda
commands}.
! @node Agenda, Agenda commands, Timeline, Timeline and Agenda
! @section Agenda
! @cindex agenda
An agenda can be compiled from one or more org files. The main
purpose of this command is to act like a planner, in order to show you
***************
*** 1374,1380 ****
unfinished TODO items (also those without a date) are also listed at
the beginning of the buffer, before the first address@hidden
The key binding @kbd{C-c a} is only a suggestion - see
! @ref{Installation}.
@end table
The commands available in the Agenda buffer are listed in
--- 1398,1404 ----
unfinished TODO items (also those without a date) are also listed at
the beginning of the buffer, before the first address@hidden
The key binding @kbd{C-c a} is only a suggestion - see
! @ref{Installation and Activation}.
@end table
The commands available in the Agenda buffer are listed in
***************
*** 1384,1407 ****
@cindex category
In the agenda buffer, each entry is preceded by a @emph{category},
! which is derived from the file name. You can also set the category of
! a file through file variables, for example by making the first line of
! the file look like this:
!
! @cindex file variables
! @example
! Planet Finder -*- mode: org; org-category: Cheops -*-
! @end example
! @noindent
! Or, like with TODO keywords (@pxref{Per file keywords}), you can
! insert a special line anywhere in the file:
!
@example
#+CATEGORY: Cheops
@end example
@noindent
! The display looks best if the category is no longer than 10 characters.
@subsection Sorting of agenda items
@cindex sorting, of agenda items
--- 1408,1425 ----
@cindex category
In the agenda buffer, each entry is preceded by a @emph{category},
! which is derived from the file name. The category can also be set
! with a special line anywhere in the buffer, looking like this:
@example
#+CATEGORY: Cheops
@end example
@noindent
! After changing this line, press @kbd{C-c C-c} with the cursor still in
! the line, to make the changes know to org-mode. Otherwise, the change
! will only be active the next time you visit this file with Emacs.
+ The display in the agenda buffer looks best if the category is no
+ longer than 10 characters.
@subsection Sorting of agenda items
@cindex sorting, of agenda items
***************
*** 1427,1433 ****
Sorting can be customized using the variable
@code{org-agenda-sorting-strategy}.
! @node Agenda commands, Calendar/Diary integration, Agenda (multiple files),
Timeline and Agenda
@section Commands in the agenda buffer
Entries in the agenda buffer are linked back to the org file or diary
--- 1445,1451 ----
Sorting can be customized using the variable
@code{org-agenda-sorting-strategy}.
! @node Agenda commands, Calendar/Diary integration, Agenda, Timeline and Agenda
@section Commands in the agenda buffer
Entries in the agenda buffer are linked back to the org file or diary
***************
*** 1443,1448 ****
--- 1461,1473 ----
exceptions are marked.
@table @kbd
+ @tsubheading{Motion}
+ @kindex n
+ @item n
+ Next line (same as @key{up}).
+ @kindex p
+ @item p
+ Previous line (same as @key{down}).
@tsubheading{View/GoTo org file}
@kindex mouse-3
@kindex @key{SPC}
***************
*** 1470,1476 ****
the agenda buffer, the other window always shows the corresponding
location in the org file.
-
@tsubheading{Change display}
@kindex o
@item o
--- 1495,1500 ----
***************
*** 1515,1522 ****
Change the TODO state of the item, both in the agenda and in the
original org file.
! @kindex p
! @item p
Set the priority for the current item. Org-mode prompts for the
priority character. If you reply with @key{SPC}, the priority cookie
is removed from the entry.
--- 1539,1546 ----
Change the TODO state of the item, both in the agenda and in the
original org file.
! @kindex ,
! @item ,
Set the priority for the current item. Org-mode prompts for the
priority character. If you reply with @key{SPC}, the priority cookie
is removed from the entry.
***************
*** 1526,1538 ****
--- 1550,1566 ----
Display weighted priority of current item.
@kindex +
+ @kindex address@hidden
@item +
+ @item address@hidden
Increase the priority of the current item. The priority is changed in
the original buffer, but the agenda is not resorted. Use the @kbd{r}
key for this.
@kindex -
+ @kindex address@hidden
@item -
+ @item address@hidden
Decrease the priority of the current item.
@kindex address@hidden
***************
*** 1568,1577 ****
@item c
Open the Emacs calendar and move to the date at the agenda cursor.
! @kindex C
! @item C
! Convert the date at cursor into many other cultural and historic
! calendars.
@kindex M
@item M
--- 1596,1604 ----
@item c
Open the Emacs calendar and move to the date at the agenda cursor.
! @item c
! When in the calendar, compute and show the Org-mode agenda for the
! date at the cursor.
@kindex M
@item M
***************
*** 1579,1586 ****
@kindex S
@item S
! Show sunrise and sunset times. The location must be set with calendar
! variables, see documentation of the Emacs calendar.
@kindex H
@item H
--- 1606,1618 ----
@kindex S
@item S
! Show sunrise and sunset times. The geographical location must be set
! with calendar variables, see documentation of the Emacs calendar.
!
! @kindex C
! @item C
! Convert the date at cursor into many other cultural and historic
! calendars.
@kindex H
@item H
***************
*** 1643,1649 ****
command to insert new entries for the current date works in the agenda
buffer, as well as the commands @kbd{S}, @kbd{M}, and @kbd{C} to
display Sunrise/Sunset times, show lunar phases and to convert to
! other calendars, respectively.
@node Agenda to diary, , Diary to agenda, Calendar/Diary integration
@subsection Including the agenda into the diary
--- 1675,1682 ----
command to insert new entries for the current date works in the agenda
buffer, as well as the commands @kbd{S}, @kbd{M}, and @kbd{C} to
display Sunrise/Sunset times, show lunar phases and to convert to
! other calendars, respectively. @kbd{c} can be used to switch back and
! forth between calendar and agenda.
@node Agenda to diary, , Diary to agenda, Calendar/Diary integration
@subsection Including the agenda into the diary
***************
*** 1651,1658 ****
If you prefer to use the Emacs diary as your main instrument and if
you wish to include the Org-mode agenda into it, the following steps
are necessary: Autoload the function @command{org-diary} as shown
! above under @ref{Installation}. You also need to use @emph{fancy
! diary display} by setting in @file{.emacs}:
@lisp
(add-hook 'diary-display-hook 'fancy-diary-display)
--- 1684,1691 ----
If you prefer to use the Emacs diary as your main instrument and if
you wish to include the Org-mode agenda into it, the following steps
are necessary: Autoload the function @command{org-diary} as shown
! above under @ref{Installation and Activation}. You also need to use
! @emph{fancy diary display} by setting in @file{.emacs}:
@lisp
(add-hook 'diary-display-hook 'fancy-diary-display)
***************
*** 2038,2048 ****
Org mode cooperates with table.el, see @ref{table.el}.
@end table
- @c EmacsWiki
- @c organizer-mode
- @c todo-mode
- @c records mode
-
@page @c FIXME
@node Acknowledgments, Bugs, Interaction, Miscellaneous
--- 2071,2076 ----
***************
*** 2068,2076 ****
Christian Egli converted the documentation into TeXInfo format. He
also showed me his plans for a multifile summary for Org-mode. Some of
his ideas have found their way into the agenda.
! @item
! Philip Rooke created the Org-mode reference card and did some
! beta-testing.
@item
Linking to VM/BBDB/GNUS was inspired by Tom Shannon's
@file{organizer-mode.el}.
--- 2096,2104 ----
Christian Egli converted the documentation into TeXInfo format. He
also showed me his plans for a multifile summary for Org-mode. Some of
his ideas have found their way into the agenda.
! @item
! Philip Rooke created the Org-mode reference card. He also helped with
! beta testing and contributed a number of very useful ideas.
@item
Linking to VM/BBDB/GNUS was inspired by Tom Shannon's
@file{organizer-mode.el}.
***************
*** 2102,2109 ****
Under XEmacs, if Org-mode entries are included into the diary, it is
not possible to jump back from the diary to the org file. Apparently,
the text properties are lost when the fancy-diary-display is used.
! However, from Org-mode's agenda (created with @kbd{C-c C-r} or
! @kbd{M-x org-agenda}), things do work correctly.
@item
Linux should also have a default viewer application, using mailcap.
Maybe we can use GNUS or VM mime code? Or dired's guessing commands?
--- 2130,2137 ----
Under XEmacs, if Org-mode entries are included into the diary, it is
not possible to jump back from the diary to the org file. Apparently,
the text properties are lost when the fancy-diary-display is used.
! However, from Org-mode's timeline and agenda buffers (created with
! @kbd{C-c C-r} and @kbd{C-c a}), things do work correctly.
@item
Linux should also have a default viewer application, using mailcap.
Maybe we can use GNUS or VM mime code? Or dired's guessing commands?
***************
*** 2126,2132 ****
@bye
-
@ignore
arch-tag: 7893d1fe-cc57-4d13-b5e5-f494a1bcc7ac
@end ignore
--- 2154,2159 ----
- [Emacs-diffs] Changes to emacs/man/org.texi,
Carsten Dominik <=