doorstop export all doesn't do the obvious thing
#678
Assignees
Comments
|
I believe the |
|
Yep. They issue here is the error or behaviour when that isn’t there.
…On Tue, 8 Oct 2024 at 15:56, Jace Browning ***@***.***> wrote:
I believe the . in doorstop export all . is the location we want the full
document tree to be exported to. Is that not the case?
—
Reply to this email directly, view it on GitHub
<#678 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAB4O4DTEHBML3GHPQ2ITE3Z2PXAXAVCNFSM6AAAAABPSGZX5WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMBQGA4DMMBWGE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
Simplest fix is to fix error to ‘location for output file(s) is required’
though maybe a more ‘normal’ command line behaviour would be to output to
cwd and have a -o option for an output location, but this wouldn’t be
backward compatible.
…On Tue, 8 Oct 2024 at 23:39, Robert Taylor ***@***.***> wrote:
Yep. They issue here is the error or behaviour when that isn’t there.
On Tue, 8 Oct 2024 at 15:56, Jace Browning ***@***.***>
wrote:
> I believe the . in doorstop export all . is the location we want the
> full document tree to be exported to. Is that not the case?
>
> —
> Reply to this email directly, view it on GitHub
> <#678 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AAB4O4DTEHBML3GHPQ2ITE3Z2PXAXAVCNFSM6AAAAABPSGZX5WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMBQGA4DMMBWGE>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>
|
|
Updated the description, will file a PR asap.. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
To export all, you still need to pass the path, e.g.
doorstop export -x all .whereas, e.g.
doorstop export -x allgives the error
doorstop: error: only single documents can be displayed, which seems nonsensical from a user perspective.I suggest
doorstop export allshould do the obvious thing of exporting all to the current working directory. @jacebrowning what do you think?The text was updated successfully, but these errors were encountered: