[Orgmode] Org mode release 6.04
Hi, I am releasing Org 6.04, at http://orgmode.org Enjoy! - Carsten Changes in version 6.04 ~~~ Overview - Statistics cookies [/] and [%] for TODO entries - Editing source code example in the proper mode - iCalendar now defines proper UIDs for entries - New properties for customizing subtree export Incompatible changes - The default of the variable `org-tags-match-list-sublevels' is now `t'. The main reason for this is that it is easier to explain in the manual and will lead to fewer surprises. - The former CONTRIB directory is now called contrib. This was already the case in the git distribution, but the tar and zip archives still did this wrong. Details === Statistics for TODO entries --- The [/] and [%] cookies have already provided statistics for checkboxes. Now they do the same also for TODO entries. If a headline contains either cookie, changing the TODO state of any direct child will trigger an update of this cookie. Children that are neither TODO nor DONE are ignored. There have already been requests to automatically switch the parent headline to DONE when all children are done. I am not making this a default feature, because one needs to make many decisions about which keyword to use, etc. Instead of a complex customization variable, I am providing a hook that can be used. This hook will be called each time a TODO statistics cookie is updated, with the cursor in the corresponding line. Each function in the hook will receive two arguments, the number of done entries, and the number of not-done entries, and you can use the hook to change the state of the headline. Here is an example implementation: (defun org-summary-todo (n-done n-not-done) Switch entry to DONE when all sub-entries are done, to TODO otherwise. (let (org-log-done org-log-states) ; turn off logging (org-todo (if (= n-not-done 0) DONE TODO (add-hook 'org-after-todo-statistics-hook 'org-summary-todo) Editing source code example in the proper mode -- If you are writing a document with source code examples, you can include these examples into a `#+BEGIN_SRC lang ... #+END_SRC' or (with the org-mtags module loaded) a `src...' structure. `lang' stands for the Emacs mode used for editing the language, this could be `emacs-lisp' for Emacs Lisp mode examples, or `org' for Org mode examples. You can now use the key C-c ' (that is C-c followed by the single quote) to edit the example in its native mode. This works by creating an indirect buffer, narrowing it to the example and setting the appropriate mode. You need to exit editing by killing that indirect buffer, with `C-x k'. This is important, because lines that have syntactic meaning in Org will be quoted when the indirect buffer is killed. I guess it would be nice to exit with `C-c C-c', but who knows what this key is supposed to do in a random mode. iCalendar now defines proper UIDs for entries - This is necessary for synchronization services. The UIDs are created using the the org-id.el module which is now part of the Or core. If you set the variable (setq org-icalendar-store-UID t) then all created UIDs will be stored in the entry as an `:ID:' property. This is off by default because it creates lots of property drawers even if you only play with iCalendar export. But if you plan to use synchronization, you really need to turn this on. Diary sexp entries do not yet receive proper persistent UIDs, because they are transformed to iCalendar format by icalendar.el which creates fresh UIDs each time, based on the current time. An interesting aspect of Org is that a single outline node can give rise to multiple iCalendar entries (as a timestamp, a deadline, a scheduled item, and as a TODO item). Therefore, Org adds prefixes TS-, DL- CS-, and TD- to the UID during iCalendar export, depending on what triggered the inclusion of the entry. In this way the UID remains unique, but a synchronization program can still figure out from which entry all the different instances originate. New properties for customizing subtree export. -- When exporting a subtree by selecting it before calling the export command, you can now use the properties `EXPORT_TITLE', `EXPORT_TEXT', and `EXPORT_OPTIONS' to overrule the global `#+TITLE', `#+TEXT', and `#+OPTIONS' settings. You can also set an export file name with `EXPORT_FILE_NAME' that will overrule the file name derived from the buffer's file name. As far as the options are concerned, the global `#+OPTIONS' will still be read, and only the options you give in the property will be overwritten. For example: #+OPTIONS: skip:nil * Computer Tricks :PROPERTIES: :EXPORT_FILE_NAME: ct.html :EXPORT_TITLE: Steve's collected computer tricks :EXPORT_OPTIONS: h:2
[Orgmode] Re: Org mode release 6.04
On Sun, May 25 2008, Carsten Dominik wrote: Editing source code example in the proper mode -- If you are writing a document with source code examples, you can include these examples into a `#+BEGIN_SRC lang ... #+END_SRC' or (with the org-mtags module loaded) a `src...' structure. `lang' stands for the Emacs mode used for editing the language, this could be `emacs-lisp' for Emacs Lisp mode examples, or `org' for Org mode examples. You can now use the key C-c ' (that is C-c followed by the single quote) to edit the example in its native mode. This works by creating an indirect buffer, narrowing it to the example and setting the appropriate mode. You need to exit editing by killing that indirect buffer, with `C-x k'. This is important, because lines that have syntactic meaning in Org will be quoted when the indirect buffer is killed. Carsten-- This is a phenomenally exciting addition. Combining this with the htmlized code examples in html export, and the option for \LaTeX export, org has clearly just vaulted past the rest of the field for literate programming. Expect a tutorial from me in the next few weeks about using org with RWeave (the R variant of SWeave). This will be a fantastic way to write articles that include statistical analyses and figures. That said, don't be surprised if by opening this door you end up with some new feature requests from me :) One addition that I can already see being interested in is the evaluation of embedded code before export, so that the results of the code are included along with the source. Obviously, there are security issues here that will need to be thought about, but I'd like to see if we could make this work. Greedy feature requests aside, this is very, very cool. I guess it would be nice to exit with `C-c C-c', but who knows what this key is supposed to do in a random mode. I can tell you now that C-c C-c is almost as overloaded in R-mode (from the package ESS) as it is in org-mode, and I will want it to have its R-mode interpretation while I edit R code. While I'm writing, I'll try to keep an eye out for sensible ways of jumping out of coding mode and back to org-mode. Thanks for this release! /au -- Austin Frank http://aufrank.net GPG Public Key (D7398C2F): http://aufrank.net/personal.asc pgpifd0UQAibq.pgp Description: PGP signature ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: Org mode release 6.04
On 2008-05-25 08:31 +0100, Carsten Dominik wrote: iCalendar now defines proper UIDs for entries - This is necessary for synchronization services. The UIDs are created using the the org-id.el module which is now part of the Or core. If you set the variable (setq org-icalendar-store-UID t) then all created UIDs will be stored in the entry as an `:ID:' property. This is off by default because it creates lots of property drawers even if you only play with iCalendar export. But if you plan to use synchronization, you really need to turn this on. Nice to see advance in this front. I wonder whether it is possible to do a direct synchronisation with google calendar using json.el. That would be very interesting. -- .: Leo :. [ sdl.web AT gmail.com ] .: [ GPG Key: 9283AA3F ] :. Use the better alternative -- http://www.openoffice.org/ ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: Emacs-orgmode Digest, Vol 27, Issue 47
On Sun, May 25, 2008 at 10:00 AM, [EMAIL PROTECTED] wrote: Editing source code example in the proper mode -- If you are writing a document with source code examples, you can include these examples into a `#+BEGIN_SRC lang ... #+END_SRC' or (with the org-mtags module loaded) a `src...' structure. `lang' stands for the Emacs mode used for editing the language, this could be `emacs-lisp' for Emacs Lisp mode examples, or `org' for Org mode examples. You can now use the key C-c ' (that is C-c followed by the single quote) to edit the example in its native mode. This works by creating an indirect buffer, narrowing it to the example and setting the appropriate mode. You need to exit editing by killing that indirect buffer, with `C-x k'. This is important, because lines that have syntactic meaning in Org will be quoted when the indirect buffer is killed. I guess it would be nice to exit with `C-c C-c', but who knows what this key is supposed to do in a random mode. iCalendar now defines proper UIDs for entries - This is necessary for synchronization services. The UIDs are created using the the org-id.el module which is now part of the Or core. If you set the variable (setq org-icalendar-store-UID t) then all created UIDs will be stored in the entry as an `:ID:' property. This is off by default because it creates lots of property drawers even if you only play with iCalendar export. But if you plan to use synchronization, you really need to turn this on. Diary sexp entries do not yet receive proper persistent UIDs, because they are transformed to iCalendar format by icalendar.el which creates fresh UIDs each time, based on the current time. An interesting aspect of Org is that a single outline node can give rise to multiple iCalendar entries (as a timestamp, a deadline, a scheduled item, and as a TODO item). Therefore, Org adds prefixes TS-, DL- CS-, and TD- to the UID during iCalendar export, depending on what triggered the inclusion of the entry. In this way the UID remains unique, but a synchronization program can still figure out from which entry all the different instances originate. New properties for customizing subtree export. -- When exporting a subtree by selecting it before calling the export command, you can now use the properties `EXPORT_TITLE', `EXPORT_TEXT', and `EXPORT_OPTIONS' to overrule the global `#+TITLE', `#+TEXT', and `#+OPTIONS' settings. You can also set an export file name with `EXPORT_FILE_NAME' that will overrule the file name derived from the buffer's file name. As far as the options are concerned, the global `#+OPTIONS' will still be read, and only the options you give in the property will be overwritten. For example: #+OPTIONS: skip:nil * Computer Tricks :PROPERTIES: :EXPORT_FILE_NAME: ct.html :EXPORT_TITLE: Steve's collected computer tricks :EXPORT_OPTIONS: h:2 toc:nil :END: -- Message: 4 Date: Sun, 25 May 2008 08:41:54 -0400 From: Austin Frank [EMAIL PROTECTED] Subject: [Orgmode] Re: Org mode release 6.04 To: emacs-orgmode@gnu.org Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=us-ascii On Sun, May 25 2008, Carsten Dominik wrote: This is a phenomenally exciting addition. Combining this with the htmlized code examples in html export, and the option for \LaTeX export, org has clearly just vaulted past the rest of the field for literate programming. +1 Austin, could you point us to the tools you plan to use for code weaving? -- Non est ad astra mollis e terris via. ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: Emacs-orgmode Digest, Vol 27, Issue 47
Okay, got one little problem report here: Loading org...done Problems while trying to load feature `org-id' Loading disp-table...done Loading edmacro...done Loading footnote...done Loading vc-svn...done Loading vc...done Loading cl-seq...done Let me just mention that if the Problems report gave some clue as to what the problem was, it would be easier to help debug it. But in any case, this I do't think is a feature I'm using yet. Charlie ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: Integration of Org mode with Mairix: org-mairix.el
Dan Davison [EMAIL PROTECTED] writes: user-base first. Is there anyone other than myself and Austin currently reading the list who uses org-mairix.el, or who might be interested in using it? Yes, I am interested too. Cezar ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: Integration of Org mode with Mairix: org-mairix.el
Cezar == Cezar Halmagean [EMAIL PROTECTED] writes: Cezar Dan Davison [EMAIL PROTECTED] writes: user-base first. Is there anyone other than myself and Austin currently reading the list who uses org-mairix.el, or who might be interested in using it? I'm one user... Sincerely, Gour -- Gour | Zagreb, Croatia | GPG key: C6E7162D pgpAPXZcSOJUe.pgp Description: PGP signature ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] can't get source code editing working
On Sun, May 25, 2008 at 10:25:22AM -0600, Charles Martin wrote: On Sun, May 25, 2008 at 10:00 AM, [EMAIL PROTECTED] wrote: Editing source code example in the proper mode -- If you are writing a document with source code examples, you can include these examples into a `#+BEGIN_SRC lang ... #+END_SRC' or (with the org-mtags module loaded) a `src...' structure. `lang' stands for the Emacs mode used for editing the language, this could be `emacs-lisp' for Emacs Lisp mode examples, or `org' for Org mode examples. You can now use the key C-c ' (that is C-c followed by the single quote) to edit the example in its native mode. This works by creating an indirect buffer, narrowing it to the example and setting the appropriate mode. You need to exit editing by killing that indirect buffer, with `C-x k'. This is important, because lines that have syntactic meaning in Org will be quoted when the indirect buffer is killed. ... Message: 4 Date: Sun, 25 May 2008 08:41:54 -0400 From: Austin Frank [EMAIL PROTECTED] Subject: [Orgmode] Re: Org mode release 6.04 To: emacs-orgmode@gnu.org Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=us-ascii On Sun, May 25 2008, Carsten Dominik wrote: This is a phenomenally exciting addition. Combining this with the htmlized code examples in html export, and the option for \LaTeX export, org has clearly just vaulted past the rest of the field for literate programming. I agree, this sounds great. I was just about to start trying to combine org and latex usage in any case. However I'm being dense. I've done git pull make make install, and I have org-version equal to 6.04b. OK so far, right? Now I create an org file containing * section 1 #+BEGIN_SRC latex \log p(z|x,\theta) #+END_SRC * section 2 #+BEGIN_SRC r xor - function(a,b) (a | b) !(a b) #+END_SRC * section 3 #+BEGIN_SRC emacs-lisp (defun org-xor (a b) Exclusive or. (if a (not b) b)) #+END_SRC but despite repeated invocations of /C-c '/ and org-edit-special and org-edit-src-example, with point in various places, I haven't brought up a narrowed buffer in the requested mode. Instead I get C-c ' can do nothing useful here. (from C-c ' and org-edit-special) and silence from org-edit-src-example I'm sure I'm being stupid, could someone tell me how? I'm also a heavy R user, so I liked Austin's suggestion of combining org with Sweave / Rnw files and look forward to further developments. I might have a go myself if I can get beyond step 1 here. Sweave/Rnw files can get really ugly and cumbersome and merely org-style outlining and folding would be excellent, though I bet it can go much further than that. Austin -- it would be well worth CC'ing any developments on that front to the ESS (Emacs Speaks Statistics) mailing list. Austin, could you point us to the tools you plan to use for code weaving? See http://www.r-project.org and http://www.statistik.lmu.de/~leisch/Sweave/. Sweave() is an R function that processes an R/noweb file containing a mixture of R and latex, evaluating the R code and inlining any resulting textual or graphical output into the latex output. Dan -- Non est ad astra mollis e terris via. ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: Org mode release 6.04
On Sun, 25 May 2008 08:41:54 -0400 Austin Frank [EMAIL PROTECTED] wrote: On Sun, May 25 2008, Carsten Dominik wrote: Editing source code example in the proper mode -- If you are writing a document with source code examples, you can include these examples into a `#+BEGIN_SRC lang ... #+END_SRC' or (with the org-mtags module loaded) a `src...' structure. `lang' stands for the Emacs mode used for editing the language, this could be `emacs-lisp' for Emacs Lisp mode examples, or `org' for Org mode examples. You can now use the key C-c ' (that is C-c followed by the single quote) to edit the example in its native mode. This works by creating an indirect buffer, narrowing it to the example and setting the appropriate mode. You need to exit editing by killing that indirect buffer, with `C-x k'. This is important, because lines that have syntactic meaning in Org will be quoted when the indirect buffer is killed. Carsten-- This is a phenomenally exciting addition. Combining this with the htmlized code examples in html export, and the option for \LaTeX export, org has clearly just vaulted past the rest of the field for literate programming. Expect a tutorial from me in the next few weeks about using org with RWeave (the R variant of SWeave). This will be a fantastic way to write articles that include statistical analyses and figures. That said, don't be surprised if by opening this door you end up with some new feature requests from me :) One addition that I can already see being interested in is the evaluation of embedded code before export, so that the results of the code are included along with the source. Obviously, there are security issues here that will need to be thought about, but I'd like to see if we could make this work. Greedy feature requests aside, this is very, very cool. I guess it would be nice to exit with `C-c C-c', but who knows what this key is supposed to do in a random mode. I can tell you now that C-c C-c is almost as overloaded in R-mode (from the package ESS) as it is in org-mode, and I will want it to have its R-mode interpretation while I edit R code. While I'm writing, I'll try to keep an eye out for sensible ways of jumping out of coding mode and back to org-mode. Thanks for this release! /au -- Jabber: [EMAIL PROTECTED] ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] can't get source code editing working
On May 25, 2008, at 10:04 PM, Dan Davison wrote: I agree, this sounds great. I was just about to start trying to combine org and latex usage in any case. However I'm being dense. I've done git pull make make install, and I have org-version equal to 6.04b. OK so far, right? Now I create an org file containing * section 1 #+BEGIN_SRC latex \log p(z|x,\theta) #+END_SRC * section 2 #+BEGIN_SRC r xor - function(a,b) (a | b) !(a b) #+END_SRC * section 3 #+BEGIN_SRC emacs-lisp (defun org-xor (a b) Exclusive or. (if a (not b) b)) #+END_SRC but despite repeated invocations of /C-c '/ and org-edit-special and org-edit-src-example, with point in various places, I haven't brought up a narrowed buffer in the requested mode. Instead I get C-c ' can do nothing useful here. (from C-c ' and org-edit-special) and silence from org-edit-src-example The #+begin and #+end lines must start in column 0, you have whitespace in front of them. If you load the org-mtags.el module, you can also use a Muse-like syntax: src lang=latex /src these may be indented. HTH - Carsten ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] new functionality for org-publish.el
Dear Carsten, I send a few more patches for org-publish.el (against 6.04b/git): - I saw that the include-list functionality, which I find very useful, was not implemented. I think this does what you want (at least it works for me: 451a452,456 (mapc (lambda (f) (pushnew (expand-file-name (concat base-dir f)) org-publish-temp-files)) include-list) - In the web index generated automatically for a project the name of the files are used as descriptors in the index. It seems nicer to use the actual title in the file if available. This works for me: 600c609,613 (let ((fn (file-name-nondirectory file))) --- (let ((fn ;; (file-name-nondirectory file) (substring (expand-file-name file) (length (expand-file-name dir))) )) 604c617 (file-name-sans-extension fn) --- (org-publish-find-title (concat dir fn)) 608a622,634 (defun org-publish-find-title (file) Find the title of file in project. (save-excursion (set-buffer (find-file-noselect file)) (let* ((opt-plist (org-combine-plists (org-default-export-plist) (org-infile-export-plist (or (plist-get opt-plist :title) (and (not (plist-get opt-plist :skip-before-1st-heading)) (org-export-grab-title-from-buffer)) (file-name-sans-extension file) - Finally, I find it useful to have a completion-function in addition to a preparation-function. I use it for, e.g., changing the permissions of the generated files in the remote site. It can be done for each individual file by adding it to the :publishing-function list, but it looked more tedious to program and would be slower when publising remotely. 571a577,578 (completion-function (plist-get project-plist :completion-function)) 576c583,585 (org-publish-file file project --- (org-publish-file file project)) (when completion-function (funcall completion-function)) )) I also send at the end of the message the patched version of org-publish.el for sanity check. Cheers, Manuel P.S. I have not used git extensively, but if you prefer me to send you the patches using git I can give it a try next time. ;;; org-publish.el --- publish related org-mode files as a website ;; Copyright (C) 2006, 2007, 2008 Free Software Foundation, Inc. ;; Author: David O'Toole [EMAIL PROTECTED] ;; Maintainer: Bastien Guerry bzg AT altern DOT org ;; Keywords: hypermedia, outlines, wp ;; Version: 6.04b ;; This file is part of GNU Emacs. ;; ;; GNU Emacs is free software: you can redistribute it and/or modify ;; it under the terms of the GNU General Public License as published by ;; the Free Software Foundation, either version 3 of the License, or ;; (at your option) any later version. ;; GNU Emacs is distributed in the hope that it will be useful, ;; but WITHOUT ANY WARRANTY; without even the implied warranty of ;; MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the ;; GNU General Public License for more details. ;; You should have received a copy of the GNU General Public License ;; along with GNU Emacs. If not, see http://www.gnu.org/licenses/. ;;; Commentary: ;; Requires at least version 4.27 of org.el ;; This program allow configurable publishing of related sets of ;; Org-mode files as a complete website. ;; ;; org-publish.el can do the following: ;; ;; + Publish all one's org-files to HTML or LaTeX ;; + Upload HTML, images, attachments and other files to a web server ;; + Exclude selected private pages from publishing ;; + Publish a clickable index of pages ;; + Manage local timestamps for publishing only changed files ;; + Accept plugin functions to extend range of publishable content ;; ;; Special thanks to the org-mode maintainer Carsten Dominik for his ;; ideas, enthusiasm, and cooperation. ;;; Installation: ;; Put org-publish.el in your load path, byte-compile it, and then add ;; the following lines to your emacs initialization file: ;; (autoload 'org-publish org-publish nil t) ;; (autoload 'org-publish org-publish-all nil t) ;; (autoload 'org-publish org-publish-current-file nil t) ;; (autoload 'org-publish org-publish-current-project nil t) ;; NOTE: When org-publish.el is included with org.el, those forms are ;; already in the file org-install.el, and hence don't need to be put ;; in your emacs initialization file in this case. ;;; Usage: ;; ;; The program's main configuration variable is ;; `org-publish-project-alist'. See below for example configurations ;; with commentary. ;; The main interactive functions are: ;; ;; M-x org-publish ;; M-x org-publish-all ;; M-x org-publish-current-file ;; M-x org-publish-current-project Simple example configuration: ;; (setq org-publish-project-alist ;;
[Orgmode] Re: a small (?) feature request
Leo [EMAIL PROTECTED] writes: On 2008-05-24 22:33 +0100, Jose A. Ortega Ruiz wrote: [...] Is there already a way of doing this? Setting `org-special-ctrl-a/e' to t Yes, exactly what i was looking for. Thanks a lot. jao, who will try to rtfm next time -- Always have a vision. Why spend your life making other people’s dreams? -Orson Welles (1915-1985) ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] a small (?) feature request
Jose A. Ortega Ruiz [EMAIL PROTECTED] wrote: Hi, When i'm on a header line that has tags, C-e will bring the cursor, well, to the end of the line, i.e., after the tags. But, most of the time, that's not the 'end' i meant: i want to go to the 'end' of the header text *before* the tags (e.g., to add some text to said header--modifying the tags is much more conveniently done via C-cC-c). Is there already a way of doing this? You can find what function C-e is bound to (C-h c C-e RET) and then get the documentation for this function (C-h f org-end-of-line RET) which says: org-end-of-line is an interactive compiled Lisp function in `org.el'. It is bound to C-e. (org-end-of-line optional ARG) Go to the end of the line. If this is a headline, and `org-special-ctrl-a/e' is set, ignore tags on the first attempt, and only move to after the tags when the cursor is already beyond the end of the headline. So, setting org-special-ctrl-a/e should do what you want. HTH, Nick ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
