Re: [DISCUSS] Asciidoc Header Reformat

Looks good! Robert Dale On Tue, Sep 26, 2017 at 1:38 PM, Daniel Kuppitz wrote: > Yea, that was the right regex to look for these errors: grep '^== $' > $(find . -name "*.asciidoc") > Got them all now, will push the fix in a few. > > Cheers, > Daniel > > > On Tue, Sep 26,

Re: [DISCUSS] Asciidoc Header Reformat

Yea, that was the right regex to look for these errors: grep '^== $' $(find . -name "*.asciidoc") Got them all now, will push the fix in a few. Cheers, Daniel On Tue, Sep 26, 2017 at 10:30 AM, Robert Dale wrote: > docs/src/reference/gremlin-applications.asciidoc: > @@

Re: [DISCUSS] Asciidoc Header Reformat

That was master. tp32 is: @@ -278,8 +272,7 @@ v[2] v[3] v[4] v[5] -v[6] - +== v[6] It is also possible to pass arguments to scripts. Any parameters following the file name specification are treated as arguments to the script. They are collected into a list and passed in as a variable

Re: [DISCUSS] Asciidoc Header Reformat

docs/src/reference/gremlin-applications.asciidoc: @@ -294,8 +288,7 @@ v[2] v[3] v[4] v[5] -v[6] - +== v[6] It is also possible to pass arguments to scripts. Any parameters following the file name specification are treated as arguments to the script. They are collected into a list and

Re: [DISCUSS] Asciidoc Header Reformat

Looks like master CHANGELOG picked up a conflict... <<< HEAD == TinkerPop 3.3.0 (Gremlin Symphony #40 in G Minor) . . . == TinkerPop 3.2.0 (Nine Inch Gremlins) === == TinkerPop 3.2.0 (Nine Inch Gremlins) >>> asciidoc-header Robert Dale On Tue, Sep 26, 2017 at 1:19 PM, Daniel

Re: [DISCUSS] Asciidoc Header Reformat

Ah, good find! That's the same issue I've had in the reference docs and recipes. Fixed. Cheers, Daniel On Tue, Sep 26, 2017 at 10:08 AM, Robert Dale wrote: > git grep "== ==" > > Robert Dale > > On Tue, Sep 26, 2017 at 1:07 PM, Robert Dale wrote: > > > I

Re: [DISCUSS] Asciidoc Header Reformat

git grep "== ==" Robert Dale On Tue, Sep 26, 2017 at 1:07 PM, Robert Dale wrote: > I see things like '== ==>6' in docs/src/upgrade/release-3.2. > x-incubating.html > > Robert Dale > > On Tue, Sep 26, 2017 at 12:57 PM, Robert Dale wrote: > >> ^d >> >>

Re: [DISCUSS] Asciidoc Header Reformat

I see things like '== ==>6' in docs/src/upgrade/release-3.2.x-incubating.html Robert Dale On Tue, Sep 26, 2017 at 12:57 PM, Robert Dale wrote: > ^d > > Robert Dale > > On Tue, Sep 26, 2017 at 12:56 PM, Daniel Kuppitz wrote: > >> This is one. I pushed the

Re: [DISCUSS] Asciidoc Header Reformat

^d Robert Dale On Tue, Sep 26, 2017 at 12:56 PM, Daniel Kuppitz wrote: > This is one. I pushed the changes to tp32/ and master/. I only found (and > fixed) 2 minor issues, where my script produced a little formatting mess. > > Cheers, > Daniel > > > On Tue, Sep 19, 2017 at

Re: [DISCUSS] Asciidoc Header Reformat

This is one. I pushed the changes to tp32/ and master/. I only found (and fixed) 2 minor issues, where my script produced a little formatting mess. Cheers, Daniel On Tue, Sep 19, 2017 at 9:23 AM, Stephen Mallette wrote: > For whatever reason we started writing our

Re: [DISCUSS] Asciidoc Header Reformat

I ran into this problem previously as well; it's also interesting that the build will break if the length of the heading is much longer/shorter than the length of the underline (I think a difference of more than 2 characters causes a build error). Here is a Python and shell script I wrote to do

[DISCUSS] Asciidoc Header Reformat

For whatever reason we started writing our headers in our docs with: Header == Subheader - SubSubHeader as opposed to the alternative: = This Is A Header == Subheader === SubSubHeader The downside with the first approach is that it forces us to do two things: 1.