emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@gnu.org>
To: Johan Ekh <ekh.johan@gmail.com>
Cc: marc@ihm.name, "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Adding new heading results in "not in an item"
Date: Wed, 24 Apr 2013 09:39:11 +0200	[thread overview]
Message-ID: <87d2tk4bts.fsf@bzg.ath.cx> (raw)
In-Reply-To: <CAH13ZghOewUN8_Kgx2x+sRVVg7=TCrxZcs4n0WXqtK09w8PRpg@mail.gmail.com> (Johan Ekh's message of "Wed, 24 Apr 2013 08:18:18 +0200")

Hi Johan,

Johan Ekh <ekh.johan@gmail.com> writes:

> Marc: I use git for installation and I don't think I have any old
> files in my load path. I have the files in my home directory but the
> compiled files are installed in the system emacs/site-lisp.

The compiled files *are* in your load-path, because Emacs loads them
when you launch it.  This is in /usr/.../emacs/lisp/loaddefs.el, which
contains pointers to the autoloaded functions.  Some Org's functions
are autoloaded by Emacs, and these are functions from an older version
than the one you installed manually.

> Victor: Good, but please help a newbie. How do I apply this patch?

You don't need to install this particular patch, you just need to
updated your Git installation.

~$ cd org-mode/  [change with the relevant path]
~$ git pull
~$ make

This pull latest master branch and compile Org.

Or you can do:

~$ cd org-mode/  [change with the relevant path]
~$ make update

> Finally, I noticed that adding a new heading works with Ctrl-RET. But
> I still want M-RET to work!

Please follow the instructions above and report any problem you may
have afterwards.



  reply	other threads:[~2013-04-24  7:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-23 14:41 Adding new heading results in "not in an item" Johan Ekh
2013-04-23 20:36 ` Marc-Oliver Ihm
2013-04-23 21:15 ` Viktor Rosenfeld
2013-04-24  6:18   ` Johan Ekh
2013-04-24  7:39     ` Bastien [this message]
2013-04-24 13:28       ` Johan Ekh

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:

  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=87d2tk4bts.fsf@bzg.ath.cx \
    --to=bzg@gnu.org \
    --cc=ekh.johan@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=marc@ihm.name \


* 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


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).