Re: planner & muse mode questions

[Charles Philip Chan]

Wei Chang <changwei.cn@gmail.com> writes:

> How to setup and use org-mtags.el ?

This is from the el file:

,----
| ;;; Commentary:                                                               
    |
| ;;                                                                            
    |
| ;; This modules implements some of the formatting tags available in           
    |
| ;; Emacs Muse.  This is not a way if adding new functionality, but just       
    |
| ;; a different way to write some formatting directives.  The advantage is     
    |
| ;; that files written in this way can be read by Muse reasonably well,        
    |
| ;; and that this provides an alternative way of writing formatting            
    |
| ;; directives in Org, a way that some might find more pleasant to type        
    |
| ;; and look at that the Org's #+BEGIN..#+END notation.                        
    |
|                                                                               
    |
| ;; The goal of this development is to make it easier for people to            
    |
| ;; move between both worlds as they see fit for different tasks.              
    |
|                                                                               
    |
| ;; The following muse tags will be translated during export into their        
    |
| ;; native Org equivalents:                                                    
    |
| ;;                                                                            
    |
| ;;   <br>                                                                     
    |
| ;;        Needs to be at the end of a line.  Will be translated to "\\".      
    |
| ;;                                                                            
    |
| ;;   <example>                                                                
    |
| ;;        Needs to be on a line by itself, similarly the </example> tag.      
    |
| ;;        Will be translated into Org's #+BEGIN_EXAMPLE construct.            
    |
| ;;                                                                            
    |
| ;;   <quote>                                                                  
    |
| ;;        Needs to be on a line by itself, similarly the </quote> tag.        
    |
| ;;        Will be translated into Org's #+BEGIN_QUOTE construct.              
    |
| ;;                                                                            
    |
| ;;                                                                            
    |
| ;;   <comment>                                                                
    |
| ;;        Needs to be on a line by itself, similarly the </comment> tag.      
    |
| ;;        Will be translated into Org's #+BEGIN_COMMENT construct.            
    |
| ;;                                                                            
    |
| ;;   <verse>                                                                  
    |
| ;;        Needs to be on a line by itself, similarly the </verse> tag.        
    |
| ;;        Will be translated into Org's #+BEGIN_VERSE construct.              
    |
| ;;                                                                            
    |
| ;;   <contents>                                                               
    |
| ;;        This gets translated into "[TABLE-OF-CONTENTS]".  It will not       
    |
| ;;        trigger the production of a table of contents - that is done        
    |
| ;;        in Org with the "#+OPTIONS: toc:t" setting.  But it will define     
    |
| ;;        the location where the TOC will be placed.                          
    |
| ;;                                                                            
    |
| ;;   <literal style="STYLE">    ;; only latex and html supported in Org       
    |
| ;;        Needs to be on a line by itself, similarly the </literal> tag.      
    |
| ;;                                                                            
    |
| ;;   <src lang="LANG">                                                        
    |
| ;;        Needs to be on a line by itself, similarly the </src> tag.          
    |
| ;;        Will be translated into Org's BEGIN_SRC construct.                  
    |
| ;;                                                                            
    |
| ;;   <include file="FILE" markup="MARKUP" lang="LANG" prefix="str" 
prefix1="str"> |
| ;;        Needs to be on a line by itself.                                    
    |
| ;;        Will be translated into Org's #+INCLUDE construct.                  
    |
| ;;                                                                            
    |
| ;; The lisp/perl/ruby/python tags can be implemented using the                
    |
| ;; `org-eval.el' module, which see.                                           
    |
`----

Charles

-- 
    if (argc > 1 && strcmp(argv[1], "-advice") == 0) {
        printf("Don't Panic!\n");
        exit(42);
    }
(Arnold Robbins in the LJ of February '95, describing RCS)

-- 
>Ever heard of .cshrc?
That's a city in Bosnia.  Right?
(Discussion in comp.os.linux.misc on the intuitiveness of commands.)

pgptCl5Jb_V9O.pgp
Description: PGP signature