that is excellent - thanks for doing that.
On Wed, Mar 20, 2019 at 6:51 AM Robert Dale wrote:
> Sure, probably to 'latest' docs where these things could change. So, we can
> use the 'anchor:name[]' syntax to create explicit anchors context-free.
>
> Thus:
>
> anchor:connecting-via-remotegraph[]
Sure, probably to 'latest' docs where these things could change. So, we can
use the 'anchor:name[]' syntax to create explicit anchors context-free.
Thus:
anchor:connecting-via-remotegraph[]
anchor:connecting-via-java[]
[[gremlin-java]]
== Gremlin-Java
I've restored the anchors in this way -
ht
i've external linked to those anchors many times from other sites like
StackOverflow, blog posts, the mailing lists, etc. didn't want them to have
to come up "dead".
On Tue, Mar 19, 2019 at 6:17 PM Robert Dale wrote:
> There does have to be some sort of content following the anchor. So maybe
>
There does have to be some sort of content following the anchor. So maybe
an html comment after each would work. I can try it later.
But what links are you seeing that need preserved? Something that
references ‘latest’ docs? All the internal links are fully qualified with
the version.
On Tue
oh hellthat's bad. so there's no way to preserve old links? is there no
workaround at all? some sort of hidden text maybe?
[[connecting-via-remotegraph]]
// comment
[[connecting-via-java]]
// comment
[[gremlin-java]]
== Gremlin-Java
???
On Tue, Mar 19, 2019 at 5:23 PM Robert Dale wrote:
In Asciidoc, you cannot stack multiple anchor Ids. Only the last one will
be used. You will end up with broken links if any of the previous anchors
are referenced. Asciidoc will not warn you or complain.
Bad:
[[connecting-via-remotegraph]]
[[connecting-via-java]]
[[gremlin-java]]
== Gremlin-Java
