asciidoc @10.2.0 Warning: invalid escape sequence '\S'

[christophecvr]

asciidoc: Update to 10.2.1

Closes: https://trac.macports.org/ticket/70039

Description

Type(s)

• bugfix
• enhancement
• security fix

Tested on

macOS 10.15.7
Xcode 11.5 / Command Line Tools 11.5.0
Compiler Apple clang 11.0.1

Verification

Have you

• followed our Commit Message Guidelines?
• squashed and minimized your commits?
• checked that there aren't other open pull requests for the same change?
• referenced existing tickets on Trac with full URL in commit message?
• checked your Portfile with port lint --nitpick?
• tried existing tests with sudo port test?
• tried a full install with sudo port -vst install?
• tested basic functionality of all binary files?
• checked that the Portfile's most important variants haven't been broken?

[macportsbot]

Notifying maintainers:
@neverpanic for port asciidoc.

[ryandesign]

I assume you meant macOS 10.15.7?

When we merge this (or beforehand by force-pushing if you wish) we should reword the commit message to remove the square brackets around the URL.

[ryandesign]

The first line of the commit message should also be reworded to say "asciidoc: Update to 10.2.1"

[christophecvr]

I assume you meant macOS 10.15.7?

When we merge this (or beforehand by force-pushing if you wish) we should reword the commit message to remove the square brackets around the URL.

Yes corrected to 10.15.7

The commit message self can't be edited, but I updated the message here
First line update to asciidoc: to 10.2.1
and the link here Fixes : [...] is removed

Closes: link set instead.

p.s. I well can just create a commit just to have a new message on top but then it becomes a messy pot (I find)
However now I know that by the initial commit the msg created with the git vi editor does not need brackets for the link.
So I know it for next time. 👍

[ryandesign]

Changing the text of the PR isn't relevant. The commit message can be edited. Then you force push. Or we can edit the message when we merge the PR.

[christophecvr]

@ryandesign
Would this be the perfect commit initial message created with vi editor perfect ?
Since I did not commit the change to my personal work branch in my github fork of macports.
I took the opportunity to test it.

For just this last patch update asciidoc: to 10.2.1
example

[markemer]

Should we recommend asciidoctor as that has replaced this as Asciidoc's reference implementation?

[christophecvr]

Should we recommend asciidoctor as that has replaced this as Asciidoc's reference implementation?

This is asciidoc-py not asciidocter . asciidocter also a converter but is another utility. aciidoctor has also a port.

The git hub has been moved from :

https://github.com/asciidoc/asciidoc-py3

to :

https://github.com/asciidoc-py/asciidoc-py

[christophecvr]

Changing the text of the PR isn't relevant. The commit message can be edited. Then you force push. Or we can edit the message when we merge the PR.

Ok sorry forgot about the git amend followed by forced push. Is just done now