Uwe Brauer writes:
Hello
Since I can't submit a bug report I attach the error trace
when I try to open a file in org mode:
Hi Uwe
I'm also using 21.4.22.
To send bug reports just copy org-colview-xemacs.el over org-
colview.el
To get rid of the (void-function decompose-region) error message I
copied the following definition from mule-composite.el from
xemacs-21.5-b28:
(defun decompose-region (start end)
"UNIMPLEMENTED.
Decompose text in the current region.
When called from a program, expects two arguments,
positions (integers or markers) specifying the region."
(interactive "r")
(let ((modified-p (buffer-modified-p))
(buffer-read-only nil))
(remove-text-properties start end '(composition nil))
(set-buffer-modified-p modified-p)))
Then org-mode started fine for me. But I had to do some other
changes in
order to execute source blocks with babel and produce html and pdf
output.
--- ob.el.orig 2010-08-07 09:00:28.000000000 +0200
+++ ob.el 2010-10-15 12:46:33.281250000 +0200
@@ -258,7 +258,7 @@
'((:session . "none") (:results . "silent") (:exports . "results"))
"Default arguments to use when evaluating an inline source block.")
-(defvar org-babel-current-buffer-properties)
+(defvar org-babel-current-buffer-properties nil)
(make-variable-buffer-local 'org-babel-current-buffer-properties)
(defvar org-babel-result-regexp
--- org-latex.el.orig 2010-08-07 09:00:28.000000000 +0200
+++ org-latex.el 2010-10-15 12:17:53.328125000 +0200
@@ -849,7 +849,7 @@
(save-match-data
(shell-quote-argument file))
t t cmd)))
- (shell-command cmd outbuf outbuf)))
+ (shell-command cmd outbuf)))
(message "Processing LaTeX file...done")
(if (not (file-exists-p pdffile))
(error "PDF file was not produced")
--- ob-latex.el.orig 2010-08-07 09:00:28.000000000 +0200
+++ ob-latex.el 2010-10-15 12:16:31.531250000 +0200
@@ -137,7 +137,7 @@
(save-match-data
(shell-quote-argument tex-file))
t t cmd)))
- (shell-command cmd outbuf outbuf)))
+ (shell-command cmd outbuf)))
(if (not (file-exists-p pdffile))
(error "PDF file was not produced from %s" tex-file)
(set-window-configuration wconfig)
These two patches are needed due to differences in the following
function definitions:
Emacs: (defvar symbol &optional initvalue docstring)
XEmacs: (defvar SYMBOL INITVALUE DOCSTRING)
Emacs: (shell-command command &optional output-buffer error-buffer)
XEmacs: (shell-command COMMAND &optional OUTPUT-BUFFER)
In addition the function number-sequence is not defined in XEmacs.
So I
copied the definition from the emacs distribution (in subr.el):
(defun number-sequence (from &optional to inc)
"Return a sequence of numbers from FROM to TO (both inclusive) as a
list.
INC is the increment used between numbers in the sequence and
defaults to 1.
So, the Nth element of the list is \(+ FROM \(* N INC)) where N
counts from
zero. TO is only included if there is an N for which TO = FROM + N
* INC.
If TO is nil or numerically equal to FROM, return \(FROM).
If INC is positive and TO is less than FROM, or INC is negative
and TO is larger than FROM, return nil.
If INC is zero and TO is neither nil nor numerically equal to
FROM, signal an error.
This function is primarily designed for integer arguments.
Nevertheless, FROM, TO and INC can be integer or float. However,
floating point arithmetic is inexact. For instance, depending on
the machine, it may quite well happen that
\(number-sequence 0.4 0.6 0.2) returns the one element list \(0.4),
whereas \(number-sequence 0.4 0.8 0.2) returns a list with three
elements. Thus, if some of the arguments are floats and one wants
to make sure that TO is included, one may have to explicitly write
TO as \(+ FROM \(* N INC)) or use a variable whose value was
computed with this exact expression. Alternatively, you can,
of course, also replace TO with a slightly larger value
\(or a slightly more negative value if INC is negative)."
(if (or (not to) (= from to))
(list from)
(or inc (setq inc 1))
(when (zerop inc) (error "The increment can not be zero"))
(let (seq (n 0) (next from))
(if (> inc 0)
(while (<= next to)
(setq seq (cons next seq)
n (1+ n)
next (+ from (* n inc))))
(while (>= next to)
(setq seq (cons next seq)
n (1+ n)
next (+ from (* n inc)))))
(nreverse seq))))
Right now with these changes the latest org-mode works fine for me (at
least for my usage pattern).
Uwe Brauer
Ciao
Volker
_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
address@hidden
http://lists.gnu.org/mailman/listinfo/emacs-orgmode