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

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

[Charles Martin]

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.

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

[Charles Martin]

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

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

[Carsten Dominik]

Hi Charles, this report meant that a

  (require 'org-id)

has failed.  Cannot imagine why.

- Carsten

On May 25, 2008, at 6:39 PM, Charles Martin wrote:

> 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

can't get source code editing working

[Dan Davison]

On Sun, May 25, 2008 at 10:25:22AM -0600, Charles Martin wrote:
> 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.
<...>
> >
> > 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.

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

Re: can't get source code editing working

[Carsten Dominik]

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