85cb554400
This is more consistent than it is at the moment. For the __FILENAME__ macro, use the path relative to the original file or the location last matched on the include path. This ensures that the macro is consistent no matter which directory you call quickbook from. Also enable `__FILENAME__` in debug mode - so I can test this. [SVN r70230]
9 lines
150 B
Plaintext
9 lines
150 B
Plaintext
[article Filename test with include path
|
|
[quickbook 1.5]
|
|
]
|
|
|
|
__FILENAME__
|
|
|
|
[include filename_include1.quickbook]
|
|
|
|
[include filename_include2.quickbook] |