emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: serious problems with org-8 under Xemacs-21.5.32
Date: Fri, 14 Jun 2013 05:32:06 -0400	[thread overview]
Message-ID: <87obb9xckp.fsf@pierrot.dokosmarshall.org> (raw)
In-Reply-To: 87zjut2jk1.fsf@gilgamesch.quim.ucm.es

Uwe Brauer <oub@mat.ucm.es> writes:

> Hello
>
> In order to check whether org-8 works under Xemacs-21.5.32 Mule (and not
> using my old org-7 setting), I did the following
>
>     -  I started xemacs -vanilla (equivalent to GNU emacs -q)
>
>     -  I loaded the following init file:
>
>
> ,----
> | (push (expand-file-name
> | "~/xemacs/site-lisp/packages/org-8.0.3/lisp/") load-path)
> | (push (expand-file-name
> | "~/xemacs/site-lisp/packages/org-8.0.3/contrib/lisp/") load-path)
> | (push (expand-file-name
> | "~/xemacs/site-lisp/packages/org-8.0.3/contrib/odt/etc/schema/")
> | load-path)
> | 
> | (require 'org-compat)
> | (require 'ox)
> | (require 'org-install)
> `----
>
> I opened an org file. Observations
>
>     -  the file was in *fundamental* mode!
>

You need to set up auto-mode-alist in your init file:

(add-to-list 'auto-mode-alist   '("\\.org$" . org-mode))


>     -  I turned on org-mode and received and error I attach.
>

The error is[fn:1]:

--8<---------------cut here---------------start------------->8---
Debugger entered--Lisp error: (invalid-state "Autoloading failed to define function" outline-previous-heading)
  outline-previous-heading()
  org-cycle-show-empty-lines(overview)
  run-hook-with-args(org-cycle-show-empty-lines overview)
  org-cycle-internal-global()
  org-cycle((4))
  org-set-startup-visibility()
  ...
  call-interactively(org-mode)
  command-execute(org-mode t)
  execute-extended-command(nil)
  call-interactively(execute-extended-command)
--8<---------------cut here---------------end--------------->8---

so xemacs found an outline.el that did not define
outline-previous-heading. Check which outline.el xemacs finds with M-x
locate-library RET outline RET. It's probably a compiled file, but the
corresponding outline.el should be in the same directory, or you might need to
get a source package with the xemacs .el files to find it. Check what version
it is, compare it with the emacs version, check whether it includes
outline-previous-heading (probably not, hence the error).

Crossing fingers and toes, you might try using the emacs outline.el but
unless you are really lucky, it's probably not going to work.
Which will mean that somebody will nees to port a recent outline.el from
emacs to xemacs. An xemacs specific mailing list seems the best bet for
that.

>     -  I tried to use org-preview-latex-fragment and received a
>        different error (also attached)
>

The error here:

--8<---------------cut here---------------start------------->8---
Debugger entered--Lisp error: (void-function face-at-point)
  face-at-point()
--8<---------------cut here---------------end--------------->8---

Presumably xemacs does not have face-at-point.

>     -  I tried to use org-submit-bug-report and received third error.
>

--8<---------------cut here---------------start------------->8---
Debugger entered--Lisp error: (void-function call-process-shell-command)
  call-process-shell-command("command" nil nil nil "-v" "x11idle")
--8<---------------cut here---------------end--------------->8---


and it does not seem to have call-process-shell-command. This is
a thin wrapper around call-process (which xemacs should have), so
this should be easy to port.

> Any comments?
>
> thanks
>
> Uwe Brauer 
>
>
>

Footnotes:

[fn:1] Can you please make sure that when you send attachments they are
typed properly? They are sent as "application/octet-stream" currently,
requiring two steps: saving them and then opening the saved file. For
backtraces, just use "text/plain" instead: emacs/gnus knows how to open
these directly.

-- 
Nick

  reply	other threads:[~2013-06-14  9:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-14  8:17 serious problems with org-8 under Xemacs-21.5.32 Uwe Brauer
2013-06-14  9:32 ` Nick Dokos [this message]
2013-06-14 10:40   ` face-at-point (was: serious problems with org-8 under Xemacs-21.5.32) Uwe Brauer
2013-06-14 12:21     ` face-at-point Nick Dokos
2013-06-14 12:31       ` face-at-point Nick Dokos
2013-06-14 13:00       ` face-at-point Uwe Brauer
2013-06-14 20:17         ` face-at-point Nick Dokos
2013-06-14 20:55           ` face-at-point Eric S Fraga
2013-06-14 21:18           ` face-at-point Uwe Brauer
2013-06-14 22:32             ` face-at-point Nick Dokos
2013-06-15 11:45     ` face-at-point Michael Sperber
2013-06-14 11:06   ` [partically solved] (was: serious problems with org-8 under Xemacs-21.5.32) Uwe Brauer
2013-06-14 15:00   ` serious problems with org-8 under Xemacs-21.5.32 Eric S Fraga
2013-06-14 16:23     ` Nick Dokos

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87obb9xckp.fsf@pierrot.dokosmarshall.org \
    --to=ndokos@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).