On Jan 26, 2011, at 10:34 AM, Eli Zaretskii wrote:
> The file org-complete.el, added about a month ago, causes a file-name
> clash with org-compat.el after 8+3 truncation. This causes trouble
> when unpacking Emacs tarballs on DOS filesystems.
Also rename org-complete-* functions in org-pcomplete.el and remove a
wrong reference to org-complete in doc/org.texi.
We still use org-complete-* namespace for the custom group and the
custom variables.
sync_release and sync_manual are copying release files from the
temporary RELEASE directory to the server at /var/www/orgmode.org
the relup directive now calls makerelease and sync_* directives.
A small fix: remove calls to updateweb.
I removed this directives:
- relup: which called makerelease, upload_release and upload_manual
- upload_release: which uploaded the release from Carsten's machine
- upload_manual: which uploaded the manuals from Carsten's machine
We don't need these directives anymore as the release process is
done from orgmode.org server.
* Makefile (LISPF): Add org-special-blocks to the list of Lisp files
* lisp/org-special-blocks.el (htmlp):
(latexp):
(line): Add defvars for dynamically scoped variables.
* lisp/org.el (org-modules): Move org-special-blocks into
the core modules section.
Carsten
Reworked the changes based on your feedback. Customize to your tastes.
Jambunathan K.
From 1121461037e0308054afeabf8c67bd1a568dd9b1 Mon Sep 17 00:00:00 2001
From: Jambunathan K <kjambunathan@gmail.com>
Date: Tue, 5 Oct 2010 15:33:08 +0530
Subject: [PATCH] Support for elpa-compatible tarballs
* Makefile (pkg): New target for creating elpa-compatible tarball.
* Makefile (LISPF): adding ob-scheme.el to the makefile
* lisp/ob-scheme.el: very preliminary support for evaluating scheme
code blocks
* lisp/org.el (org-babel-load-languages): adding scheme
ob-org has two non-standard header arguments in that it exports it's
results by default and the result type defaults to raw, this ensures
that the body of a begin_src org block exports transparently.
This is a breaking change in that if you are currently using org
code blocks to export org-fontified code you will have to set the
":exports" header argument for org-mode blocks to "code" on a block,
file, language or system-wide basis.
* Makefile (LISPF): adding ob-org.el to the makefile
* lisp/ob-org.el: defines handling of org code blocks
* lisp/ob.el (org-babel-insert-result): now when "org" is a result
type the results are wrapped in an org code block
* Makefile (LISPF): now compiling and installing ob-plantuml.el
* contrib/scripts/.gitignore : ignores the plantuml.jar file, so that
it can be located next to ditaa.jar
* lisp/ob-plantuml.el: adding copyright notice and FSF attribution
(org-plantuml-jar-path): now a defcustom
(org-babel-execute:plantuml): now using org-babel-eval which
displays error messages
* lisp/org.el (org-babel-load-languages): ob-plantuml is now part of
org-babel-load-languages
The latest XEmacs package release does now contain a modern version of
outline.el, put there by Michael Sperber.
* Makefile: Remove targets related to noutline.el.
* README: Remove the entry for the xemacs directory.
* README_DIST: Remove the entry for the xemacs directory.
* doc/org.texi (Installation): Remove the special installation
instructions for XEmacs.
* lisp/org.el (outline): Remove special code to load noutline.el
for XEmacs.
* xemacs/README: File removed.
* xemacs/noutline.el: File removed.
* xemacs/ps-print-invisible.el: File removed.
OK, we finally have a make file where I can do a complete release,
including all the git updates on master and maint branches, with a
single command:
make release TAG=N.NN
It is important that the working directory is clean when calling this
command.
Since this command can fail and then leave the git repo in an
uncertain state, it is best to first run this:
make testrelease
This will create a throw-away branch "testrelease" and try alll the
commands there, to make sure everything is fine.
from the comments of the new file
This software provides EMACS org-babel export support for message
sequence charts. The mscgen utility is used for processing the
sequence definition, and must therefore be installed in the system.
Mscgen is available and documented at
http://www.mcternan.me.uk/mscgen/index.html
This code is directly inspired by Eric Schulte's ob-dot.el
Example:
msc {
A,B;
A -> B [ label = "send message" ];
A <- B [ label = "get answer" ];
}
Header for alternative file type:
This differs from most standard languages in that
1) there is no such thing as a "session" in mscgen
2) we are generally only going to return results of type "file"
3) we are adding the "file" and "filetype" header arguments
4) there are no variables
Bastien Guerry
Carsten Dominik
Eric Schulte
John Wiegley
Jambunathan K
Christian Egli