all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Jens Lechtenboerger <lechten@wi.uni-muenster.de>
To: Johannes Brauer <brauer@nordakademie.de>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>,
	John Kitchin <jkitchin@andrew.cmu.edu>
Subject: Re: Two bibliography slides using org-reveal
Date: Fri, 26 Jul 2019 21:21:36 +0200	[thread overview]
Message-ID: <87zhl0a9fj.fsf@localhost> (raw)
In-Reply-To: <1472697E-0015-4CF8-8DB0-554512C1162A@nordakademie.de> (Johannes Brauer's message of "Fri, 26 Jul 2019 13:08:18 +0000")

Johannes Brauer <brauer@nordakademie.de> writes:

> GET file:///Users/jb/Downloads/org-re-reveal-ref-master/reveal.js/lib/js/head.min.js net::ERR_FILE_NOT_FOUND  README.html:173 
>
> Is this a relevant message?

Hi Johannes,

that message appears for newer versions of reveal.js (but does not
hurt).  You can avoid it by customizing variable
org-re-reveal-script-files to remove lib/js/head.min.js, which does not
seem to exist for your version.

Alternatively, if you added (require 'org-re-reveal) in your ~/.emacs,
you could add the following:
(setq org-re-reveal-script-files '("js/reveal.js"))

Best wishes
Jens

  reply	other threads:[~2019-07-26 19:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-25 12:18 Two bibliography slides using org-reveal Johannes Brauer
2019-07-25 12:41 ` Fraga, Eric
2019-07-25 13:54   ` Johannes Brauer
2019-07-25 13:59     ` John Kitchin
2019-07-25 14:27       ` Johannes Brauer
2019-07-25 17:00       ` Jens Lechtenboerger
2019-07-25 21:44         ` Johannes Brauer
2019-07-26  6:43           ` Jens Lechtenboerger
2019-07-26 13:08             ` Johannes Brauer
2019-07-26 19:21               ` Jens Lechtenboerger [this message]
2019-07-26 21:19                 ` Johannes Brauer
2019-07-31 21:19                   ` Two bibliography slides using org-reveal - new prblem Johannes Brauer
2019-07-31 22:16                     ` Two bibliography slides using org-reveal - SORRY no new problem Johannes Brauer

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87zhl0a9fj.fsf@localhost \
    --to=lechten@wi.uni-muenster.de \
    --cc=brauer@nordakademie.de \
    --cc=emacs-orgmode@gnu.org \
    --cc=jkitchin@andrew.cmu.edu \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.