Specifying Environment variable not working in browser

[jcayouette]

I am trying to setup specific rules for a github environment + asciidoctorjs plugin. When on github or when viewing adoc files on a local system using the asciidoctorjs browser extension I would like to prevent displaying includes and use cross references instead:

include::

I have the following so far:

ifndef::env-github,ENV?[]
include::quickstart_overview.adoc[leveloffset=1]
endif::[]

ifdef::env-github,backend-html5[]
<<quickstart_overview.adoc#overview, Overview>>
endif::[]

This works for github. But when I view the same file in a browser using the asciidoctorjs extension I get the following result:

quickstart_overview.adoc
Overview

Which env should I specify in the first ifndef to prevent loading of includes in asciidoctorjs within the browser?

Is this the correct way to go about this? Or could you suggest an alternative?

Best!

[ggrossetie]

Hello @jcayouette I believe your issue is related to the Asciidoctor browser extension ? If so could you please open your issue on https://github.com/asciidoctor/asciidoctor-browser-extension ? Thanks :smiley:

[mojavelinux]

On top of that, environment variables are not accessible to the document.

[ggrossetie]

Which env should I specify in the first ifndef to prevent loading of includes in asciidoctorjs within the browser?

I guess you could define an attribute in the browser extension:

@jcayouette Does it answer your question ? Can we close this issue ?

[ggrossetie]

Closing, please join http://gitter.im/asciidoctor/asciidoctor.js if we didn't answer your question.

[yoarch]

Hi, I don't want to necro bump this post but I have the exact same issue. I need the {user-home} environment variable in my asciidoc scripts, it works perfectly except when I render with Brave (close to Chromium). Tried to add environment variable in the asciidoctor.js as suggested but unsuccessful. Any more ideas?

[ggrossetie]

@yoarch Environment variables are not available in a browser environment. The value of the built-in attribute user-home in a browser environment will be ..

You will need to explicitly define the value using a custom attribute: my-user-home=/home/guillaume

[yoarch]

Hi Guillaume, Thanks for the reply. Yes, indeed. It works. Thanks for your time.

[mojavelinux]

@Mogztter It definitely seems like it should be possible to set user-home manually using the options page. Do you see a problem with that idea?

[ggrossetie]

@mojavelinux I don't recall, is it possible to override a built-in attribute? https://github.com/asciidoctor/asciidoctor/blob/4284a176fac29bdde62288f13e7ebb18defeb9aa/lib/asciidoctor/document.rb#L374

[mojavelinux]

Oh, duh. You're right. Certain built-in attributes cannot be overridden even from the commandline. I think it should be possible to override user-home because we cannot be sure the inherent value is correct. Let's take that up in core.

[ggrossetie]

Follow-up issue: https://github.com/asciidoctor/asciidoctor/issues/3732