On 11/19/2012 10:53 PM, Stuart Rackham wrote:
It works for me, please post a minimal example that illustrates the
problem and the version of AsciiDoc that you are using.

Cheers, Stuart


On 20/11/12 16:35, ping wrote:
On 11/16/2012 6:40 PM, ping wrote:
per man asciidoc:

       -a, --attribute=ATTRIBUTE
            Define or delete document attribute.  ATTRIBUTE is
formatted like NAME=VALUE. Command-line attributes take precedence
over document and configuration
            file attributes. Alternate acceptable forms are NAME (the
VALUE defaults to an empty string); NAME!  (delete the NAME
attribute); NAME=VALUE@ (do not
            override document or configuration file attributes). Values
containing spaces should be enclosed in double-quote characters. This
option may be
            specified more than once. A special attribute named trace
controls the output of diagnostic information.



but I tried:
asciidoc -a numbered! abc.asciidoc
asciidoc --attributes numbered! abc.asciidoc
asciidoc numbered! abc.asciidoc

none of the work.
not sure is it because this looks a stupid question or it was slipped
away in the weekend emails?

I'm sorry to waste your time. it IS a stupid Q and I just realized why.


==some details if anyone get same oversight as me=============================
I got a habit to do most things in vim, so I was testing like this:
:w !asciidoc -a toc -o Dropbox/temp-transfer/temp.html -a numbered! -

and it report:

asciidoc: Too many arguments

Man page:     asciidoc --help manpage
Syntax:       asciidoc --help syntax

shell returned 1

because that "!" was not escaped in vim Ex cmd and was causing the issue.

This work well:
:w !asciidoc -a toc -o Dropbox/temp-transfer/temp.html -a numbered\! -

--
You received this message because you are subscribed to the Google Groups 
"asciidoc" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/asciidoc?hl=en.

Reply via email to