christiangalsterer / bitbucket-asciidoc-plugin Goto Github PK

It would be very cool, if you add support for diagrams

1. I have a master as my default branch
2. I push up some .adoc with some image::[] blocks and some .pngs to my-branch
3. I view the new rendered page

the images do not seem to be included in the rendering of my-branch.
It looks like they are only included when merged into the default branch.

Similar to #12, when linking to a different document with link:my_dir/my_doc.adoc it does not factor that I am not using the default branch.

I would like to be able to have text strikethrough rendered.

Following the example from below.
http://stackoverflow.com/questions/38804306/how-do-i-do-strikethrough-line-through-in-asciidoc

I attempted this:

* [line-through]#link:{travis-ci}[Tavis CI]#

I have tested this with asciidoctor and does render as expected.

Hello,

Using Bitbucket 5.5..1, with AsciiDoc 3.1.1, the inline link is incorrect. If you hover over a link, the PATH will be <path>/#<anchor name>?at=/refs/heads/master. You will be presented the folder list after clicking on this link. In AsciiDoc 3.0.0, if you hover over a link, the PATH will be <path>/<filename>#<anchor>, Clicking on this link, the target is presented.

Attached is a sample asciidoc file.

Thank-you!
sample_asciidoc.txt

The latest UPM update (3.0) marks this plugin is not compatible with the following text:

The currently installed app was a part of the deprecated Data Center program and the app version is now not Data Center compatible. Please update the app to a Data Center version.

According to Atlassian:

The latest UPM update (3.0.0) contains Data Center compatibility messaging, which is why you’re now seeing these messages.
You’re seeing these as Atlassian has launched a new class for marketplace data center to test if the add-ons are DC compatible. This is to ensure that those add-ons are not compromising performance of the instance. Please refer to the full announcement here A new class of Marketplace app has arrived.
As a result, you will encounter situation where the plugins are marked as incompatible. We’re still approving new apps daily as our vendors and partners update their apps to meet our new Data Center standards. Ultimately, Atlassian recommends you contact the vendor to determine compatibility at scale. For the apps released by us, we are currently working on releasing new versions but that could still take some time.
In most cases, the add-ons should still work and you won’t see any problems (as they’ve been working fine so far), but look out for any updates from vendors.

Use the standard CSS styles used for rendering markdown to provide an similar/identical rendering experience.

Image references like

image::sunset.jpg[]

are not resolved. There is a raw display mode for files in Bitbucket but the URL but those are not relative to the asciidoc document. Hence images are not displayed.

Would be nice to have icons rendered with font awesome

Support highlight.js as intermediate solution to highlight code snippets.

Hello,
is there a way to use your BitBucket-Asciidoc-Plugin for BitBucket Server ( v7.17.5) or DataCenter?
Thanks for your feedback.

After we installed the plugin into our Atlassian Bitbucket v4.5.1 server it renders build.gradle files und fails at it.

Is there any possiblity to restrict the plugin to *.adoc files only?

Hey,

We are evaluating writing our doc files with asciidoc instead of markdown.

One feature I am excited about is the include possibility.
In asciidoc I could write:

[source,perl]
----
include::lib/dirlist.pl[lines=9..17]
----

Which gets processed and resolved in the IDEA Asciidoc support, but when viewed on our bitbucket server, it gets translated to:

link:lib/dirlist.pl[]

I learned that for example github also does this, probably due to the so called safe mode:

http://asciidoctor.org/docs/user-manual/#running-asciidoctor-securely

But at least the link should work I guess (meaning I'd like to have the actual link not the text "link").

We are running version 2.3.1 of the plugin.

Could you please suggest a workaround?

Render .adoc files using Asciidoctor default stylesheet

https://github.com/asciidoctor/asciidoctor/blob/master/data/stylesheets/asciidoctor-default.css

Images (and potentially other files) that are stored in git lfs aren't linked to correctly; it appears that the "&raw" extension to the url doesn't actually point (or redirect) to the actual image. If the image is browsed to directly using the BitBucket Server interface, the "Raw File" link is actually some kind of REST API call to the associated lfs server.

Not sure if this is even an issue that can be (easily?) solved, but given the prevalence of git lfs, thought I'd raise it anyway!

Thanks!

Bitbucket server version: v4.5.2

If I have a README.adoc it does not get rendered by default when going to the repository. README.md files are shown by default.

I would like to have the same behavior if a README.adoc is present.

Please vote here. Depending on the number of votes I will also try to maintain a version for Bitbucket Server < 4.0.0

this is quite some special behaviour...

in IE11, images are linked without the ?raw parameter at the end which result in those images not being displayed.

A workaround is to add the parameter manually (it doesn't hurt the normal rendering):

image::demo.png?raw[]

Do you know what going on here? I can't see a section in the source where the ?raw paramater is not appended...

"This app is not compatible with your Bitbucket instance. Request an update from the vendor." displayed after upgrading to Bitbucket Server 6.0.1

Hey.
Based on #9 .

I writing doc on my project with asciidoc.

I could write:

---
include::dir/file[tag=tag1]
---

But when viewed on our bitbucket server, it gets translated to:

link:dir/file[]

We used plugin version: 3.1.2.

Could you please suggest a workaround?

Use the build in Bitbucket code mirror theme for code highlighting for consistent look and feel.

Hello,

With AsciiDoc version 3.1.0, after clicking on a link in an AsciiDoc document, the link does not go to the correct target but lists the files in the folder. AsciiDoc 3.1.0 determines the link to be /#?at=refs/heads/master which does not exist whereas AsciiDoc 3.0.0 determines the link to be /# which exists and the target is displayed.

Can you please resolve the issue so that the links are followed.

Thanks!

Support for AsciiMath syntax
Support for LaTeX syntax