emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Charles <charles.cave@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: GNU Emacs 24.3.1 creates macro-expansion failure messages
Date: Tue, 16 Apr 2013 04:59:56 +0000 (UTC)	[thread overview]
Message-ID: <loom.20130416T065631-872@post.gmane.org> (raw)
In-Reply-To: 87mwt15isq.fsf@bzg.ath.cx

Bastien <bzg <at> gnu.org> writes:

> I gather this is not with emacs -Q.
> Can you narrow down to what causes this in your configuration?

I decided to start with a new .emacs file by commenting out every line then 
adding back the commands starting with orgmode. Everything worked fine so I 
can only assume that I had been loading an old package that caused a conflict.

Now that I am happy with the latest version of org-mode and GNU Emacs I wont 
pursue the cause of my reported problem - obviously something of my own 

It is good to have a much cleaner .emacs file.  I deleted a lot of code of 
things I have tried out in the past and dont use.


  reply	other threads:[~2013-04-16  5:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-14 13:24 GNU Emacs 24.3.1 creates macro-expansion failure messages Charles Cave
2013-04-14 13:43 ` Bastien
2013-04-16  4:59   ` Charles [this message]
2013-04-16  6:25     ` Bastien

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=loom.20130416T065631-872@post.gmane.org \
    --to=charles.cave@gmail.com \
    --cc=emacs-orgmode@gnu.org \


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