OS X uses bash, and yes, $HOME is substituted just fine ($HOME is the usual environment variable for the user's home directory in sh, bash, and many other shells). I can copy and paste the path to 'ls' or 'cat' or anything else, and the system has no problem finding the file. I've tried doing the replacement for $HOME manually, providing a full absolute path; again, it works everywhere else but asciidoc's --conf-file option.
And I just wrote a tiny program that uses os.path.isfile() on that exact path . . . and it returns True. In short, the problem is not with the file. The problem is that Asciidoc can't seem find a fully-specified absolute path that actually does exist, and I'd like to know why. On Tuesday, June 21, 2016 at 3:59:06 AM UTC-7, Lex Trotman wrote: > > On 21 June 2016 at 20:37, Ken McGlothlen <[email protected] > <javascript:>> wrote: > > 1. asciidoc 8.6.9 > > 2. Mac OS X v10.11.5 > > 3. $HOME/ven/repos/vistaexpertise.net/ven-page.conf > > > > The file was working just fine in my $HOME/.asciidoc directory; moving > it to > > this new directory produces said error. > > It was probably located by the standard search paths before the > --conf-file option was processed, thats why it worked. > > > > > The full command line: > > > > /opt/local/bin/asciidoc --verbose --attribute=rootdir=".." \ > > > > --conf-file="$HOME/ven/repos/vistaexpertise.net/ven-page.conf" \ > > > > -o $HOME/ven/repos/vistaexpertise.net/build/newsite/test.html \ > > > > $HOME/ven/repos/vistaexpertise.net/newsite/test.adoc > > > > What is $HOME ? > > I know nothing about OSX, what shell does it use? Is $HOME substituted > inside the "" ? > > Essentially the problem is that the path does not look like a standard > file to Python, since Asciidoc uses the os.path.isfile() function to > test for the existence of the file. Look at what is printed on the > error message and check its correct, the exact path is printed after > the colon space at the end of the message. > > > > > > > On Tuesday, June 21, 2016 at 12:46:04 AM UTC-7, Lex Trotman wrote: > >> > >> 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] <javascript:>. > > To post to this group, send email to [email protected] > <javascript:>. > > 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.
