Re: Emacs-orgmode Digest, Vol 27, Issue 47

["Charles Martin" <chasrmartin@gmail.com>]

On Sun, May 25, 2008 at 10:00 AM,  <emacs-orgmode-request@gnu.org> 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 <austin.frank@gmail.com>
> Subject: [Orgmode] Re: Org mode release 6.04
> To: emacs-orgmode@gnu.org
> Message-ID: <m07idi8sj1.fsf@h-67-102-51-235.mclnva23.covad.net>
> 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.