I'd like to to use stylesdir and stylesheet attributes to override default styles applied to my document by the JCEF Browser. This, however, only works if CSS files are stored locally. My company has an internal repo, where all asciidoc related files are stored (e.g. css, common includes etc.) - this allows everyone to start working on the document with almost zero configuration.

Is there a way to specify placement of CSS files like this

:stylesdir: https://internal.asciidoc.repository/asciidoc/css/asciidoc-skins
:stylesheet: adoc-colony.css

instead of this

:stylesdir: ./
:stylesheet: adoc-colony.css

Good to hear that! As usual I'll keep this version for a few more days as a pre-release before I promote it to a regular release. This allows you and other users of this pre-release to report bugs regarding this and other features that are part of the pre-release.

If I should forget to promote it to a regular, please ping me with a short comment in this ticket.

Pre-release 0.31.32 supports also the shorter version where stylesdir is not set in the document.

= Bold

This is bold.

== Bold ?

Bold again ?

<!-- go to File -> Settings -> Plugins -> AsciiDoc and type in the version number you see --> AsciiDoc Plugin Version

0.30.41

IDE Name and Version

WebStorm 2019.3.3
Build #WS-193.6494.34, built on February 11, 2020
Runtime version: 11.0.5+10-b520.38 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Linux 4.15.0-88-generic
GC: ParNew, ConcurrentMarkSweep
Memory: 1931M
Cores: 8
Registry: debugger.watches.in.variables=false
Non-Bundled Plugins: BashSupport, net.seesharpsoft.intellij.plugins.csv, org.asciidoctor.intellij.asciidoc, org.jetbrains.plugins.slim, org.toml.lang

IntelliJ is phasing out JavaFX in favor of JCEF; there is a near to nothing chance for this to be fixed in JavaFX.

This issue has only been observed on JavaFX, therefore I close this issue. Please comment if you disagree.

Apply a reformat to the following document:

= Title

Some text here.
Some text about CSS3.
Some more text.

Expected: document is not modified.

Actual: document is formatted this way:

= Title

Some text here.
Some text about CSS3. Some more text.

<!-- go to File -> Settings -> Plugins -> AsciiDoc and type in the version number you see --> AsciiDoc Plugin Version: 0.30.59.1

<!-- go to Help -> About, hover with the mouse over the logo - then a small icon to click on appears. Click on it to copy your IDE version to your clipboard and paste the contents of your clipboard here --> IDE Name and Version: RubyMine 2020.1 Build #RM-201.6668.156, built on April 14, 2020 Runtime version: 11.0.6+8-b765.25 amd64 VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o Windows 10 10.

A dot after a number is ambiguous. It could be the end of a sentence or not. As it is ambiguous, the plugin will keep it "as is". Both two texts will not be reformatted and be kept as is.

Some text here.
Some text about CSS3.
Some more text.

and

Some text here.
Some text about CSS3. Some more text.

This will be part of the next upcoming release.

... like implemented by the Markdown plugin. Users will be able to disable it in the settings.

The JCEF preview now has a CSP.

<!-- Please fill out the following if you report a problem. It will help to find the cause of the issue. Otherwise please delete this text.

First describe the behavior you see in the IDE or plugin (either a problem or a bug).

Then describe the behavior you expect or want to see in the IDE or plugin.

Please provide a minimal Asciidoctor example.
It helps to reproduce the problem/feature request!

Thanks! -->

Experiencing an IDE-error cf. picture, in the manual documentation itself, saying

include file not found: doctoolchain/build/docs/contributors/manual/04_further_reading.adoc 
(doctoolchain/src/docs/manual/feedback.adoc, line 6)
(uri:classloader:/gems/asciidoctor-2.0.10/lib/asciidoctor/reader.rb:preprocess_include_directive)

<!-- go to File -> Settings -> Plugins -> AsciiDoc and type in the version number you see --> AsciiDoc Plugin Version: 0.31.27

<!-- go to Help -> About, hover with the mouse over the logo - then a small icon to click on appears. Click on it to copy your IDE version to your clipboard and paste the contents of your clipboard here --> IDE Name and Version: IntelliJ 2020.2.1

The next upcoming release highlight errors in the parent files on the correct line, event for nested includes.

I've added support for linkcss in the preview in the pre-release version 0.31.31. The example provided by @mojavelinux works now both in the JavaFX and the JCEF preview.

I've also updated the docs: https://intellij-asciidoc-plugin.ahus1.de/docs/users-guide/features/advanced/stylesheets.html

@GauntletPL - please give it a try. If the docs need improvement, please comment here or provide a pull request.

The pre-release of the plugin is available from GitHub releases and the IntelliJ AsciiDoc EAP repository.

@GauntletPL - thanks for reporting this. This is a reasonable scenario that the plugin should support.

As the plugin uses the "embedded" Asciidoctor converter and later adds a custom header/footer, some feature that affect header/footer might not be supported yet.

A quick test on my side revealed that linkcss is not supported by the plugin, yet.

I'll see after it that the preview supports this in an upcoming release.

This class has been deprecated for a while. I don't know about alternatives.

The strategy for keycloak-dropwizard-bearermodule: I'll internalize the class into the library once it is no longer available in the main keycloak distribution.

I hope this answers your question. Please close this ticket if it does.

asciidoctorj-diagram hasn't been released yet, therefore IntelliJ hasn't upgraded yet. No harm done!

As you pulled release 2.0.3, the master of asciidoctorj-diagram will probably fail to build.

Depending on when you plan to publish a new 2.0.4 version it is up to @robertpanzer to decide if he wants to wait, or to roll back the master to 2.0.2.

Hi @schittli, thanks for reporting this. The behavior you see is the "header" of an AsciiDoc document.

The two lines of text just after a title (the one with the single =) are used for revision and author information. They will never show up in the preview.

The first real content will start after two lines of text OR after a blank line. If you add attributes into the header these don't count as lines. A full example looks like this:

= The Dangerous and Thrilling Documentation Chronicles
Kismet Chameleon <[email protected]>
v1.0, October 2, 2013: First incarnation

I hope this explains the behavior you see.

Unfortunately the AsciiDoclet snippets can't show syntax highlighting in the editor. If you copy your example to an AsciiDoc file you could at least see some syntax highlighting. I would like to name an automated rule how to detect such a situation, but unfortunately I can't.

What Happens

1. AsciiDoc presents a banner indicating an advanced JCEF preview is available.
2. When you click on the "Yes, tell me more!" link, it results in a 404

Excepted

The correct link should open.

The link is pointing to: https://intellij-asciidoc-plugin.ahus1.de/docs/users-guide/preview/jcef-preview.html But the correct link is: https://intellij-asciidoc-plugin.ahus1.de/docs/users-guide/features/preview/jcef-preview.html

Looks like it is this line that needs fixing. If you would like a PR, I can submit one. But it seems to me a PR would be a lot more work for you given the simplicity of the fix.

Versions

AsciiDoc Plugin Version: 0.31.28

IDE Name and Version: IntelliJ IDEA 2020.2.2 (Ultimate Edition) Build #IU-202.7319.50, built on September 14, 2020

Thanks, I was wondering if the notification was valid. It appears it is. As the next release will contain the fix, I'll close this issue then.

Thanks, will be fixed in next upcoming version.

I wonder: what runtime did you use for your IDE? The pre-packaged runtime of 2020.2.2 should support JCEF out of the box.

Hi @JMikeP - did you have a chance to tackle the first question:

Did you test the extension you want to use with the latest version of IntelliJ and the AsciiDoc plugin?

Please let me know if you into issues.

There is unfortunately a semantic difference between xref:b.adoc[] and xref:bar:foo:b.adoc[]:

• the short form will link to the page in the current component's version
• the long form will link to the page in the lastest component's version
• there is an "extra long form xref:{page-version}@bar:foo:b.adoc[] that would link to the page in the current component's version

If you would use the long version in all your docs, the user will switch to the latest release documentation (even after they selected a specific version). This would make your documentation quite unusable.

The conclusion I came to:

• links should always be as short as possible when navigating within a component
• components should be defined on the level where you create major/minor releases
• when users would navigate between modules and expect to stay within the version they have selected, these modules should be part of the same component

I haven't seen that written down as a best practice anywhere yet, maybe I should raise that to the maintainers.

See #418 for a previous discussion, especially https://github.com/asciidoctor/asciidoctor-intellij-plugin/issues/418#issuecomment-615989451. Dan writes:

If you want to specify the component name, but stay in the current version, you can use:

xref:{page-version}@component-name::index.adoc[]

While this is a technically correct syntax, this is quite hard to read/maintain IMHO.

The three semantically identical forms to toggle between would then be:

xref:b.adoc[]
xref:foo:b.adoc[]
xref:{page-version}@bar:foo:b.adoc[]

I'm a little hesitant to allow rotating between these link types. That's probably the reason why I haven't touched it yet.

I'd like to hear your thoughts.

@ari: it uses the PATH environment of the IDE when rendering the preview.

You can set a full path to the executable using an attribute (either in the plugin's settings or in the document) as described in the FAQ.

:mermaid: ./node_modules/.bin/mmdc
:phantomjs_2: ./node_modules/.bin/phantomjs


[mermaid]
----
classDiagram      
      class Animal {
          +int age
    }
      
----

Reading the notes in https://github.com/asciidoctor/asciidoctor-diagram/issues/275 this attributes will change in the upcoming asciidoctorj-diagram 2.0.3

@rdmueller - there seem to be some updates to handle incorrect mermaid diagrams in https://github.com/asciidoctor/asciidoctor-diagram/issues/257 and https://github.com/asciidoctor/asciidoctor-diagram/issues/275 - both are part of asciidoctor-diagram 2.0.3.

I'm currently waiting for the new release to propagate to asciidoctorj-diagram https://github.com/asciidoctor/asciidoctorj-diagram/pull/5

Take your time. Nothing urgent here, just want to stay up-to-date with upstream releases.

This is now available as part of pre-release 0.31.28.

The pre-release of the plugin is available from GitHub releases and the IntelliJ AsciiDoc EAP repository.

This updates the status badge on the repository's README

The badge show the CI workflow status on the master branch.

See https://docs.github.com/en/actions/managing-workflow-runs/adding-a-workflow-status-badge#using-the-branch-parameter for the docs.

A new version of asciidoctor-diagram has been released, let's keep this project it in-sync

Thanks for sharing this. I might have fixed inlined SVG as part of issue #548, that ended up in pre-release 0.31.25 and stable-release 0.31.27.

JCEF preview now uses real SVGs, and the proper content-security-policy in the preview. If you find anything else that bothers you, please don't hesitate to open an issue.

When rendering the preview, a nested include is mission.

The plugin currently maps all errors that occur outside of the current document to the first line of the document.

What would be the behavior you expect?

Good to hear that you like the AsciidoctorJ feature. Please be aware that not all AsciidoctorJ extensions might work as expected. Did you test the extension you want to use with the latest version of IntelliJ and the AsciiDoc plugin?

I usually back-port only bug fixes, not features. Are you (or is someone else in your organisation) willing to provide a pull request with a backport of #532?

I mean today there is no way to add third party AsciiDoc extensions to the plugin, so that it will be affected in the preview panel.

I think it would be a good idea to have a general way to add third party extensions. I'm to familar with the intellij plugin development, but if you give me some hints, i would like to try it.

I think for the issue #237 it would also be nice, to have some kind of possibility.

I'm closing this issue as there hasn't been a response for more than two weeks. Please continue to share your experiences as comments in this ticket, and I'll re-open it.

To share things that worked for you with future developers, please consider a pull request to the plugin's documentation.

Fixes ahus1/keycloak-dropwizard-integration#36

Running master @fca9af0 the example:

mvn test -pl keycloak-dropwizard-jaxrs-example -am -Pkeycloak-dropwizard-jaxrs-example

fails with:

	at org.glassfish.jersey.internal.inject.Injections.lambda$lookupInjectionManagerFactory$0(Injections.java:74)
	at java.util.Optional.orElseThrow(Optional.java:290)
	at org.glassfish.jersey.internal.inject.Injections.lookupInjectionManagerFactory(Injections.java:74)
	at org.glassfish.jersey.internal.inject.Injections.createInjectionManager(Injections.java:69)
	at org.glassfish.jersey.server.ApplicationHandler.<init>(ApplicationHandler.java:259)
	at org.glassfish.jersey.servlet.WebComponent.<init>(WebComponent.java:311)
	at org.glassfish.jersey.servlet.ServletContainer.init(ServletContainer.java:154)
	at org.glassfish.jersey.servlet.ServletContainer.init(ServletContainer.java:347)
	at javax.servlet.GenericServlet.init(GenericServlet.java:180)
	at org.eclipse.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:602)

Originally posted by @gjvoosten in https://github.com/ahus1/keycloak-dropwizard-integration/issues/31#issuecomment-630610979

... and I needed to add a dependency:

        <dependency>
            <groupId>org.glassfish.jersey.inject</groupId>
            <artifactId>jersey-hk2</artifactId>
            <version>2.30.1</version>
        </dependency>

to be able to run e.g. mvn test -pl keycloak-dropwizard-jaxrs-example -am -Pkeycloak-dropwizard-jaxrs-example

ok, I've updated the README (6411ae187258510610534cd9e1d8bb24368b035e)

Thank you for sending the log file. I searched it for clues, but haven't found a clue yet. I tested it locally with Windows 10, also a second screen, but wasn't able to reproduce the issue you experienced.

When I run my IDE on windows, I see some JCEF helper processes. Do you see them as well (or do you see error messages related to them)?

I noticed that you have a non-ASCII home directory: "C:\Users\AndréGomes". Now and then I've seen errors with JRuby (see here), but this doesn't affect your preview. And you reported your preview works find with JavaFX.

As you experienced problems with the Markdown plugin, it might suffer the from the same cause. May I suggest you open an issue with JetBrains describing your problems with the Markdown plugin? If there's a bug within JCEF, and if they find and fix it for Markdown, they will fix it for the AsciiDoc plugin as well. Please post the link to the issue in this ticket so people can upvote it.

The current plugin's homepage is hosted on https://intellij-asciidoc-plugin.ahus1.de with a GitHub repository at https://github.com/ahus1/intellij-asciidoc-plugin.ahus1.de

Hosting the homepage as part of the asciidoctor.org domain would make it more consistent. Moving the repository to the Asciidoctor GitHub organisation would make collaboration easier.

Goals:

• host the plugin's homepage on intellij-plugin.asciidoctor.org
• move the GitHub repository to the asciidoctor organization.

Conditions:

• the site should still deploy on Netlify (or a similar automatic static site hosting)
• the maintainer should be able to trigger re-deployments.

I (Alexander) can't do this myself, as I don't have permissions in the Asciidoctor organisation to move the repository, and no permission on the Netlify hosting for asciidoctor.org.

(follow-up to #479 / @mojavelinux)

Quite alike #469 the IntelliJ plugin also has some issues with anchors …

Please see attached file test-plugin.txt (an adoc masked as txt). While I think — and also was mentioned so by @mojavelinux — it is okay that neither version one nor two works (id-pretext*), at least the id-post version should fully work and not claim an "unresolveable anchor" (quite alike the id-before header).

Although AsciiDoctor does render the first two versions with the forced ids into usable links … without a pretty text that ain't nice ;-)

So what would I like to see in the ~debugged~ enhanced version? I'd like the plugin to offer just two ids for << resp. xref:…# …

• id-before
• id-post also considered as a valid id resp. resolvable anchor

As #469 has been implemented, I close this issue as a duplicate.

book.adoc:

= Title

== Section 1

Link to <<foo>>.

== [[foo]]Section 2

Text.

Expected: document renders without errors, clicking on a link navigates to section 2

Actual:

AsciiDoc Plugin Version: 0.30.59.1

IDE Name and Version: RubyMine 2020.1 Build #RM-201.6668.156, built on April 14, 2020 Runtime version: 11.0.6+8-b765.25 amd64 VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o Windows 10 10.0

Handling anchors in section titles will be available in the next upcoming release 0.31.28

This bug is an annoyance when using an existing image filename as a template. E.g. you are naming your images:

my-long-image-name-01.png
my-long-image-name-02.png
my-long-image-name-03.png

Scenario:

1. Copy an image (e.g. a screenshot) to the clipboard
2. Press Paste (Ctrl-V)
3. Select .png as the format, and press OK
4. Click on an existing image filename, e.g. my-long-image-name-03.png to default the value in the filename textbox
5. Change the name in the filename textbox to my-long-image-name-04.png

A popup is displayed: my-long-image-name-03.png already exists. Do you want to replace it?

Desired behavior: The image is saved as my-long-image-name-04.png

AsciiDoc Plugin Version: 0.31.15

IDE Name and Version: IntelliJ IDEA 2020.2 (Community Edition)