Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Relative path to the original or new command does not work #1

Closed
HubTou opened this issue Jun 5, 2021 · 1 comment
Closed

Relative path to the original or new command does not work #1

HubTou opened this issue Jun 5, 2021 · 1 comment
Assignees
@HubTou
Labels
bug Something isn't working documentation Improvements or additions to documentation

Comments

@HubTou
Copy link
Owner

HubTou commented Jun 5, 2021

Indeed, as the b2bt utility execute the original and the new commands in an auto created sub directory, the path to these utilities currently has to be an absolute one, which is not indicated in the documentation.

This will be corrected in a future version.
@HubTou HubTou added bug Something isn't working documentation Improvements or additions to documentation labels Jun 5, 2021
@HubTou HubTou self-assigned this Jun 5, 2021
@HubTou HubTou changed the title Relative path to the orginal or new command does not work Relative path to the original or new command does not work Jun 5, 2021
HubTou added a commit that referenced this issue Jun 5, 2021
@HubTou
Update to v1.0.1
39f4c72 
Path to the original and new command can now be relative (fixes issue #1)
@HubTou
Copy link
Owner Author

HubTou commented Jun 5, 2021

Fixed in v1.0.1

@HubTou HubTou closed this as completed Jun 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@HubTou HubTou

Labels
bug Something isn't working documentation Improvements or additions to documentation
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@HubTou