emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <dominik@science.uva.nl>
To: York Block <ypblock@yahoo.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: orgmode under XEmacs
Date: Mon, 6 Nov 2006 11:06:37 +0100	[thread overview]
Message-ID: <bd429b03a7adefe7e5f4adfab52dd801@science.uva.nl> (raw)
In-Reply-To: <20061106013941.74142.qmail@web31705.mail.mud.yahoo.com>

Hi York,

we definitely need more information in order to find what the problem  
is.

1. org-mode version
    Always make sure you are using the latest version of org-mode because
    you bug may already have been found and fixed.

2. A copy of your entire configuration regarding org-mode.

3. A back-trace of the error.  This you can produce in the following  
way:
    - start a fresh xemacs and make sure that you load noutline.el and
      org.el instead of the byte-compiled .elc versions.  For example,
      I do this with

           xemacs -l /path/to/noutline.el -l /path/to/org.el

    - go to the menu Options->Troubleshooting
      and select "Debug on Error" there.

4. Go ahead and do whatever you have to do to hit the bug, like loading
    an org-mode file.

5. When the error is hit, xemacs will pop up a "*Backtrace*" buffer.
    We need to see the full content of this buffer.  As this buffer
    may contain very long lines, it is better to send it as an attachment
    than to copy it into the email.

With this information I often can find the bug already, or at least
know what else to ask from you.

- Carsten

On Nov 6, 2006, at 2:39, York Block wrote:

> Hi,
>
> I am trying to get orgmode working under XEmacs 21.4 (patch 18)  
> without any
> luck. I have followed the instruction, installed noutline-mode and set  
> all the
> variables as requested but I keep getting the following error:
>
> Meta-x org-mode --> Wrong type argument: stringp, nil
> If I load a .org file --> File mode specification error:  
> (wrong-type-argument
> stringp nil)
>
> Thanks in advance,
>
> York P. Block
>
> ps. I am not an expert on XEmacs or Emacs configuration, I usually  
> copy the
> config  from what I find in the web.
>
>
>
> _______________________________________________________________________ 
> ___________________
> Check out the New Yahoo! Mail - Fire up a more powerful email and get  
> things done faster.
> (http://advision.webevents.yahoo.com/mailbeta)
>
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>
>

--
Carsten Dominik
Sterrenkundig Instituut "Anton Pannekoek"
Universiteit van Amsterdam
Kruislaan 403
NL-1098SJ Amsterdam
phone: +31 20 525 7477

      reply	other threads:[~2006-11-06 11:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-06  1:39 orgmode under XEmacs York Block
2006-11-06 10:06 ` Carsten Dominik [this message]

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=bd429b03a7adefe7e5f4adfab52dd801@science.uva.nl \
    --to=dominik@science.uva.nl \
    --cc=emacs-orgmode@gnu.org \
    --cc=ypblock@yahoo.com \
    /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).