callouts not working with deck.js backend

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
14 messages Options
Reply | Threaded
Open this post in threaded view
|

callouts not working with deck.js backend

wimalopaan
Hi all,

trying to render the following example with deck.js backend gives very unpleasing results for the callouts.

They aren't rendered as circled numbers but as (1), (2) ...
And the appear on a separate line, that's very disturbing!

Anything I can do?

--
Wilhelm  

= Test
wimalopaan <x@y.de>
:lang: de
:toc:
:numbered:
:src_numbered:
:description: A test presentation
:icons: font
:sectanchors:
:sectlinks:
:experimental:
:source-highlighter: coderay
:coderay-css: class
:status:
:menu:
:navigation:
:split:
:goto:
:deckjs_theme: swiss
:showtitle:
//:linenums:
//:coderay-linenums-mode: table

== Chap1

belongs to chap1

[source,cpp]
----
#include "bla"

int main() // <1>
{
}
----
<1> test

bla

----
a line <1>
a line <2>
----
<1> bla
<2> blub

[source,java]
----
class {
      public static void main(String[] args) { <1>
      }
}
----
<1> xyz

Reply | Threaded
Open this post in threaded view
|

Re: callouts not working with deck.js backend

mojavelinux
Administrator
Thanks for the heads up. The problem was that the CSS was missing for the callout bullets in the deckjs backend. I just added it in. Update master and it should look good.

-Dan


On Mon, Feb 10, 2014 at 8:31 AM, wimalopaan [via Asciidoctor :: Discussion] <[hidden email]> wrote:
Hi all,

trying to render the following example with deck.js backend gives very unpleasing results for the callouts.

They aren't rendered as circled numbers but as (1), (2) ...
And the appear on a separate line, that's very disturbing!

Anything I can do?

--
Wilhelm  

= Test
wimalopaan <[hidden email]>
:lang: de
:toc:
:numbered:
:src_numbered:
:description: A test presentation
:icons: font
:sectanchors:
:sectlinks:
:experimental:
:source-highlighter: coderay
:coderay-css: class
:status:
:menu:
:navigation:
:split:
:goto:
:deckjs_theme: swiss
:showtitle:
//:linenums:
//:coderay-linenums-mode: table

== Chap1

belongs to chap1

[source,cpp]
----
#include "bla"

int main() // <1>
{
}
----
<1> test

bla

----
a line <1>
a line <2>
----
<1> bla
<2> blub

[source,java]
----
class {
      public static void main(String[] args) { <1>
      }
}
----
<1> xyz




If you reply to this email, your message will be added to the discussion below:
http://discuss.asciidoctor.org/callouts-not-working-with-deck-js-backend-tp1408.html
To start a new topic under Asciidoctor :: Discussion, email [hidden email]
To unsubscribe from Asciidoctor :: Discussion, click here.
NAML



--
Reply | Threaded
Open this post in threaded view
|

Re: callouts not working with deck.js backend

wimalopaan
Hi Dan,

thank you for your response.
I just downloaded master, built the gem and installed it.

But unfortunately I'm missing something:

⏚ 1& [lmeier:~/asciidoctor/asciidoctor-master] $ asciidoctor --version
/usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:135:in `require': cannot load such file -- asciidoctor (LoadError)
        from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:135:in `rescue in require'
        from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:144:in `require'
        from /home/lmeier/.gem/ruby/2.1.0/gems/asciidoctor-1.5.0.preview/bin/asciidoctor:8:in `<top (required)>'
        from /usr/bin/asciidoctor:23:in `load'
        from /usr/bin/asciidoctor:23:in `<main>'
⏚ 1& [lmeier:~/asciidoctor/asciidoctor-master] 1 $

This is the list of installed gems:

 1& [lmeier:~/asciidoctor/asciidoctor-master] $ gem list -a

*** LOCAL GEMS ***

asciidoctor (1.5.0.preview, 0.1.4)
bigdecimal (1.2.3)
bundler (1.5.2)
celluloid (0.15.2)
chunky_png (1.2.9)
coderay (1.1.0)
compass (0.12.2)
em-websocket (0.5.0)
eventmachine (1.0.3)
ffi (1.9.3)
formatador (0.2.4)
fssm (0.2.10)
guard (2.3.0)
guard-livereload (2.1.1)
haml (4.0.5)
http_parser.rb (0.5.3)
io-console (0.4.2)
json (1.8.1)
listen (2.4.0)
lumberjack (1.0.4)
method_source (0.8.2)
minitest (4.7.5)
multi_json (1.8.4)
posix-spawn (0.3.8)
pry (0.9.12.6)
psych (2.0.2)
pygments.rb (0.5.4)
rake (10.1.0)
rb-fsevent (0.9.4)
rb-inotify (0.9.3)
rb-pygments (0.1.0)
-rdoc (4.1.0)
require (0.2.7)
sass (3.2.14)
slim (2.0.2)
slop (3.4.7)
temple (0.6.7)
test-unit (2.1.0.0)
thor (0.18.1)
tilt (2.0.0)
timers (1.1.0)
yajl-ruby (1.1.0)
zurb-foundation (4.3.2)
⏚ 1& [lmeier:~/asciidoctor/asciidoctor-master] $

Reply | Threaded
Open this post in threaded view
|

Re: callouts not working with deck.js backend

wimalopaan
After uninstalling all asciidoctor versions (0.1.4 and 1.5.0-preview) and reinstalling asciidoctor-0.1.4 I now get the following error (see below): how can I fix that?

$ asciidoctor -a data-uri -T ~/asciidoctor/asciidoctor-backends-master/haml/deckjs test.adoc
/usr/lib/ruby/2.1.0/fileutils.rb:250:in `mkdir': Permission denied @ dir_s_mkdir - /usr/lib/ruby/gems/2.1.0/extensions/x86_64-linux (Errno::EACCES)
        from /usr/lib/ruby/2.1.0/fileutils.rb:250:in `fu_mkdir'
        from /usr/lib/ruby/2.1.0/fileutils.rb:224:in `block (2 levels) in mkdir_p'
        from /usr/lib/ruby/2.1.0/fileutils.rb:222:in `reverse_each'
        from /usr/lib/ruby/2.1.0/fileutils.rb:222:in `block in mkdir_p'
        from /usr/lib/ruby/2.1.0/fileutils.rb:208:in `each'
        from /usr/lib/ruby/2.1.0/fileutils.rb:208:in `mkdir_p'
        from /usr/lib/ruby/2.1.0/rubygems/ext/builder.rb:210:in `write_gem_make_out'
        from /usr/lib/ruby/2.1.0/rubygems/ext/builder.rb:132:in `build_error'
        from /usr/lib/ruby/2.1.0/rubygems/ext/builder.rb:171:in `rescue in build_extension'
        from /usr/lib/ruby/2.1.0/rubygems/ext/builder.rb:156:in `build_extension'
        from /usr/lib/ruby/2.1.0/rubygems/ext/builder.rb:198:in `block in build_extensions'
        from /usr/lib/ruby/2.1.0/rubygems/ext/builder.rb:195:in `each'
        from /usr/lib/ruby/2.1.0/rubygems/ext/builder.rb:195:in `build_extensions'
        from /usr/lib/ruby/2.1.0/rubygems/specification.rb:1436:in `block in build_extensions'
        from /usr/lib/ruby/2.1.0/rubygems/user_interaction.rb:45:in `use_ui'
        from /usr/lib/ruby/2.1.0/rubygems/specification.rb:1434:in `build_extensions'
        from /usr/lib/ruby/2.1.0/rubygems/stub_specification.rb:60:in `build_extensions'
        from /usr/lib/ruby/2.1.0/rubygems/basic_specification.rb:56:in `contains_requirable_file?'
        from /usr/lib/ruby/2.1.0/rubygems/specification.rb:925:in `block in find_inactive_by_path'
        from /usr/lib/ruby/2.1.0/rubygems/specification.rb:924:in `each'
        from /usr/lib/ruby/2.1.0/rubygems/specification.rb:924:in `find'
        from /usr/lib/ruby/2.1.0/rubygems/specification.rb:924:in `find_inactive_by_path'
        from /usr/lib/ruby/2.1.0/rubygems.rb:185:in `try_activate'
        from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:132:in `rescue in require'
        from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:144:in `require'
        from /home/lmeier/.gem/ruby/2.1.0/gems/asciidoctor-0.1.4/lib/asciidoctor/cli/options.rb:172:in `parse!'
        from /home/lmeier/.gem/ruby/2.1.0/gems/asciidoctor-0.1.4/lib/asciidoctor/cli/options.rb:32:in `parse!'
        from /home/lmeier/.gem/ruby/2.1.0/gems/asciidoctor-0.1.4/lib/asciidoctor/cli/invoker.rb:20:in `initialize'
        from /home/lmeier/.gem/ruby/2.1.0/gems/asciidoctor-0.1.4/bin/asciidoctor:12:in `new'
        from /home/lmeier/.gem/ruby/2.1.0/gems/asciidoctor-0.1.4/bin/asciidoctor:12:in `<top (required)>'
        from /home/lmeier/.gem/ruby/2.1.0/bin/asciidoctor:23:in `load'
        from /home/lmeier/.gem/ruby/2.1.0/bin/asciidoctor:23:in `<main>'

Reply | Threaded
Open this post in threaded view
|

Re: callouts not working with deck.js backend

wimalopaan
Sorry, please forget the last posting about reinstalling asciidoctor-0.1.4!

Asciidoctor-0.1.4 runs as before after uninstalling asciidoctor-1.5.0.preview.

But asciidoctor-1.5.0.preview still gives the error as posted previously.

Any hints?

--
Wilhelm
Reply | Threaded
Open this post in threaded view
|

Re: callouts not working with deck.js backend

mojavelinux
Administrator

Good to hear you got things working!

The error message you posted seems to be happening because you were running it from a directory to which you don't have write access.

That said, the error message isn't very descriptive and thus could be improved to make the user experience more friendly. You are welcome to file an issue to improve that message so we don't forget to improve it.

I take it the callouts are working then?

-Dan

On Feb 11, 2014 12:26 AM, "wimalopaan [via Asciidoctor :: Discussion]" <[hidden email]> wrote:
Sorry, please forget the last posting about reinstalling asciidoctor-0.1.4!

Asciidoctor-0.1.4 runs as before after uninstalling asciidoctor-1.5.0.preview.

But asciidoctor-1.5.0.preview still gives the error as posted previously.

Any hints?

--
Wilhelm


If you reply to this email, your message will be added to the discussion below:
http://discuss.asciidoctor.org/callouts-not-working-with-deck-js-backend-tp1408p1413.html
To start a new topic under Asciidoctor :: Discussion, email [hidden email]
To unsubscribe from Asciidoctor :: Discussion, click here.
NAML
Reply | Threaded
Open this post in threaded view
|

Re: callouts not working with deck.js backend

wimalopaan
Hi Dan,

thanks for your answer.
But unfortunately I still get the following error with 1.5.0:

$ asciidoctor --version
/usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:135:in `require': cannot load such file -- asciidoctor (LoadError)
        from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:135:in `rescue in require'
        from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:144:in `require'
        from /home/lmeier/.gem/ruby/2.1.0/gems/asciidoctor-1.5.0.preview/bin/asciidoctor:8:in `<top (required)>'
        from /usr/bin/asciidoctor:23:in `load'
        from /usr/bin/asciidoctor:23:in `<main>'
⏚ 1& [lmeier:~/asciidoctor/asciidoctor-master] 1 $
Reply | Threaded
Open this post in threaded view
|

Re: callouts not working with deck.js backend

mojavelinux
Administrator
What seems to have happened is that the gem got removed, but the bin stub (the asciidoctor script itself) did not.

You can take two ways to get out of it, one more drastic than the other.

1. You can remove your ~/.gems directory so that you just start with a clean environment.

2. You need to remove references to asciidoctor in ~/.gems so that you can install Asciidoctor fresh.

 $ find ~/.gems -name 'asciidoctor*' -exec rm -Rf {} \;

Personally, this is why I strongly recommend using RVM (http://rvm.io) when using Ruby. RVM helps you manage gems in isolation so at the very worst, you only ever have to remove a single "collection" (or project-specific environment) when cleaning up gems. Each gemset is sort of like a workbench.

For instance, here's how I work with Ruby. I'm going to be testing out the deck.js backend. So, I have a gemset for "asciidoctor-user".

 $ rvm use 2.1@asciidoctor-user
 $ asciidoctor --version
 # Asciidoctor 0.1.4 [http://asciidoctor.org]

Then, when I go back to development, I type

 $ rvm use 2.1@asciidoctor-dev
 $ asciidoctor --version
 # bash: asciidoctor: command not found... <1>

<1> It's not found because I'm using the development branch, so only the dependencies of Asciidoctor are installed.

Best of luck!

-Dan


On Tue, Feb 11, 2014 at 12:55 AM, wimalopaan [via Asciidoctor :: Discussion] <[hidden email]> wrote:
Hi Dan,

thanks for your answer.
But unfortunately I still get the following error with 1.5.0:

$ asciidoctor --version
/usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:135:in `require': cannot load such file -- asciidoctor (LoadError)
        from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:135:in `rescue in require'
        from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:144:in `require'
        from /home/lmeier/.gem/ruby/2.1.0/gems/asciidoctor-1.5.0.preview/bin/asciidoctor:8:in `<top (required)>'
        from /usr/bin/asciidoctor:23:in `load'
        from /usr/bin/asciidoctor:23:in `<main>'
⏚ 1& [lmeier:~/asciidoctor/asciidoctor-master] 1 $


If you reply to this email, your message will be added to the discussion below:
http://discuss.asciidoctor.org/callouts-not-working-with-deck-js-backend-tp1408p1415.html
To start a new topic under Asciidoctor :: Discussion, email [hidden email]
To unsubscribe from Asciidoctor :: Discussion, click here.
NAML



--
Reply | Threaded
Open this post in threaded view
|

Re: callouts not working with deck.js backend

wimalopaan
Well, I tried the drastic way and removed ~/.gem directory. The I reinstalled the 1.5.0.preview.

The error remains:

$ asciidoctor -a data-uri -T ~/asciidoctor/asciidoctor-backends-master/haml/deckjs -v test.adoc
/usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require': cannot load such file -- asciidoctor (LoadError)
        from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require'
        from /home/lmeier/.gem/ruby/2.1.0/gems/asciidoctor-1.5.0.preview/bin/asciidoctor:8:in `<top (required)>'
        from /home/lmeier/.gem/ruby/2.1.0/bin/asciidoctor:23:in `load'
        from /home/lmeier/.gem/ruby/2.1.0/bin/asciidoctor:23:in `<main>'

Can I provide you with more debugging information?

Deleting 1.5.0 and installing 0.1.4 works then.

--
Wilhelm
Reply | Threaded
Open this post in threaded view
|

Re: callouts not working with deck.js backend

mojavelinux
Administrator
Yep, it would be helpful if you ran the following commands:

$ which asciidoctor
$ find ~/.gem/ruby/2.1.0
$ ruby -e "require 'pp'; pp RbConfig::CONFIG"

This still seems like a fairly run of the mill gem error. The fact that you can run 0.1.4 but not 1.5.0.preview.1 tells me it is finding 0.1.4 already installed somewhere, but when you install 1.5.0.preview.1 then where ever it is looking (perhaps in the system) it's not finding that version. Either way, the LOAD_PATH is messed up somehow.

-Dan


On Tue, Feb 11, 2014 at 1:46 AM, wimalopaan [via Asciidoctor :: Discussion] <[hidden email]> wrote:
Well, I tried the drastic way and removed ~/.gem directory. The I reinstalled the 1.5.0.preview.

The error remains:

$ asciidoctor -a data-uri -T ~/asciidoctor/asciidoctor-backends-master/haml/deckjs -v test.adoc
/usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require': cannot load such file -- asciidoctor (LoadError)
        from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require'
        from /home/lmeier/.gem/ruby/2.1.0/gems/asciidoctor-1.5.0.preview/bin/asciidoctor:8:in `<top (required)>'
        from /home/lmeier/.gem/ruby/2.1.0/bin/asciidoctor:23:in `load'
        from /home/lmeier/.gem/ruby/2.1.0/bin/asciidoctor:23:in `<main>'

Can I provide you with more debugging information?

Deleting 1.5.0 and installing 0.1.4 works then.

--
Wilhelm



If you reply to this email, your message will be added to the discussion below:
http://discuss.asciidoctor.org/callouts-not-working-with-deck-js-backend-tp1408p1417.html
To start a new topic under Asciidoctor :: Discussion, email [hidden email]
To unsubscribe from Asciidoctor :: Discussion, click here.
NAML



--
Reply | Threaded
Open this post in threaded view
|

Re: callouts not working with deck.js backend

mojavelinux
Administrator
In reply to this post by wimalopaan
Another thing you can try is to modify /home/lmeier/.gem/ruby/2.1.0/gems/asciidoctor-1.5.0.preview/bin/asciidoctor by adding the following below the first line:

require 'pp'
pp $LOAD_PATH

-Dan


On Tue, Feb 11, 2014 at 2:25 AM, Dan Allen <[hidden email]> wrote:
Yep, it would be helpful if you ran the following commands:

$ which asciidoctor
$ find ~/.gem/ruby/2.1.0
$ ruby -e "require 'pp'; pp RbConfig::CONFIG"

This still seems like a fairly run of the mill gem error. The fact that you can run 0.1.4 but not 1.5.0.preview.1 tells me it is finding 0.1.4 already installed somewhere, but when you install 1.5.0.preview.1 then where ever it is looking (perhaps in the system) it's not finding that version. Either way, the LOAD_PATH is messed up somehow.

-Dan


On Tue, Feb 11, 2014 at 1:46 AM, wimalopaan [via Asciidoctor :: Discussion] <[hidden email]> wrote:
Well, I tried the drastic way and removed ~/.gem directory. The I reinstalled the 1.5.0.preview.

The error remains:

$ asciidoctor -a data-uri -T ~/asciidoctor/asciidoctor-backends-master/haml/deckjs -v test.adoc
/usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require': cannot load such file -- asciidoctor (LoadError)
        from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require'
        from /home/lmeier/.gem/ruby/2.1.0/gems/asciidoctor-1.5.0.preview/bin/asciidoctor:8:in `<top (required)>'
        from /home/lmeier/.gem/ruby/2.1.0/bin/asciidoctor:23:in `load'
        from /home/lmeier/.gem/ruby/2.1.0/bin/asciidoctor:23:in `<main>'

Can I provide you with more debugging information?

Deleting 1.5.0 and installing 0.1.4 works then.

--
Wilhelm



If you reply to this email, your message will be added to the discussion below:
http://discuss.asciidoctor.org/callouts-not-working-with-deck-js-backend-tp1408p1417.html
To start a new topic under Asciidoctor :: Discussion, email [hidden email]
To unsubscribe from Asciidoctor :: Discussion, click here.
NAML






--
Reply | Threaded
Open this post in threaded view
|

Re: callouts not working with deck.js backend

wimalopaan
Ok, inserted the two lines. Now I get:

asciidoctor -v
["/usr/lib/ruby/site_ruby/2.1.0",
 "/usr/lib/ruby/site_ruby/2.1.0/x86_64-linux",
 "/usr/lib/ruby/site_ruby",
 "/usr/lib/ruby/vendor_ruby/2.1.0",
 "/usr/lib/ruby/vendor_ruby/2.1.0/x86_64-linux",
 "/usr/lib/ruby/vendor_ruby",
 "/usr/lib/ruby/2.1.0",
 "/usr/lib/ruby/2.1.0/x86_64-linux"]
/usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:135:in `require': cannot load such file -- asciidoctor (LoadError)
        from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:135:in `rescue in require'
        from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:144:in `require'
        from /home/lmeier/.gem/ruby/2.1.0/gems/asciidoctor-1.5.0.preview/bin/asciidoctor:8:in `<top (required)>'
        from /home/lmeier/.gem/ruby/2.1.0/bin/asciidoctor:27:in `load'
        from /home/lmeier/.gem/ruby/2.1.0/bin/asciidoctor:27:in `<main>'

-------------

⌁66% 1& [lmeier:~/Lehre/Eigene/Prog2NeuesKonzept/ppc/doc] ppc(7) 1 ‡ which asciidoctor
/home/lmeier/.gem/ruby/2.1.0/bin/asciidoctor
^[[A⌁65% 1& [lmeier:~/Lehre/Eigene/Prog2NeuesKonzept/ppc/doc] ppc(7) ‡ which -a asciidoctor
/home/lmeier/.gem/ruby/2.1.0/bin/asciidoctor
/usr/bin/asciidoctor
⌁65% 1& [lmeier:~/Lehre/Eigene/Prog2NeuesKonzept/ppc/doc] ppc(7) ‡

-----------------

The configuration:

c.txt

------------------

find output:

f.txt


Reply | Threaded
Open this post in threaded view
|

Re: callouts not working with deck.js backend

mojavelinux
Administrator
I see two things. First, I see that you have an asciidoctor at /usr/bin/asciidoctor. That means you have residual Asciidoctor installation somewhere on your system. Maybe a RPM or DEB package? Or perhaps you installed it into the system at some point?

The second problem, which is really the heart of the error, is that your asciidoctor-1.5.0.preview installation only has the bin/ directory:

/home/lmeier/.gem/ruby/2.1.0/gems/asciidoctor-1.5.0.preview
/home/lmeier/.gem/ruby/2.1.0/gems/asciidoctor-1.5.0.preview/bin
/home/lmeier/.gem/ruby/2.1.0/gems/asciidoctor-1.5.0.preview/bin/asciidoctor-safe
/home/lmeier/.gem/ruby/2.1.0/gems/asciidoctor-1.5.0.preview/bin/asciidoctor
/home/lmeier/.gem/ruby/2.1.0/gems/asciidoctor-1.5.0.preview/LICENSE

This gem appears to be a package you created locally, because the preview release on rubygems.org is 1.5.0.preview.1 (notice the trailing .1). My guess here is that the gem you are using to install is incomplete.

I'm going to be releasing 1.5.0.preview.2 before the end of the week. Perhaps you'd just like to wait to use Asciidoctor 1.5.0 when I do that release. Otherwise, check how you are building the gem file and make sure that when you build it, it includes all the files. Inside the asciidoctor directory, run:

 $ rake build

You can check the contents of the gem using `gem unpack`.

Cheers,

-Dan


On Tue, Feb 11, 2014 at 2:44 AM, wimalopaan [via Asciidoctor :: Discussion] <[hidden email]> wrote:
Ok, inserted the two lines. Now I get:

asciidoctor -v
["/usr/lib/ruby/site_ruby/2.1.0",
 "/usr/lib/ruby/site_ruby/2.1.0/x86_64-linux",
 "/usr/lib/ruby/site_ruby",
 "/usr/lib/ruby/vendor_ruby/2.1.0",
 "/usr/lib/ruby/vendor_ruby/2.1.0/x86_64-linux",
 "/usr/lib/ruby/vendor_ruby",
 "/usr/lib/ruby/2.1.0",
 "/usr/lib/ruby/2.1.0/x86_64-linux"]
/usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:135:in `require': cannot load such file -- asciidoctor (LoadError)
        from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:135:in `rescue in require'
        from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:144:in `require'
        from /home/lmeier/.gem/ruby/2.1.0/gems/asciidoctor-1.5.0.preview/bin/asciidoctor:8:in `<top (required)>'
        from /home/lmeier/.gem/ruby/2.1.0/bin/asciidoctor:27:in `load'
        from /home/lmeier/.gem/ruby/2.1.0/bin/asciidoctor:27:in `<main>'

-------------

⌁66% 1& [lmeier:~/Lehre/Eigene/Prog2NeuesKonzept/ppc/doc] ppc(7) 1 ‡ which asciidoctor
/home/lmeier/.gem/ruby/2.1.0/bin/asciidoctor
^[[A⌁65% 1& [lmeier:~/Lehre/Eigene/Prog2NeuesKonzept/ppc/doc] ppc(7) ‡ which -a asciidoctor
/home/lmeier/.gem/ruby/2.1.0/bin/asciidoctor
/usr/bin/asciidoctor
⌁65% 1& [lmeier:~/Lehre/Eigene/Prog2NeuesKonzept/ppc/doc] ppc(7) ‡

-----------------

The configuration:

c.txt

------------------

find output:

f.txt





If you reply to this email, your message will be added to the discussion below:
http://discuss.asciidoctor.org/callouts-not-working-with-deck-js-backend-tp1408p1420.html
To start a new topic under Asciidoctor :: Discussion, email [hidden email]
To unsubscribe from Asciidoctor :: Discussion, click here.
NAML



--
Reply | Threaded
Open this post in threaded view
|

Re: callouts not working with deck.js backend

wimalopaan
Thank you for your patience!

rake build fails:
----
[lmeier:~/asciidoctor/asciidoctor-master] 1 $ rake  build
LANG: de_DE.UTF-8
rake aborted!
Don't know how to build task 'build'

(See full trace by running task with --trace)
----

So I'll wait until you release the preview.2.

Thank you!
--
Wilhelm