emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-orgmode@gnu.org
Subject: Re: Paths including spaces fail the installation: Patch
Date: Thu, 14 Mar 2013 07:49:19 +0100	[thread overview]
Message-ID: <87r4jifpcg.fsf@Rainer.invalid> (raw)
In-Reply-To: 87ip4vnpau.fsf@Rainer.invalid

[please reply to the list]

> BS-Quoting and Doublequote-ing were the first things I tried:

Yes I see, that is due to inadvertent double quoting.  Try this
definition in local.mk (not the extra two single quotes around

--8<---------------cut here---------------start------------->8---
# How to generate org-version.el
	  --eval '(load "org-compat.el")' \
	  --eval '(load "../mk/org-fixup.el")' \
	  --eval '(org-make-org-version "$(ORGVERSION)" "$(GITVERSION)" "'$(datadir)'")'
--8<---------------cut here---------------end--------------->8---

Please test, I'll push the fix if it solves your problem.

> But quite apart from that, I seems like the right thing to me to make
> sure that things that should be one string get interpreted as one
> string on the logic level, which even fixing the escaping behaviour
> would not do in the makefiles themselves.

The build system assumes that these definitions will always be
interpreted by the shell (the above fix makes sure it actually does), so
you need to shell-quote in the definitions already.  The Makefile itself
never cares what those strings are, embedded spaces or not.

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

SD adaptation for Waldorf rackAttack V1.04R1:

  reply	other threads:[~2013-03-14  6:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-13 15:03 Paths including spaces fail the installation: Patch Bernd Haug
2013-03-13 16:05 ` Bastien
2013-03-13 18:10 ` Achim Gratz
2013-03-14  6:49   ` Achim Gratz [this message]
2013-04-22 13:33     ` Bernd Haug
2013-04-22 15:47       ` Achim Gratz
2013-04-23  6:22         ` Bernd Haug
2013-04-23 16:56           ` Achim Gratz
2013-04-25 10:24             ` Bernd Haug

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=87r4jifpcg.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).