Clearly something unusual is happening, so some more information would be useful, like the version of asciidoc, the system you are running it on, the exact name of the file, etc.
On 21 June 2016 at 15:15, Ken McGlothlen <[email protected]> wrote: > I get the "asciidoc: FAILED: missing configuration file" error on a file > that exists, is readable, and is a valid asciidoc configuration file. I'm > specifying it with an absolute path with --conf-file on the command line, so > there shouldn't be any confusion, should there? > > -- > You received this message because you are subscribed to the Google Groups > "asciidoc" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/asciidoc. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "asciidoc" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/d/optout.
