From: Angel de Vicente <angelv@iac.es>
To: Jambunathan K <kjambunathan@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-version reported as 6.33x after upgrading to the "latest and greatest" with Emacs' Package Manager
Date: Tue, 31 Jan 2012 05:19:43 +0000 [thread overview]
Message-ID: <yegaa54bg9c.fsf@carro.ll.iac.es> (raw)
In-Reply-To: <81ty3dm8cd.fsf@gmail.com> (Jambunathan K.'s message of "Mon, 30 Jan 2012 22:32:58 +0530")
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=utf-8, Size: 2034 bytes --]
Hi,
Jambunathan K <kjambunathan@gmail.com> writes:
>> Any idea on how to test if org is getting confused with 6.33 beyond
>> reporting that as its version?
>
> In your .emacs file, *just before* package-initialize add this and
> restart Emacs.
>
> (when (featurep 'org)
> (error "Some mysterious force has already loaded org. Investigate why
> this is so."))
Yes, there were mysterious forces... :-)
As I recall it I had two problems in my .emacs file:
1) a line:
(find-file "~/org/MAIN.org")
2) and
;; Remember-Mode
(org-remember-insinuate)
(setq org-directory "/home/angelv/org/")
(setq org-default-notes-file (concat org-directory "/notes.org"))
(define-key global-map "\C-cr" 'org-remember)
Those were forcing the bundled org version to load.
Issue solved by:
* Moving line in 1) right after the (package-initialize) right at the
bottom of my .emacs
* Getting rid of lines in 2) and substituting them by:
(setq org-directory "/home/angelv/org/")
(setq org-default-notes-file (concat org-directory "notes.org"))
(define-key global-map "\C-cc" 'org-capture)
* Putting out of the way the directory where the bundled ORG was
(probably not needed, but for extra peace of mind)
BUT, I still could not capture anything with C-cc, and I got an error
about org-called-interactively-p not being valid/defined.. (don't
remember now). It looks like the new org was byte-compiled when the old
org was active and there were some issues in there. Deleting all the
.elc files, making sure that only the new org was active and then
byte-compiling the .el files again did the trick.
Cheers,
--
Ãngel de Vicente
http://www.iac.es/galeria/angelv/
---------------------------------------------------------------------------------------------
ADVERTENCIA: Sobre la privacidad y cumplimiento de la Ley de Protección de Datos, acceda a http://www.iac.es/disclaimer.php
WARNING: For more information on privacy and fulfilment of the Law concerning the Protection of Data, consult http://www.iac.es/disclaimer.php?lang=en
next prev parent reply other threads:[~2012-01-31 5:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-30 11:40 org-version reported as 6.33x after upgrading to the "latest and greatest" with Emacs' Package Manager Angel de Vicente
2012-01-30 13:45 ` Jambunathan K
2012-01-30 15:30 ` Angel de Vicente
2012-01-30 17:02 ` Jambunathan K
2012-01-31 5:19 ` Angel de Vicente [this message]
2012-01-30 16:35 ` Sankalp
2012-01-30 17:50 ` Jambunathan K
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=yegaa54bg9c.fsf@carro.ll.iac.es \
--to=angelv@iac.es \
--cc=emacs-orgmode@gnu.org \
--cc=kjambunathan@gmail.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).