emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-orgmode@gnu.org
Subject: Re: HTML export fails with (void-variable org-version)
Date: Fri, 27 Apr 2012 07:26:41 +0200	[thread overview]
Message-ID: <87ehr968z2.fsf@Rainer.invalid> (raw)
In-Reply-To: 87y5piartp.fsf@norang.ca

Bernt Hansen writes:
> Thanks for the detailed explanation Achim.  I hope my problem report on
> this issue wasn't taken as a complaint - it wasn't intended that way --

Don't worry, problem reports are appreciated (even in the form of
comaplints, which yours weren't).  As I said before, I do want to
support everything non-buggy that the old Makefile did.

> I'll redo my make autoloads after pointing at NT Emacs (tomorrow) and
> will remove emacs from Cygwin since the only reason I installed it in
> the first place was to try to get make autoloads to complete.

If you pull from latest Git you should get a Makefile that drops a
local.mk into your lap that you only need to edit (unless you already
have one).  It already has a default target that includes "autoloads".
It also updates the info documentation, which should work when you have
makeinfo on Cygwin.  If not, just put your own default target there
without "info", but having a current documentation comes highly

> Your efforts on cleaning up the Makefile system for org-mode are really
> appreciated.  I'll just add 'make autoloads' to my list of things to do
> when updating my master branch in git.

That should be a only temporary measure, it will eventually work as it
did before — with some magic behind the curtains to DTRT(TM) instead of
relying on buggy behaviour.

+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Factory and User Sound Singles for Waldorf rackAttack:

  reply	other threads:[~2012-04-27  5:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-23 13:13 HTML export fails with (void-variable org-version) Eric Schulte
2012-04-23 15:32 ` Bastien
2012-04-23 15:49   ` Torsten Wagner
2012-04-23 16:04   ` Achim Gratz
2012-04-25 16:21     ` Bernt Hansen
2012-04-25 17:18       ` Jonathan Leech-Pepin
2012-04-25 21:07         ` Bernt Hansen
2012-04-26  4:42           ` Achim Gratz
2012-04-27  1:25             ` Bernt Hansen
2012-04-27  5:26               ` Achim Gratz [this message]
2012-04-25 18:15       ` Achim Gratz

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=87ehr968z2.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --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).