emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Martyn Jago <martyn.jago@btinternet.com>
To: emacs-orgmode@gnu.org
Subject: Re: error on opening org-file with #+startup: indent
Date: Tue, 24 Apr 2012 22:45:24 +0100	[thread overview]
Message-ID: <m2aa20u7m3.fsf@btinternet.com> (raw)
In-Reply-To: 87mx61c513.fsf@Rainer.invalid

Hi Achim

Achim Gratz <Stromeko@nexgo.de> writes:

> Fritz Kunze writes:
>>      I ran M-x load-library org followed by M-x org-version - which
>> returned 7.8.09. 
>
> You didn't generate and (require 'org-install).
>
>>           (Incidentally, and for the sake of completeness in this
>> report, I built the compiled version of this upgrade by using 
>>
>>             M-x cd ~/.emacs.d/org-7.8.09/ followed by C-u 0 M-x
>> byte-recompile-directory)
>
> You still don't have org-install.el
>

I think this tone of reply is very harsh, and I feel for the OP. Has it
suddenly become a requirement to know emacs-lisp, and have a reasonable
understanding of `autoload' to even install?

A very formal announcement and good documentation would perhaps have been a
good idea. Don't get me wrong - I like the new makefile, but there *is*
now magic that there never was, without question. 

I think it would be better to refer to some good documentation rather
than short terse admonishment over something that `used to work'.

My 2c.

Best, Martyn

>>      I renamed the org-6.36 folder. I started up emacs and the error
>> still appeared. 
>
> You do not have org-install.el and you are picking up outdated autoload
> definitions from your emacs installation.
>
>> As an experiment, I modified the load-path to consist only of one
>> statement:
>>      (add-to-list 'load-path "~/.emacs.d/org-7.8.09/")
>>      ; (add-to-list 'load-path "~/.emacs.d/org-7.8.09/contrib/lisp")
>> And suddenly the "bug" vanished.  What's going on - do you have any
>> idea?  I thought I would certainly need this
>> directory "~/.emacs.d/org-7.8.09/contrib/lisp" in my load-path.
>
> Fix the installation first and then worry about things in contrib/.
>
>
> Regards,
> Achim.

  reply	other threads:[~2012-04-24 21:45 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-22 21:21 error on opening org-file with #+startup: indent fkunze
2012-04-23 23:15 ` Bastien
2012-04-24 11:45   ` Mike McLean
2012-04-24 12:45     ` Bastien
2012-04-24 14:22     ` Fritz Kunze
2012-04-24 19:18       ` Achim Gratz
2012-04-24 21:45         ` Martyn Jago [this message]
2012-04-25 16:47           ` Achim Gratz
2012-04-25 18:56             ` Achim Gratz
2012-04-25 21:01           ` fkunze
2012-04-25  1:41         ` Mike McLean
2012-04-25 21:29           ` fkunze
2012-04-25 20:53         ` fkunze
2012-04-26  4:29           ` Achim Gratz
2012-04-26  7:03           ` Bastien
2012-04-26 17:08             ` fkunze
2012-04-27 21:31               ` 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:
  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=m2aa20u7m3.fsf@btinternet.com \
    --to=martyn.jago@btinternet.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).