emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Michael Alan Dorman <mdorman@jaunder.io>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: org ELPA broken (was: Re: Bug: bug&fix for org-compile-file on Windows)
Date: Mon, 12 Dec 2016 13:39:11 -0500	[thread overview]
Message-ID: <87wpf52drk.fsf_-_@jaunder.io> (raw)
In-Reply-To: <877f75bnax.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Mon, 12 Dec 2016 08:48:22 +0100")

Has the URL for Org ELPA moved?  Because if I look at
http://orgmode.org/elpa/, I don't see any updates since 11/18?

Assuming the build-org-pkg.txt file is intended to be a record of the
build process, it would appear there is an error preventing the code
from building correctly.

Mike.

Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:

> Hello,
>
> Mirko Vukovic <mirko.vukovic@gmail.com> writes:
>
>> I was not able to preview latex fragments using
>> org-toggle-latex-fragment (C-c C-x C-l)
>>
>> I traced the problem to the (shell-command ...) in org-compile-file
>> during the dvipng step.
>>
>> The problem was in the formatting of the destination file (the -o switch).
>> It consists
>> of the directory and filename.  Both were enclosed in double quotes, so
>> that when concatenated the string looked like this:
>> \"path\"\"filename\".extension
>
> Thanks. However, this issue was fixed a few days ago. The fix should be
> available in today's Org ELPA, or in the yet to be released Org 9.0.2.
>
> Regards,

  reply	other threads:[~2016-12-12 18:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-12  3:06 Bug: bug&fix for org-compile-file on Windows Mirko Vukovic
2016-12-12  7:48 ` Nicolas Goaziou
2016-12-12 18:39   ` Michael Alan Dorman [this message]
2017-07-03  4:43     ` org ELPA broken 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=87wpf52drk.fsf_-_@jaunder.io \
    --to=mdorman@jaunder.io \
    --cc=emacs-orgmode@gnu.org \
    --cc=mail@nicolasgoaziou.fr \
    /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).